From mboxrd@z Thu Jan 1 00:00:00 1970 From: Gleb Natapov Subject: Re: [PATCH v5] enable x2APIC without interrupt remapping under KVM Date: Sat, 4 Jul 2009 12:55:56 +0300 Message-ID: <20090704095556.GB24641@redhat.com> References: <20090701133007.GC27539@redhat.com> <1246482017.27006.10670.camel@localhost.localdomain> <20090703082905.GF21833@elte.hu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Ingo Molnar , Suresh Siddha , "linux-kernel@vger.kernel.org" , Sheng Yang , "kvm@vger.kernel.org" , "avi@redhat.com" To: "Eric W. Biederman" Return-path: Received: from mx2.redhat.com ([66.187.237.31]:44483 "EHLO mx2.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751843AbZGDJ4L (ORCPT ); Sat, 4 Jul 2009 05:56:11 -0400 Content-Disposition: inline In-Reply-To: Sender: kvm-owner@vger.kernel.org List-ID: On Sat, Jul 04, 2009 at 02:35:30AM -0700, Eric W. Biederman wrote: > Ingo Molnar writes: > > > * Suresh Siddha wrote: > > > >> On Wed, 2009-07-01 at 06:30 -0700, Gleb Natapov 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 > >> > >> Acked-by: Suresh Siddha > > > > Now, since this affects core x86 APIC code non-trivially so should > > submitted to and go via the x86 tree. (Can prepare a special branch > > with just this change if KVM tree wants/needs to pull it before > > v2.6.32.) > > Please don't separate the x2apic code from the dmar code for this > reason. > > Supporting hotplug cpus with ioapics is torture. > What is the connection between this patch and cpu hotplug? -- Gleb.