From: Rik van Riel <riel@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Liu, Jinsong" <jinsong.liu@intel.com>,
Eduardo Habkost <ehabkost@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 2/2] Expose tsc deadline timer cpuid to guest
Date: Mon, 19 Mar 2012 18:35:53 -0400 [thread overview]
Message-ID: <4F67B4C9.3010502@redhat.com> (raw)
In-Reply-To: <DE8DF0795D48FD4CA783C40EC82923350D7271@SHSMSX101.ccr.corp.intel.com>
On 03/09/2012 01:27 PM, Liu, Jinsong wrote:
> As for 'tsc deadline' feature exposing, my patch (as attached) just obey qemu general cpuid exposing method, and also satisfied your target I think.
One question.
Why is TSC_DEADLINE not exposed in the cpuid allowed feature
bits in do_cpuid_ent() in arch/x86/kvm/x86.c ?
/* cpuid 1.ecx */
const u32 kvm_supported_word4_x86_features =
F(XMM3) | F(PCLMULQDQ) | 0 /* DTES64, MONITOR */ |
0 /* DS-CPL, VMX, SMX, EST */ |
0 /* TM2 */ | F(SSSE3) | 0 /* CNXT-ID */ | 0 /*
Reserved */ |
F(FMA) | F(CX16) | 0 /* xTPR Update, PDCM */ |
0 /* Reserved, DCA */ | F(XMM4_1) |
F(XMM4_2) | F(X2APIC) | F(MOVBE) | F(POPCNT) |
0 /* Reserved*/ | F(AES) | F(XSAVE) | 0 /* OSXSAVE */ |
F(AVX) |
F(F16C) | F(RDRAND);
Would it make sense to expose F(TSC_DEADLINE) above?
Or is there something truly special about tsc deadline
that means it should be different from everything else?
--
All rights reversed
next prev parent reply other threads:[~2012-03-19 22:36 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-28 21:55 [Qemu-devel] [PATCH 2/2] Expose tsc deadline timer cpuid to guest Liu, Jinsong
2012-01-04 16:48 ` Jan Kiszka
2012-01-05 20:07 ` Liu, Jinsong
2012-01-05 20:34 ` Jan Kiszka
2012-01-07 18:23 ` Liu, Jinsong
2012-01-08 21:24 ` Jan Kiszka
2012-02-27 16:05 ` Liu, Jinsong
2012-02-27 17:18 ` Jan Kiszka
2012-02-28 10:30 ` Liu, Jinsong
2012-03-06 7:49 ` Liu, Jinsong
2012-03-06 10:14 ` Jan Kiszka
2012-03-09 18:27 ` Liu, Jinsong
2012-03-09 18:56 ` Jan Kiszka
2012-03-09 19:09 ` Liu, Jinsong
2012-03-09 20:52 ` Jan Kiszka
2012-03-10 1:07 ` Andreas Färber
2012-03-11 18:54 ` Liu, Jinsong
2012-03-12 17:21 ` Eduardo Habkost
2012-03-25 8:51 ` Liu, Jinsong
2012-03-09 19:29 ` Liu, Jinsong
2012-03-19 22:35 ` Rik van Riel [this message]
2012-03-20 12:53 ` Liu, Jinsong
2012-03-20 13:33 ` Eduardo Habkost
2012-03-23 3:49 ` Liu, Jinsong
2012-03-23 13:46 ` Eduardo Habkost
2012-03-23 14:17 ` Liu, Jinsong
[not found] <20120419200331.GB19463@otherpad.lan.raisama.net>
[not found] ` <4F913696.20301@siemens.com>
[not found] ` <20120420150005.GW3169@otherpad.lan.raisama.net>
[not found] ` <4F917E75.2080003@siemens.com>
[not found] ` <20120420153656.GX3169@otherpad.lan.raisama.net>
[not found] ` <4F926086.3020307@web.de>
[not found] ` <20120423144818.GA3169@otherpad.lan.raisama.net>
[not found] ` <4F9583DD.10807@siemens.com>
[not found] ` <20120423200214.GG3169@otherpad.lan.raisama.net>
[not found] ` <4F96CF9F.9060302@siemens.com>
[not found] ` <20120424171925.GT3169@otherpad.lan.raisama.net>
2012-06-14 19:02 ` Liu, Jinsong
2012-06-14 19:12 ` Eduardo Habkost
2012-06-14 19:18 ` Liu, Jinsong
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=4F67B4C9.3010502@redhat.com \
--to=riel@redhat.com \
--cc=ehabkost@redhat.com \
--cc=jinsong.liu@intel.com \
--cc=qemu-devel@nongnu.org \
/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;
as well as URLs for NNTP newsgroup(s).