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] L1[0x1fb] = 0000000000000000 which faults on one type of

To: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
Subject: Re: [Xen-devel] L1[0x1fb] = 0000000000000000 which faults on one type of machine but on another works?
From: Jeremy Fitzhardinge <jeremy@xxxxxxxx>
Date: Thu, 17 Mar 2011 10:21:37 -0700
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, andrew.thomas@xxxxxxxxxx, Jan Beulich <JBeulich@xxxxxxxxxx>, Ian Campbell <Ian.Campbell@xxxxxxxxxxxxx>, keir.xen@xxxxxxxxx, swente@xxxxxxxxxxxxx, gianni.tedesco@xxxxxxxxxx
Delivery-date: Thu, 17 Mar 2011 10:22:23 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20110317164143.GA26392@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/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>
References: <20110316221912.GA13035@xxxxxxxxxxxx> <4D81EF97020000780003706E@xxxxxxxxxxxxxxxxxx> <20110317155211.GA29603@xxxxxxxxxxxx> <4D82411002000078000371D8@xxxxxxxxxxxxxxxxxx> <20110317164143.GA26392@xxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv: Gecko/20101209 Fedora/3.1.7-0.35.b3pre.fc14 Lightning/1.0b3pre Thunderbird/3.1.7
On 03/17/2011 09:41 AM, Konrad Rzeszutek Wilk wrote:
> I don't remember if it was suggested to hpa/ingo/tglx whether we could
> provide another 'struct apic' that would be Xen specific and the apic->probe()
> would either provide a struct mostly filled with dummy functions that return
> nothing, or the Xen apic->probe() function would over-write the current
> 'apic->read,write, etc' with the xen dummy functions.

I still maintain the "proper fix" is to just turn off the APIC CPU
capability.  There is no local apic, and trying to pretend otherwise
just leads to a mass of hacks.

But of course, that's not particularly easy in practice...


Xen-devel mailing list