From: Ingo Molnar <mingo@elte.hu>
To: Ian Campbell <ijc@hellion.org.uk>
Cc: linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
Jeremy Fitzhardinge <jeremy@goop.org>,
Mark McLoughlin <markmc@redhat.com>,
Alexander van Heukelum <heukelum@fastmail.fm>
Subject: Re: [PATCH 2/2] x86/xen: Disable DMI parsing in Xen kernel.
Date: Thu, 28 Feb 2008 11:44:34 +0100 [thread overview]
Message-ID: <20080228104434.GA8964@elte.hu> (raw)
In-Reply-To: <1204194923.5446.30.camel@zakaz.uk.xensource.com>
* Ian Campbell <ijc@hellion.org.uk> wrote:
> > > Looks like the only sane solution will be to mark regions between
> > > 640K-1M reserved early on in boot.
> >
> > and as luck has it, such a patch from Alexander van Heukelum has
> > been put into x86.git#testing just yesterday.
> >
> > So ... could you try x86.git#testing - does it work out of box? Is
> > the reservation early enough to prevent pagetables be allocated in
> > weird places?
>
> That patch is 64 bit only and also I'm not sure what EBDA looks like
> to a Xen domU (I expect it doesn't exist). I'll give it a go but I'm
> not hopeful.
it was requested to be unified to 32 bit as well already - no patch yet.
I'd gladly take a patch that does it - it fixing 32-bit Xen guests would
be an added bonus. Perhaps this all should be done by injecting a very
eary e820 filter instead of reserving it later on? 640k..1M being
special is a deep PC legacy, i doubt we'll ever recover from it ;-)
Ingo
prev parent reply other threads:[~2008-02-28 10:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-28 8:26 [PATCH 1/2] x86: Add nodmi command line option to turn off DMI parsing Ian Campbell
2008-02-28 8:26 ` [PATCH 2/2] x86/xen: Disable DMI parsing in Xen kernel Ian Campbell
2008-02-28 9:31 ` Ian Campbell
2008-02-28 9:46 ` Ingo Molnar
2008-02-28 10:35 ` Ian Campbell
2008-02-28 10:44 ` Ingo Molnar [this message]
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=20080228104434.GA8964@elte.hu \
--to=mingo@elte.hu \
--cc=heukelum@fastmail.fm \
--cc=hpa@zytor.com \
--cc=ijc@hellion.org.uk \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=markmc@redhat.com \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
/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.