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

Re: [Xen-devel] [PATCH] [Xen] Check FADT's signature


  • To: Stefan Berger <stefanb@xxxxxxxxxx>
  • From: Keir Fraser <keir@xxxxxxxxxxxxx>
  • Date: Fri, 10 Aug 2007 14:23:26 +0100
  • Cc: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • Delivery-date: Fri, 10 Aug 2007 06:24:03 -0700
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AcfbUaH+4NhH4EdEEdy2zAAX8io7RQ==
  • Thread-topic: [Xen-devel] [PATCH] [Xen] Check FADT's signature

On 10/8/07 12:36, "Stefan Berger" <stefanb@xxxxxxxxxx> wrote:

(XEN) (1) Mapped 0xf601f to ff0f601f
(XEN) Using APIC driver default
(XEN) IN acpi_parse_fadt.
(XEN) (2) Mapped 0x3ffcfec0 to fff9bec0, base = 0xfff9b000
(XEN) ACPI: Invalid FADT signature A__ADR

This ‘A__ADR’ looks remarkably like the middle of another ACPI table. :-)

Perhaps you could scan all physical memory in the range 3ffcd000-3ffd0000, either via /dev/mem in native Linux, or hack some code to map-and-check within Xen, or whatever, and look for that string? It’d be interesting to know:
 a) does it appear at all?
 b) is it at the same offset in a page as we expect the fadt signature to appear (ie., offset 0xec0)?
 c) is it in a page we mapped previously via __acpi_map_table()?

 -- 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®.