From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: xen-devel@lists.xensource.com, andrew.thomas@oracle.com,
Jan Beulich <JBeulich@novell.com>,
Ian Campbell <Ian.Campbell@eu.citrix.com>,
keir.xen@gmail.com, swente@infinitumb.de,
gianni.tedesco@citrix.com
Subject: Re: L1[0x1fb] = 0000000000000000 which faults on one type of machine but on another works?
Date: Thu, 17 Mar 2011 10:21:37 -0700 [thread overview]
Message-ID: <4D824321.6010206@goop.org> (raw)
In-Reply-To: <20110317164143.GA26392@dumpdata.com>
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...
J
next prev parent reply other threads:[~2011-03-17 17:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-16 22:19 L1[0x1fb] = 0000000000000000 which faults on one type of machine but on another works? Konrad Rzeszutek Wilk
2011-03-16 22:32 ` Keir Fraser
2011-03-17 10:25 ` Jan Beulich
2011-03-17 15:52 ` Konrad Rzeszutek Wilk
2011-03-17 16:12 ` Konrad Rzeszutek Wilk
2011-03-17 16:12 ` Jan Beulich
2011-03-17 16:41 ` Konrad Rzeszutek Wilk
2011-03-17 17:21 ` Jeremy Fitzhardinge [this message]
2011-03-17 19:56 ` [PATCH] xen/apic: Provide an 'apic_xen' to set the override the apic->[read|write] for all cases Konrad Rzeszutek Wilk
2011-03-22 13:10 ` L1[0x1fb] = 0000000000000000 which faults on one type of machine but on another works? Gianni Tedesco
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4D824321.6010206@goop.org \
--to=jeremy@goop.org \
--cc=Ian.Campbell@eu.citrix.com \
--cc=JBeulich@novell.com \
--cc=andrew.thomas@oracle.com \
--cc=gianni.tedesco@citrix.com \
--cc=keir.xen@gmail.com \
--cc=konrad.wilk@oracle.com \
--cc=swente@infinitumb.de \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.