mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Sheng Yang <sheng.yang@intel.com>
Cc: Avi Kivity <avi@qumranet.com>,
	linux-kernel@vger.kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
	Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [RFC][PATCH 0/2] x86: Add "virt flags"
Date: Mon, 8 Sep 2008 16:09:39 +0200	[thread overview]
Message-ID: <20080908140939.GH11993@elte.hu> (raw)
In-Reply-To: <12208705553277-git-send-email-sheng.yang@intel.com>


* Sheng Yang <sheng.yang@intel.com> wrote:

> Hi, Ingo
> 
> (sorry for former noises, I mistake the address... Report to lkml) 
> I've sent this patchset before, but got no comments from upstream at 
> that time.  So I'd like to resend this.
> 
> The virt flags is used for the important hardware virtualization 
> features, like EPT of incoming Nehalem. Because the feature 
> availability are read from MSRs, and I think virtualization features 
> should not at the same level as "vmx", so I added a new flags catagory 
> here.
> 
> But I still have concern, for this may broke some not that reliable 
> userspace programs. So Avi suggested that we can add more fields to 
> flags rather than a new catagory.  What's your opinion? We indeed need 
> a generic user visible way to tell the HW virtualization features.

hm, i think extending the already existing flags category sounds like a 
better solution than the separate virtual CPU flags line in 
/proc/cpuinfo. We already have self-invented flag entries (such as 
X86_FEATURE_NOPL), and adding more for virtualization would be quite 
natural to do, as long as it's reasonably close to the meaning of a 'CPU 
feature'.

Peter, what would be your preference?

	Ingo

  parent reply	other threads:[~2008-09-08 14:10 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-08 10:42 Sheng Yang
2008-09-08 10:42 ` [PATCH 1/2] x86: Move VMX MSRs to msr-index.h Sheng Yang
2008-09-09 13:47   ` Avi Kivity
2008-09-10 10:44     ` Yang, Sheng
2008-09-10 14:30       ` Avi Kivity
2008-09-11  1:56         ` Yang, Sheng
2008-09-08 10:42 ` [PATCH 2/2] x86: Add "virt flags" in /proc/cpuinfo Sheng Yang
2008-09-08 14:04 ` [RFC][PATCH 0/2] x86: Add "virt flags" Andi Kleen
2008-09-08 14:09 ` Ingo Molnar [this message]
2008-09-08 15:30   ` H. Peter Anvin
2008-09-08 17:17     ` H. Peter Anvin
2008-09-09  3:32       ` 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=20080908140939.GH11993@elte.hu \
    --to=mingo@elte.hu \
    --cc=avi@qumranet.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sheng.yang@intel.com \
    --cc=tglx@linutronix.de \
    /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

all inboxes | Powered by JetHome®