public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@qumranet.com>
To: "Yang, Sheng" <sheng.yang@intel.com>
Cc: kvm@vger.kernel.org
Subject: Re: [PATCH 1/4] KVM: Report hardware virtualization features
Date: Sun, 22 Jun 2008 09:49:51 +0300	[thread overview]
Message-ID: <485DF60F.4070907@qumranet.com> (raw)
In-Reply-To: <200806191842.56275.sheng.yang@intel.com>

Yang, Sheng wrote:
> From f02d2ccf01e8671d2da517f14a908d1df1cc42ad Mon Sep 17 00:00:00 2001
> From: Sheng Yang <sheng.yang@intel.com>
> Date: Thu, 19 Jun 2008 18:41:26 +0800
> Subject: [PATCH] KVM: Report hardware virtualization features
>
> The hardware virtualization technology evolves very fast. But currently it's
> hard to tell if your CPU support certain kind of HW technology without dig 
> into the source code.
>
> The patch introduced a virtual file called "kvm_hw_feature_report" under
> /sys/devices/system/kvm/kvm0 to show the mainly important current hardware
> virtualization feature, then it's pretty easy to tell if your CPU support
> some advanced virtualization technology now.
>
>   

Yes, this is definitely helpful.  However, I think that users will 
expect cpu flags under /proc/cpuinfo.

Perhaps we should add a new line 'virt flags' to /proc/cpuinfo?  I think 
all the features are reported using msrs, so it can be done from 
arch/x86/kernel/cpu/proc.c without involving kvm at all.

-- 
Do not meddle in the internals of kernels, for they are subtle and quick to panic.


  reply	other threads:[~2008-06-22  6:49 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-19 10:42 [PATCH 1/4] KVM: Report hardware virtualization features Yang, Sheng
2008-06-22  6:49 ` Avi Kivity [this message]
2008-06-22 12:18   ` Dor Laor
2008-06-22 12:21     ` Avi Kivity
2008-06-23  1:46       ` Yang, Sheng
2008-06-23  2:40         ` Avi Kivity
2008-06-23  3:01           ` Yang, Sheng
2008-06-23  9:47             ` Yang, Sheng

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=485DF60F.4070907@qumranet.com \
    --to=avi@qumranet.com \
    --cc=kvm@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox