[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <47C47107.2020608@goop.org>
Date: Tue, 26 Feb 2008 12:05:27 -0800
From: Jeremy Fitzhardinge <jeremy@...p.org>
To: Mark McLoughlin <markmc@...hat.com>
CC: Ian Campbell <ijc@...lion.org.uk>,
"H. Peter Anvin" <hpa@...or.com>,
Joel Becker <Joel.Becker@...cle.com>,
Jody Belka <lists-lkml@...b.org>, linux-kernel@...r.kernel.org,
Ingo Molnar <mingo@...e.hu>,
Thomas Gleixner <tglx@...utronix.de>,
"Eric W. Biederman" <ebiederm@...ssion.com>,
Andi Kleen <andi@...stfloor.org>,
Mika Penttila <mika.penttila@...umbus.fi>
Subject: Re: 2.6.25-rc1 xen pvops regression
Mark McLoughlin wrote:
>> @@ -371,6 +372,9 @@ void __init dmi_scan_machine(void)
>> }
>> }
>> else {
>> + if (e820_all_mapped(0xF0000, 0xF0000+0x10000, E820_RAM))
>> + goto out;
>>
>
> One issue with using the e820 map for this is that a Xen Dom0 will also
> have this region marked as RAM in the e820 map, but will set up a fixmap
> for it, allowing dmi_scan_machine() to map the region.
>
Would it be easier to just fake up a mapping so that window points to
the real dmi area, and mark E820 accordingly?
J
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists