From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jan Kiszka Subject: Re: [PATCH 2/2] Expose tsc deadline timer cpuid to guest Date: Fri, 20 Apr 2012 12:12:38 +0200 Message-ID: <4F913696.20301@siemens.com> References: <4F55E39F.6020608@siemens.com> <4F67B4C9.3010502@redhat.com> <20120320133314.GV9375@otherpad.lan.raisama.net> <20120323134607.GF9375@otherpad.lan.raisama.net> <20120419200331.GB19463@otherpad.lan.raisama.net> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: "Liu, Jinsong" , "qemu-devel@nongnu.org" , "kvm@vger.kernel.org" , Avi Kivity To: Eduardo Habkost Return-path: In-Reply-To: <20120419200331.GB19463@otherpad.lan.raisama.net> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: qemu-devel-bounces+gceq-qemu-devel=gmane.org@nongnu.org Sender: qemu-devel-bounces+gceq-qemu-devel=gmane.org@nongnu.org List-Id: kvm.vger.kernel.org On 2012-04-19 22:03, Eduardo Habkost wrote: > Jan/Avi: ping? > > I would like to get this ABI detail clarified so it can be implemented > the right way on Qemu and KVM. > > My proposal is to simply add tsc-deadline to the data returned by > GET_SUPPORTED_CPUID, making KVM_CAP_TSC_DEADLINE_TIMER unnecessary. > IIRC, there were problems with this model to exclude that the feature gets reported this way without ensuring that in-kernel irqchip is actually activated. Please browse the discussions, it should be documented there. Jan -- Siemens AG, Corporate Technology, CT T DE IT 1 Corporate Competence Center Embedded Linux