public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Gleb Natapov <gleb@redhat.com>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Suresh Siddha <suresh.b.siddha@intel.com>,
	Sheng Yang <sheng@linux.intel.com>,
	"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
	"avi@redhat.com" <avi@redhat.com>
Subject: Re: [PATCH v3] enable x2APIC without interrupt remapping under KVM
Date: Tue, 30 Jun 2009 22:03:07 +0300	[thread overview]
Message-ID: <20090630190307.GE8122@redhat.com> (raw)
In-Reply-To: <m1eit1acxl.fsf@fess.ebiederm.org>

On Tue, Jun 30, 2009 at 09:44:54AM -0700, Eric W. Biederman wrote:
> Gleb Natapov <gleb@redhat.com> writes:
> 
> > On Tue, Jun 30, 2009 at 02:24:05AM -0700, Eric W. Biederman wrote:
> >> Gleb Natapov <gleb@redhat.com> writes:
> >> 
> >> > 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).
> >> 
> >> 
> >> How common is hotplug hardware in kvm?  In particular hotplug cpus?
> >> 
> > It works for Linux guests.
> 
> >
> >> To support that seriously you need interrupt remapping.
> >> 
> > Can you explain why?
> 
> Because ioapics don't fully function according to spec,
> and the interrupt code on the hotplug path is a horrible
> terrible broken hack for ioapics.
> 
Considering that interrupt remapping is fairly new feature
are you saying that hotplug (pci and cpu) on x86 is a horrible
hack on Linux?

> It is better than nothing but it certainly is not something
> I would expect to work all of the time.
> 
Because of horrible code or non-complaint ioapic implementation out
there? If later this is not a big issue for KVM.

> Interrupt remapping is the one case where we have hardware
> that works according to spec and that works reasonably well.
> 
I am sure when there was only one ioapic implementation in existence
it worked according to a spec (and if not spec was changed :)) Give
interrupt remapping some time and than we will see how above statement
holds.

--
			Gleb.

  parent reply	other threads:[~2009-06-30 19:03 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-29 13:29 [PATCH v3] enable x2APIC without interrupt remapping under KVM Gleb Natapov
2009-06-29 14:58 ` Suresh Siddha
2009-06-29 15:10   ` Gleb Natapov
2009-06-29 15:15     ` Suresh Siddha
2009-06-29 15:45       ` Gleb Natapov
2009-06-30  9:24 ` Eric W. Biederman
2009-06-30  9:26   ` Gleb Natapov
2009-06-30 16:44     ` Eric W. Biederman
2009-06-30 17:12       ` Avi Kivity
2009-06-30 19:08         ` Eric W. Biederman
2009-06-30 19:16           ` Avi Kivity
2009-06-30 19:36             ` Eric W. Biederman
2009-07-01  8:30               ` Avi Kivity
2009-07-01 13:31                 ` Eric W. Biederman
2009-07-01 22:53               ` Suresh Siddha
2009-07-02  0:17                 ` Eric W. Biederman
2009-07-07 16:14                   ` Suresh Siddha
2009-07-10 20:29                     ` Eric W. Biederman
2009-06-30 19:03       ` Gleb Natapov [this message]
2009-06-30 19:43         ` Eric W. Biederman

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=20090630190307.GE8122@redhat.com \
    --to=gleb@redhat.com \
    --cc=avi@redhat.com \
    --cc=ebiederm@xmission.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