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

Re: [Xen-devel] Bad FADT and timer going backwards

  • To: Stefan Berger <stefanb@xxxxxxxxxx>
  • From: Keir Fraser <keir@xxxxxxxxxxxxx>
  • Date: Thu, 09 Aug 2007 14:55:54 +0100
  • Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Thu, 09 Aug 2007 06:53:41 -0700
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AcfajQCuPxwINEaAEdyKhAAX8io7RQ==
  • Thread-topic: [Xen-devel] Bad FADT and timer going backwards

On 9/8/07 14:52, "Stefan Berger" <stefanb@xxxxxxxxxx> wrote:

> (XEN) ACPI table at 0x3ffcfec0 mapped to address fff9bec0
> (XEN) ACPI table at 0x3ffcdec0 mapped to address fff9bec0

Is it 'ok' that these two different phys. addresses get mapped to the same virtual address?

It’s expected. See the implementation of __acpi_map_table(). For this reason, the pointer returned by __acpi_map_table() is only guaranteed valid until the next invocation of __acpi_map_table().

 -- Keir
Xen-devel mailing list



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