LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Ian Campbell <ijc@hellion.org.uk>
To: Ingo Molnar <mingo@elte.hu>
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 10:35:23 +0000	[thread overview]
Message-ID: <1204194923.5446.30.camel@zakaz.uk.xensource.com> (raw)
In-Reply-To: <20080228094613.GC2987@elte.hu>


On Thu, 2008-02-28 at 10:46 +0100, Ingo Molnar wrote:
> * Ian Campbell <ijc@hellion.org.uk> wrote:
> 
> > Actually scratch this patchset -- its not sufficient. For example 
> > ddcprobe in userspace causes the exact same issue vs 0xa0000.
> > 
> > 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.

>  [or am i missing something - this is about the guest kernel 
> reserving th 640k..1M area, not the host kernel - right?]

Correct, the area between 640k and 1M is just normal memory for a Xen
guest and the memory map reflects that so page tables and other stuff
get allocated in regions which would be magic data structures on native.

Ian.
-- 
Ian Campbell

The woman you buy -- and she is the least expensive -- takes a great
deal of money.  The woman who gives herself takes all your time.
		-- Balzac


  reply	other threads:[~2008-02-28 10:35 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 [this message]
2008-02-28 10:44         ` Ingo Molnar

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=1204194923.5446.30.camel@zakaz.uk.xensource.com \
    --to=ijc@hellion.org.uk \
    --cc=heukelum@fastmail.fm \
    --cc=hpa@zytor.com \
    --cc=jeremy@goop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=markmc@redhat.com \
    --cc=mingo@elte.hu \
    --cc=mingo@redhat.com \
    --cc=tglx@linutronix.de \
    --subject='Re: [PATCH 2/2] x86/xen: Disable DMI parsing in Xen kernel.' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).