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


Re: [Xen-devel] Re: APIC rework

To: "Zhang, Xiantao" <xiantao.zhang@xxxxxxxxx>, Jeremy Fitzhardinge <jeremy@xxxxxxxx>
Subject: Re: [Xen-devel] Re: APIC rework
From: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Date: Tue, 17 Nov 2009 03:45:15 +0000
Cc: Xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>, "Han, Weidong" <weidong.han@xxxxxxxxx>, Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
Delivery-date: Mon, 16 Nov 2009 19:45:42 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <706158FABBBA044BAD4FE898A02E4BC201CD320368@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
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/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: Acpm6+sjvDcxUGwNQduO6bITFGn2LwAR5CTAAAE47RA=
Thread-topic: [Xen-devel] Re: APIC rework
User-agent: Microsoft-Entourage/
On 17/11/2009 03:13, "Zhang, Xiantao" <xiantao.zhang@xxxxxxxxx> wrote:

>> Is there any way for the dom0 kernel to tell whether the hypervisor is
>> implementing the new ABI, so it can choose how to set up interrupts.
>> MAP_COMPAT_BIT doesn't seem like a very good name, because it implies
>> that setting it reverts to "compatible" behaviour.  I assume that
>> leaving it clear enables the historical behaviour and setting it
>> enables the new one (since old kernels won't be setting it).
> Maybe better change to MAP_NEW_ABI_BIT ?  Since the hypervisor patch didn't
> change old code path after introducing this bit, so it is very easy and safe
> to backport to xen-3.4-testing tree, and make new dom0 be able to run top of
> it.  :)

It's kind of a shame to need this though. Is there no way for the hypervisor
to work out automatically whether an older dom0 is running? Or work out the
trigger/level stuff for itself (after all it parses the relevant bios tables
just like dom0)?

 -- Keir

Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>