This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


[Xen-devel] Re: [PATCH] Re: [Xen-staging] [xen-unstable] Enable HVM gues

To: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Subject: [Xen-devel] Re: [PATCH] Re: [Xen-staging] [xen-unstable] Enable HVM guest VT-d device hotplug via a simple ACPI hotplug device model.
From: Alex Williamson <alex.williamson@xxxxxx>
Date: Sat, 16 Feb 2008 08:28:36 -0700
Cc: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Sat, 16 Feb 2008 07:29:08 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <C3DC4AA2.140BC%Keir.Fraser@xxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Organization: HP OSLO R&D
References: <C3DC4AA2.140BC%Keir.Fraser@xxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On Sat, 2008-02-16 at 08:09 +0000, Keir Fraser wrote:
> On 15/2/08 16:54, "Alex Williamson" <alex.williamson@xxxxxx> wrote:
> >    This makes use of some macros that are only defined for i386/x86_64,
> > so the ia64 build fails on piix4acpi.c.  However, I'm not sure why these
> > are x86 only, and the cset that made them x86 only doesn't appear to
> > have any dependency on them.  Things seem to work fine if we enable
> > these for everyone.  Thanks,
> 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.


Alex Williamson                             HP Open Source & Linux Org.

Xen-devel mailing list