From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Jan Beulich <JBeulich@novell.com>
Cc: Jeremy Fitzhardinge <jeremy@goop.org>,
xen-devel@lists.xensource.com, andrew.thomas@oracle.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 12:41:43 -0400 [thread overview]
Message-ID: <20110317164143.GA26392@dumpdata.com> (raw)
In-Reply-To: <4D82411002000078000371D8@vpn.id2.novell.com>
On Thu, Mar 17, 2011 at 04:12:48PM +0000, Jan Beulich wrote:
> >>> On 17.03.11 at 16:52, Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> wrote:
> > 2.6.38 fixes this by allowing in acpi_register_lapic_address, the
> > the set_fixmap_nocache(FIX_APIC_BASE, address) to be called and we
> > can provide it with a dummy page and native_apic_read can happily
> > read from that fake page.
>
> I wonder whether that's going to be appropriate in cases...
If you boot the 2.6.38 it works, but it does provide these ugly and untrue values:
0.000000] ACPI: IOAPIC (id[0x0f] address[0xfec00000] gsi_base[0])
[ 0.000000] IOAPIC[0]: apic_id 15, version 255, address 0xfec00000, GSI 0-255
[ 0.000000] ACPI: IOAPIC (id[0x0e] address[0xfec01000] gsi_base[36])
[ 0.000000] IOAPIC[1]: apic_id 14, version 255, address 0xfec01000, GSI 36-291
[ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
[ 0.000000] Int: type 0, pol 0, trig 0, bus 00, IRQ 00, APIC ID f, APIC INT 02
[ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 8 global_irq 8 low edge)
[ 0.000000] Int: type 0, pol 3, trig 1, bus 00, IRQ 08, APIC ID f, APIC INT 08
[ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 14 global_irq 14 low edge)
[ 0.000000] Int: type 0, pol 3, trig 1, bus 00, IRQ 0e, APIC ID f, APIC INT 0e
[ 0.000000] Int: type 0, pol 3, trig 3, bus 00, IRQ 09, APIC ID f, APIC INT 09
[ 0.000000] ACPI: IRQ0 used by override.
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.
However we seem to achieve this already by providing a dummy page that
is read/writen to by the native_apic_[read|write].
next prev parent reply other threads:[~2011-03-17 16:41 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 [this message]
2011-03-17 17:21 ` Jeremy Fitzhardinge
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=20110317164143.GA26392@dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=Ian.Campbell@eu.citrix.com \
--cc=JBeulich@novell.com \
--cc=andrew.thomas@oracle.com \
--cc=gianni.tedesco@citrix.com \
--cc=jeremy@goop.org \
--cc=keir.xen@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).