From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: xen-devel <xen-devel@lists.xen.org>
Subject: Re: IO-APIC pages being accessed by ACPI methods
Date: Tue, 12 Mar 2013 08:51:20 -0400 [thread overview]
Message-ID: <20130312125120.GA15743@phenom.dumpdata.com> (raw)
In-Reply-To: <513F0AB802000078000C4D23@nat28.tlf.novell.com>
On Tue, Mar 12, 2013 at 10:00:08AM +0000, Jan Beulich wrote:
> All,
>
> considering the non-negligible number of systems where firmware
> has ACPI methods that reference IO-APIC pages (causing
> method execution to fail on non-pvops Dom0, and crashing pvops),
Hmm. I recall only seeing one issue on xen-devel with an IBM box.
Were there more?
> I'm wondering whether we shouldn't relax treatment of IO-APIC
> MMIO space by moving it from the completely access denied state
> that it's currently in (due to construct_dom0() having
>
> /* I/O APICs. */
> for ( i = 0; i < nr_ioapics; i++ )
> {
> mfn = paddr_to_pfn(mp_ioapics[i].mpc_apicaddr);
> if ( smp_found_config )
> rc |= iomem_deny_access(dom0, mfn, mfn);
> }
>
> ) to allowing read access, and dropping writes (through the MMIO
> R/O emulation added for specific PCI devices during 4.2
> development).
>
> Afaict this ought to be safe, as no reads of currently defined
> IO-APIC registers have side effects. But of course we don't know
> what extensions there might be to come.
>
> If we do so (and perhaps even independently of this) we probably
> ought to enforce consistent cachability attributes on the secondary
> mappings Dom0 then is able to establish - either by further
> modifying the requested flags, or by outright denying mapping
> requests that aren't specifying UC. While the latter would be my
> preference and would work for the MMCFG case, the ACPI case
> described here wouldn't be covered - Linux'es ACPICA creates
> cachable mappings regardless of whether a SystemMemory is
> RAM or MMIO (thus risking problems even on native).
Eww. That looks like a bug in the ACPICA? Perhaps my recollection
is incorrect but shouldn't MMIO regions mostly be UC. Only drivers
that know what they are doing (say graphic cards) can choose to
set that to WC?
Or by cachable mappings you mean WB?
>
> Opinions appreciated,
> Jan
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
>
next prev parent reply other threads:[~2013-03-12 12:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-12 10:00 IO-APIC pages being accessed by ACPI methods Jan Beulich
2013-03-12 10:07 ` Jan Beulich
2013-03-12 11:42 ` Andrew Cooper
2013-03-12 12:43 ` Jan Beulich
2013-03-12 12:51 ` Konrad Rzeszutek Wilk [this message]
2013-03-12 13:14 ` Jan Beulich
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=20130312125120.GA15743@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=JBeulich@suse.com \
--cc=xen-devel@lists.xen.org \
/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.