[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] kernel breakage (kexec)

  • To: Jan Beulich <jbeulich@xxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: Keir Fraser <keir@xxxxxxxxxxxxx>
  • Date: Mon, 11 Dec 2006 15:46:00 +0000
  • Delivery-date: Mon, 11 Dec 2006 07:46:00 -0800
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AccdO3Sbs1Ss1IkuEdu9WAAX8io7RQ==
  • Thread-topic: [Xen-devel] kernel breakage (kexec)

I'm afraid there was more fallout from the late merge of kexec/kdump than we
expected. The interfaces are now frozen, we promise!

 -- Keir

On 11/12/06 15:40, "Jan Beulich" <jbeulich@xxxxxxxxxx> wrote:

> While I realize that -unstable is a development branch, feature freeze for
> 3.0.4
> was announced over a week ago, and my previously taken snapshot originates
> from after that. However, in an attempt to get the merged up 32on64 patches
> up to the latest bits I took a fresh snapshot today, with the result that even
> without any of my patches I can't boot any kexec-enabled Xen kernel built with
> the previous snapshot anymore.
> While I'm certain that this will go away as soon as I update the kernel, I
> specifically wanted to avoid doing a kernel merge (in order to save time to
> give
> the people asking for these patches something without undue delay) at least
> until after sending out these patches.
> Was it indeed impossible to not introduce this significant a set of changes (I
> got
> puzzled already when I saw the number of new change sets, which really applies
> to earlier releases, too). I would really appreciate if after feature freeze
> major
> changes (both functional any cosmetic) could be avoided.

Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.