[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] [PATCH] [HVM] [RFC] Moving the e820 table creation into hvmloader




Keir Fraser <keir@xxxxxxxxxxxxx> wrote on 11/08/2006 06:08:03 PM:

>
>
>
> On 8/11/06 10:35 pm, "Stefan Berger" <stefanb@xxxxxxxxxx> wrote:

> > Is that to be marked as ACPI too? So we can just tack it on the end
> > of a big ACPI region at, say, 0xE0000? Frankly, for now, we can just
>
> Yes, it has to be marked such that it's not claimed by an OS.
> Probably it's the best to mark it as ACPI and put it into the same
> memory chunk as the rest of ACPI.

>
> I believe regions marked ACPI are allowed to be reclaimed by the OS
> after it has parsed the ACPI tables. So perhaps the log memory needs
> to be marked reserved, or not covered by an e820 region at all.


Probably then 'reserved', although when I put it into the ACPI area it worked. The driver that accesses that log will try to map it every time one opens a sysfs file.

http://www.linux-m32r.org/lxr/http/source/drivers/char/tpm/tpm_bios.c?v=2.6.18#L386

  Stefan
>
>  -- Keir

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.