linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andi Kleen <andi@firstfloor.org>
To: Sheng Yang <sheng.yang@intel.com>
Cc: Ingo Molnar <mingo@elte.hu>, Avi Kivity <avi@qumranet.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [RFC][PATCH 0/2] x86: Add "virt flags"
Date: Mon, 08 Sep 2008 16:04:23 +0200	[thread overview]
Message-ID: <87y722u42g.fsf@basil.nowhere.org> (raw)
In-Reply-To: <12208705553277-git-send-email-sheng.yang@intel.com> (Sheng Yang's message of "Mon,  8 Sep 2008 18:42:33 +0800")

Sheng Yang <sheng.yang@intel.com> writes:
>
> 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.


FWIW when I added the "power management:" flags back then for the
64bit kernel I didn't get any reports of user programs breaking. Also
some other fields got added like cpu cores or initial apicid etc. and
that also didn't lead to breakage. So adding new lines to cpuinfo
should be ok.

-Andi
-- 
ak@linux.intel.com

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

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-08 10:42 [RFC][PATCH 0/2] x86: Add "virt flags" 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 ` Andi Kleen [this message]
2008-09-08 14:09 ` [RFC][PATCH 0/2] x86: Add "virt flags" Ingo Molnar
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=87y722u42g.fsf@basil.nowhere.org \
    --to=andi@firstfloor.org \
    --cc=avi@qumranet.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --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;
as well as URLs for NNTP newsgroup(s).