From: "H. Peter Anvin" <h.peter.anvin@intel.com>
To: Jan Kiszka <jan.kiszka@web.de>
Cc: Avi Kivity <avi@redhat.com>,
Gregory Haskins <gregory.haskins@gmail.com>,
kvm-devel <kvm@vger.kernel.org>,
RT <linux-rt-users@vger.kernel.org>,
"Yang, Sheng" <sheng.yang@intel.com>
Subject: Re: Host latency peaks due to kvm-intel
Date: Sun, 26 Jul 2009 12:16:27 -0700 [thread overview]
Message-ID: <4A6CAB8B.4080706@intel.com> (raw)
In-Reply-To: <4A6AD69E.7030201@web.de>
Jan Kiszka wrote:
> Avi Kivity wrote:
>> On 07/24/2009 12:41 PM, Jan Kiszka wrote:
>>> I vaguely recall that someone promised to add a feature reporting
>>> facility for all those nice things, modern VM-extensions may or may not
>>> support (something like or even an extension of /proc/cpuinfo). What is
>>> the state of this plan? Would be specifically interesting for Intel CPUs
>>> as there seem to be many of them out there with restrictions for special
>>> use cases - like real-time.
>>>
>> Newer kernels do report some vmx features (like flexpriority) in
>> /proc/cpuinfo but not all.
>>
>
> Ah, nice. Then we just need this?
>
Fine with me.
Acked-by: H. Peter Anvin <hpa@zytor.com>
However, I guess the real question if we shouldn't export ALL VMX
features in a consistent way instead?
-hpa
next prev parent reply other threads:[~2009-07-26 19:16 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-23 18:07 Host latency peaks due to kvm-intel Jan Kiszka
2009-07-23 19:43 ` Gregory Haskins
2009-07-24 9:41 ` Jan Kiszka
2009-07-24 12:01 ` Gregory Haskins
2009-07-25 8:15 ` Avi Kivity
2009-07-25 9:55 ` Jan Kiszka
2009-07-25 13:27 ` Avi Kivity
2009-07-26 14:23 ` Jan Kiszka
2009-07-26 19:16 ` H. Peter Anvin [this message]
2009-07-27 1:11 ` Yang, Sheng
2009-07-27 9:08 ` cpuinfo and HVM features (was: Host latency peaks due to kvm-intel) Jan Kiszka
2009-07-27 9:29 ` Yang, Sheng
2009-07-27 10:31 ` cpuinfo and HVM features Avi Kivity
2009-07-25 14:52 ` Host latency peaks due to kvm-intel Avi Kivity
2009-07-26 10:34 ` Sujit Karataparambil
2009-07-26 14:34 ` Jan Kiszka
2009-07-26 14:45 ` Avi Kivity
2009-07-26 14:52 ` Jan Kiszka
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=4A6CAB8B.4080706@intel.com \
--to=h.peter.anvin@intel.com \
--cc=avi@redhat.com \
--cc=gregory.haskins@gmail.com \
--cc=jan.kiszka@web.de \
--cc=kvm@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=sheng.yang@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.