From mboxrd@z Thu Jan 1 00:00:00 1970 From: Sheng Yang Subject: Re: [PATCH 0/1] x2apic implementation for kvm Date: Mon, 25 May 2009 14:08:26 +0800 Message-ID: <200905251408.26870.sheng@linux.intel.com> References: <1242927475-6140-1-git-send-email-gleb@redhat.com> Mime-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Cc: Gleb Natapov To: kvm@vger.kernel.org Return-path: Received: from mga09.intel.com ([134.134.136.24]:9870 "EHLO mga09.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751540AbZEYGHB (ORCPT ); Mon, 25 May 2009 02:07:01 -0400 In-Reply-To: <1242927475-6140-1-git-send-email-gleb@redhat.com> Content-Disposition: inline Sender: kvm-owner@vger.kernel.org List-ID: On Friday 22 May 2009 01:37:53 Gleb Natapov wrote: > This is implementation of x2apic for KVM that I wrote a while ago. > Unfortunately there is no guest that can take advantage of it since > Linux doesn't (yet?) use x2apic if interrupt remapping is not enabled > and I don't feel like implement interrupt remapping device :) > > Re-based to latest kvm tree for your viewing pleasure and feedback. Yeah... x2apic is for interrupt remapping, and interrupt remapping is for VT-d engine. So if we don't want to virtualize VT-d engine and interrupt remapping, x2apic is useless for the guest... And VT-d engine(and related things) virtualization is far from our scope now... Thanks... -- regards Yang, Sheng