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

[Xen-devel] Re: [PATCH] Re: [Xen-staging] [xen-unstable] Enable HVM guest VT-d device hotplug via a simple ACPI hotplug device model.


  • To: Alex Williamson <alex.williamson@xxxxxx>
  • From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
  • Date: Sat, 16 Feb 2008 15:56:41 +0000
  • Cc: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • Delivery-date: Sat, 16 Feb 2008 07:56:16 -0800
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AchwtIUgw5Cy8tynEdy5EAAWy6hiGQ==
  • Thread-topic: [PATCH] Re: [Xen-staging] [xen-unstable] Enable HVM guest VT-d device hotplug via a simple ACPI hotplug device model.

On 16/2/08 15:28, "Alex Williamson" <alex.williamson@xxxxxx> wrote:

>> Hmmm... they're x86-specific because they define x86-specific i/o port
>> addresses. It may be nicer to more clearly separate out the x86-specific
>> code that uses these macros. I'll take a look.
> 
>    That was my initial thought too, but 12390:430e06e2aa08 is the change
> that set the PM1A_EVT_BLK_ADDRESS to it's current value, and it
> indicates it's for ia64.  So my guess was that we both have this at the
> same address.  I'm not sure why cset 12390 doesn't make use of the macro
> with the acpi_map() call it makes though.

Ah, okay.

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