All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gerd Hoffmann <kraxel@suse.de>
To: Keir Fraser <keir@xensource.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: [ANNOUNCEMENT] Schedule for Xen 3.0.4
Date: Fri, 24 Nov 2006 15:41:17 +0100	[thread overview]
Message-ID: <4567048D.5000702@suse.de> (raw)
In-Reply-To: <C18CAC96.4FC4%keir@xensource.com>

  Hi,

>> What about the new domain builder, domU kexec and 32-on-64?
> 
> I don't think domU kexec or 32-on-64 will make it.

domU kexec most likely probably needs some adjustments anyway after dom0
kexec merge ...

> Maybe some of the domain
> builder patches could: Emmanuel's been looking those so perhaps he has an
> opinion on it, but really I don't see us taking the wholesale rewrite for
> 3.0.4.

Well, *merging* the new domain builder shouldn't be a problem.  No "flag
day" switch required, it can happily live side-by-side with the old one.
 Then we can switch over users one-by-one to the new code as they get
ready, most likely not all of them for 3.0.4.

> After all, the primary benefit is when it's coupled with the 32-on-64
> patches which are very unlikely to be in 3.0.4.

Well, I've seen some ia64 guys want to play with bigendian domains, the
new domain builder (especially the rewritten ELF parser) can handle that
too ...

One of the reasons I want to have it merged soon (preferably before
3.0.4) is to make it easier to have the non-x86 (and other) people look
at it, so we maybe can have everyone using the new code by 3.0.5 and can
drop the old builder code at that point in time.

Merging it also makes it easier to test domU kexec as the userspace tool
 will be able to work with the 3.0.4 libraries.

cheers,
  Gerd

-- 
Gerd Hoffmann <kraxel@suse.de>
http://www.suse.de/~kraxel/julika-dora.jpeg

  reply	other threads:[~2006-11-24 14:41 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4566D99C.5050009@suse.de>
2006-11-24 14:05 ` [ANNOUNCEMENT] Schedule for Xen 3.0.4 Keir Fraser
2006-11-24 14:41   ` Gerd Hoffmann [this message]
2006-11-24 10:28 Keir Fraser
2006-11-24 10:42 ` John Levon
2006-11-24 10:58   ` Ewan Mellor
2006-11-24 15:54     ` Daniel P. Berrange
2006-11-24 16:34       ` Ewan Mellor
2006-11-24 18:22         ` Daniel P. Berrange
2006-11-28 14:26         ` Ewan Mellor
2006-11-28 14:37           ` Daniel P. Berrange
2006-11-29 17:12           ` Daniel P. Berrange
2006-11-24 12:44 ` Jan Beulich
2006-11-24 18:26 ` Chuck Short
2006-11-29 15:31 ` Sean Dague
2006-11-30 14:59 ` Pasi Kärkkäinen
2006-11-30 15:02   ` Keir Fraser
2006-11-30 15:08     ` Pasi Kärkkäinen
2006-11-30 16:57       ` Keir Fraser
2006-11-30 17:27       ` Ian Pratt

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4567048D.5000702@suse.de \
    --to=kraxel@suse.de \
    --cc=keir@xensource.com \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.