From: Ingo Molnar <mingo@elte.hu>
To: Gleb Natapov <gleb@redhat.com>
Cc: linux-kernel@vger.kernel.org, Sheng Yang <sheng@linux.intel.com>,
kvm@vger.kernel.org, avi@redhat.com, "Siddha,
Suresh B" <suresh.b.siddha@intel.com>
Subject: Re: [PATCH v2] enable x2APIC without interrupt remapping under KVM
Date: Mon, 29 Jun 2009 12:22:35 +0200 [thread overview]
Message-ID: <20090629102235.GA15372@elte.hu> (raw)
In-Reply-To: <20090629100837.GW20289@redhat.com>
* Gleb Natapov <gleb@redhat.com> wrote:
> KVM would like to provide x2APIC interface to a guest without emulating
> interrupt remapping device. The reason KVM prefers guest to use x2APIC
> is that x2APIC interface is better virtualizable and provides better
> performance than mmio xAPIC interface:
>
> - msr exits are faster than mmio (no page table walk, emulation)
> - no need to read back ICR to look at the busy bit
> - one 64 bit ICR write instead of two 32 bit writes
> - shared code with the Hyper-V paravirt interface
>
> Included patch changes x2APIC enabling logic to enable it even if IR
> initialization failed, but kernel runs under KVM and no apic id is
> greater than 255 (if there is one spec requires BIOS to move to x2apic
> mode before starting an OS).
>
> Signed-off-by: Gleb Natapov <gleb@redhat.com>
> ---
>
> v2:
> Add help message to Kconfig
> Force physical mode if IR is not available.
>
> diff --git a/arch/x86/Kconfig b/arch/x86/Kconfig
> index d1430ef..3e5b6ea 100644
> --- a/arch/x86/Kconfig
> +++ b/arch/x86/Kconfig
> @@ -260,12 +260,15 @@ config SMP
>
> config X86_X2APIC
> bool "Support x2apic"
> - depends on X86_LOCAL_APIC && X86_64 && INTR_REMAP
> + depends on X86_LOCAL_APIC && X86_64
Have you tried to build this with X86_X2APIC set but INTR_REMAP
disabled?
Ingo
next prev parent reply other threads:[~2009-06-29 10:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-29 10:08 [PATCH v2] enable x2APIC without interrupt remapping under KVM Gleb Natapov
2009-06-29 10:22 ` Ingo Molnar [this message]
2009-06-29 10:33 ` Gleb Natapov
2009-06-29 10:46 ` Suresh Siddha
2009-06-29 11:25 ` Gleb Natapov
2009-06-29 11:48 ` Suresh Siddha
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=20090629102235.GA15372@elte.hu \
--to=mingo@elte.hu \
--cc=avi@redhat.com \
--cc=gleb@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sheng@linux.intel.com \
--cc=suresh.b.siddha@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