mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Chris Wright <chrisw@sous-sol.org>
To: Andi Kleen <ak@suse.de>
Cc: Chris Wright <chrisw@sous-sol.org>,
	virtualization@lists.osdl.org, Zachary Amsden <zach@vmware.com>,
	Linus Torvalds <torvalds@osdl.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Xen-devel <xen-devel@lists.xensource.com>,
	Andrew Morton <akpm@osdl.org>, Dan Hecht <dhecht@vmware.com>,
	Dan Arai <arai@vmware.com>, Anne Holler <anne@vmware.com>,
	Pratap Subrahmanyam <pratap@vmware.com>,
	Christopher Li <chrisl@vmware.com>,
	Joshua LeVasseur <jtl@ira.uka.de>, Chris Wright <chrisw@osdl.org>,
	Rik Van Riel <riel@redhat.com>, Jyothy Reddy <jreddy@vmware.com>,
	Jack Lo <jlo@vmware.com>, Kip Macy <kmacy@fsmware.com>,
	Jan Beulich <jbeulich@novell.com>,
	Ky Srinivasan <ksrinivasan@novell.com>,
	Wim Coekaerts <wim.coekaerts@oracle.com>,
	Leendert van Doorn <leendert@watson.ibm.com>
Subject: Re: [RFC, PATCH 1/24] i386 Vmi documentation
Date: Wed, 22 Mar 2006 13:57:32 -0800	[thread overview]
Message-ID: <20060322215732.GL15997@sorel.sous-sol.org> (raw)
In-Reply-To: <200603222213.45910.ak@suse.de>

* Andi Kleen (ak@suse.de) wrote:
> Even then it's useless for many flags because any user program can (and will) 
> call CPUID directly. 

Yes, doesn't handle userspace at all.  It's useful only to get coherent
view of flags in kernel.  Right now, for example, Xen goes in and
basically masks off flags retroactively which is not that nice either.

thanks,
-chris

  reply	other threads:[~2006-03-22 21:57 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200603131759.k2DHxeep005627@zach-dev.vmware.com>
     [not found] ` <20060313224902.GD12807@sorel.sous-sol.org>
2006-03-14  0:00   ` Zachary Amsden
2006-03-14 21:27     ` Chris Wright
     [not found]       ` <441743BD.1070108@vmware.com>
2006-03-15  2:57         ` Chris Wright
2006-03-15  5:44           ` Zachary Amsden
2006-03-15 22:56           ` Daniel Arai
2006-03-16  1:16       ` Chris Wright
2006-03-16  3:40         ` Eli Collins
2006-03-14  4:11 ` Rik van Riel
2006-03-22 20:05 ` Andi Kleen
2006-03-22 21:34   ` Chris Wright
2006-03-22 21:13     ` Andi Kleen
2006-03-22 21:57       ` Chris Wright [this message]
2006-03-23  0:06       ` Zachary Amsden
2006-03-22 21:39   ` [RFC, PATCH 1/24] i386 Vmi documentation II Andi Kleen
2006-03-22 22:43     ` Daniel Arai
2006-03-22 22:45     ` Zachary Amsden
2006-03-22 22:38       ` Andi Kleen
2006-03-22 23:54         ` Zachary Amsden
2006-03-22 23:37           ` Andi Kleen
2006-03-22 22:04   ` [RFC, PATCH 1/24] i386 Vmi documentation Zachary Amsden
2006-03-22 21:58     ` Andi Kleen

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=20060322215732.GL15997@sorel.sous-sol.org \
    --to=chrisw@sous-sol.org \
    --cc=ak@suse.de \
    --cc=akpm@osdl.org \
    --cc=anne@vmware.com \
    --cc=arai@vmware.com \
    --cc=chrisl@vmware.com \
    --cc=chrisw@osdl.org \
    --cc=dhecht@vmware.com \
    --cc=jbeulich@novell.com \
    --cc=jlo@vmware.com \
    --cc=jreddy@vmware.com \
    --cc=jtl@ira.uka.de \
    --cc=kmacy@fsmware.com \
    --cc=ksrinivasan@novell.com \
    --cc=leendert@watson.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pratap@vmware.com \
    --cc=riel@redhat.com \
    --cc=torvalds@osdl.org \
    --cc=virtualization@lists.osdl.org \
    --cc=wim.coekaerts@oracle.com \
    --cc=xen-devel@lists.xensource.com \
    --cc=zach@vmware.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

all inboxes | Powered by JetHome®