[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <200806271131.38540.sheng.yang@intel.com>
Date: Fri, 27 Jun 2008 11:31:38 +0800
From: "Yang, Sheng" <sheng.yang@...el.com>
To: Jeremy Fitzhardinge <jeremy@...p.org>
Cc: kvm@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 2/2] x86: Add "virt flag" in /proc/cpuinfo
On Friday 27 June 2008 11:26:15 Jeremy Fitzhardinge wrote:
> Yang, Sheng wrote:
> > From 54b1bb9fe5d2fe40fc047b43dd4e1a480d41a977 Mon Sep 17 00:00:00
> > 2001 From: Sheng Yang <sheng.yang@...el.com>
> > Date: Tue, 24 Jun 2008 17:03:17 +0800
> > Subject: [PATCH] x86: Add "virt flag" in /proc/cpuinfo
> >
> > The hardware virtualization technology evolves very fast. But
> > currently it's hard to tell if your CPU support a certain kind of
> > HW technology without dig into the source code.
> >
> > The patch add a new item under /proc/cpuinfo, named "virt flag".
> > The "virt flag" got the similar function as "flag". It is used to
> > indicate what features does this CPU supported. It don't cover
> > all features but only the important ones.
>
> A cpu feature is a cpu feature. I'd prefer to see all this in
> "flags:".
>
> J
But I think (as I said before)
1. The standard flag covered upper level of cpu capability, they are
covered by CPUID. And virt flag was enabled by vmx/svm (we can leave
it blank also), and covered by MSR. It's very different.
2. If we add virtual feature to standard flag, I am afraid it would
grow too fast, though we just add some key feature to it.
--
Thanks
Yang, Sheng
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists