From: "Woodhouse, David" <david.woodhouse@intel.com>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: "Song, Youquan" <youquan.song@intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"mingo@elte.hu" <mingo@elte.hu>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"hpa@zytor.com" <hpa@zytor.com>,
"hpa@linux.intel.com" <hpa@linux.intel.com>,
"Kay, Allen M" <allen.m.kay@intel.com>,
"Siddha, Suresh B" <suresh.b.siddha@intel.com>,
"Liu, Kent" <kent.liu@intel.com>,
Youquan Song <youquan.song@linux.intel.com>
Subject: Re: [PATCH v2] x86, vt-d: enable x2apic opt out
Date: Wed, 18 May 2011 23:58:57 +0100 [thread overview]
Message-ID: <1305759537.28691.39.camel@i7.infradead.org> (raw)
In-Reply-To: <1305577977.3146.112.camel@x201>
[-- Attachment #1: Type: text/plain, Size: 1459 bytes --]
On Mon, 2011-05-16 at 21:32 +0100, Alex Williamson wrote:
>
> > Is this just a workaround for a crappy BIOS? What is the *actual* reason
> > for wanting to disable x2apic?
>
> Just a guess, but the OEM probably hasn't updated their SMI handlers to
> understand x2apic yet and won't before the product ships because some
> other OS doesn't bother to use x2apic.
But I think we'll still use x2apic if interrupt remapping isn't enabled
(for example if VT-d is disabled in the BIOS and the whole DMAR table is
absent), or if we're booted with 'iommu=off' or indeed if the
distribution vendor has hacked the kernel so that iommu=off is the
*default*, because they've seen so many broken BIOSes.
AFAICT although CONFIG_X86_X2APIC depends on CONFIG_INTR_REMAP, we can
still enable x2apic at runtime if interrupt remapping is not operating?
We end up hitting this code in enable_IR_x2apic():
if (!ret) {
/* IR is required if there is APIC ID > 255 even when running
* under KVM
*/
if (max_physical_apicid > 255 ||
!hypervisor_x2apic_available())
goto nox2apic;
/*
* without IR all CPUs can be addressed by IOAPIC/MSI
* only in physical mode
*/
x2apic_force_phys();
}
So if that *is* the reason, this doesn't seem like a viable solution.
--
David Woodhouse Open Source Technology Centre
David.Woodhouse@intel.com Intel Corporation
[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 6242 bytes --]
next prev parent reply other threads:[~2011-05-18 22:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-14 7:06 Youquan Song
2011-05-11 15:07 ` Woodhouse, David
2011-05-12 3:39 ` Youquan Song
2011-05-11 15:39 ` David Woodhouse
2011-05-11 22:38 ` Valdis.Kletnieks
2011-05-16 20:32 ` Alex Williamson
2011-05-17 9:49 ` Woodhouse, David
2011-05-17 12:50 ` Alex Williamson
2011-05-18 22:58 ` Woodhouse, David [this message]
2011-05-19 5:43 ` Alex Williamson
2011-05-11 17:21 ` Woodhouse, David
2011-05-12 1:52 ` Youquan Song
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=1305759537.28691.39.camel@i7.infradead.org \
--to=david.woodhouse@intel.com \
--cc=akpm@linux-foundation.org \
--cc=alex.williamson@redhat.com \
--cc=allen.m.kay@intel.com \
--cc=hpa@linux.intel.com \
--cc=hpa@zytor.com \
--cc=kent.liu@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=suresh.b.siddha@intel.com \
--cc=tglx@linutronix.de \
--cc=youquan.song@intel.com \
--cc=youquan.song@linux.intel.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
all inboxes | Powered by JetHome®