From: Keir Fraser <keir@xensource.com>
To: Jan Beulich <jbeulich@novell.com>, xen-devel@lists.xensource.com
Subject: Re: [PATCH 0/8] 2.6.17 merge additions
Date: Fri, 02 Mar 2007 09:19:11 +0000 [thread overview]
Message-ID: <C20D9C8F.A786%keir@xensource.com> (raw)
In-Reply-To: <45E7F701.76E4.0078.0@novell.com>
On 2/3/07 09:05, "Jan Beulich" <jbeulich@novell.com> wrote:
> Before submitting 2.6.18 stuff we were missing from the -unstable merge,
> is it possible to get an understanding why patches 5 (pc speaker device
> registration in domU) and 8 (early DMI scan) of the 2.6.17 set were not
> taken?
I'm undecided on those. Keeping pcspkr is pretty harmless (actually I'm not
sure what the device registration is even for!) and removing it would just
take us further from native. I don't have a really strong opinion on this
one however. For the second patch: the principle of moving DMI scan earlier
is nice, but this approach makes a horrible mess of the mm init code (which
is quite nasty enough already!). I wonder whether we could come up with a
two-stage mm init for x86/64 -- some very early Xen-specific stuff to get is
into a state that is a bit more like native, would allow us to do things
like DMI scan at a more appropriate time, and might clean up the
paging_init() mess a bit rather than making it worse.
-- Keir
next prev parent reply other threads:[~2007-03-02 9:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-14 15:56 [PATCH 0/8] 2.6.17 merge additions Jan Beulich
2007-03-02 9:05 ` Jan Beulich
2007-03-02 9:19 ` Keir Fraser [this message]
2007-03-02 9:59 ` Jan Beulich
2007-03-02 11:17 ` Keir Fraser
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=C20D9C8F.A786%keir@xensource.com \
--to=keir@xensource.com \
--cc=jbeulich@novell.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.