From: Andi Kleen <ak@suse.de>
To: Avi Kivity <avi@qumranet.com>
Cc: Glauber de Oliveira Costa <gcosta@redhat.com>,
linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
glommer@gmail.com, tglx@linutronix.de, mingo@elte.hu,
ehabkost@redhat.com, jeremy@goop.org, anthony@codemonkey.ws,
virtualization@lists.linux-foundation.org, rusty@rustcorp.com.au,
ak@suse.de, chrisw@sous-sol.org, rostedt@goodmis.org,
hpa@zytor.com
Subject: Re: [PATCH 4/8] unify paravirt parts of system.h
Date: Tue, 4 Dec 2007 20:34:32 +0100 [thread overview]
Message-ID: <20071204193432.GI11764@bingen.suse.de> (raw)
In-Reply-To: <4755A809.4050305@qumranet.com>
On Tue, Dec 04, 2007 at 09:18:33PM +0200, Avi Kivity wrote:
> Glauber de Oliveira Costa wrote:
>> This patch moves the i386 control registers manipulation functions,
>> wbinvd, and clts functions to system.h. They are essentially the same
>> as in x86_64, except for the cr8 register, which we add.
>>
>> +
>> +static inline unsigned long native_read_cr8(void)
>> +{
>> + unsigned long cr8;
>> + asm volatile("mov %%cr8,%0" : "=r" (cr8), "=m" (__force_order));
>> + return cr8;
>> +}
>> +
>>
>
> There is no cr8 register on i386. This had better be protected by an
> #ifdef.
>
> (you're likely not getting an error since it's a static inline, so the asm
> is never emitted)
Linux never uses that register. The only user is suspend save/restore,
but that' bogus because it wasn't ever initialized by Linux in the first
place. It could be probably all safely removed.
-Andi
next prev parent reply other threads:[~2007-12-04 21:31 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-04 16:06 [PATCH 0/8] Integrate system.h Glauber de Oliveira Costa
2007-12-04 16:06 ` [PATCH 1/8] remove volatile keyword from clflush Glauber de Oliveira Costa
2007-12-04 16:06 ` [PATCH 2/8] put together equal pieces of system.h Glauber de Oliveira Costa
2007-12-04 16:06 ` [PATCH 3/8] unify load_segment macro Glauber de Oliveira Costa
2007-12-04 16:06 ` [PATCH 4/8] unify paravirt parts of system.h Glauber de Oliveira Costa
2007-12-04 16:06 ` [PATCH 5/8] remove unused macro Glauber de Oliveira Costa
2007-12-04 16:06 ` [PATCH 6/8] unify smp parts of system.h Glauber de Oliveira Costa
2007-12-04 16:06 ` [PATCH 7/8] move switch_to macro to system.h Glauber de Oliveira Costa
2007-12-04 16:06 ` [PATCH 8/8] unify system.h Glauber de Oliveira Costa
2007-12-04 19:18 ` [PATCH 4/8] unify paravirt parts of system.h Avi Kivity
2007-12-04 19:34 ` Andi Kleen [this message]
2007-12-05 16:30 ` Pavel Machek
2007-12-15 13:17 ` Ingo Molnar
2007-12-17 0:27 ` Rafael J. Wysocki
2007-12-17 0:23 ` Pavel Machek
2007-12-17 0:58 ` Rafael J. Wysocki
2007-12-15 13:26 ` Andi Kleen
2007-12-15 22:54 ` Pavel Machek
2007-12-15 20:28 ` H. Peter Anvin
2007-12-04 19:41 ` Glauber de Oliveira Costa
2007-12-04 22:14 ` Denys Vlasenko
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=20071204193432.GI11764@bingen.suse.de \
--to=ak@suse.de \
--cc=akpm@linux-foundation.org \
--cc=anthony@codemonkey.ws \
--cc=avi@qumranet.com \
--cc=chrisw@sous-sol.org \
--cc=ehabkost@redhat.com \
--cc=gcosta@redhat.com \
--cc=glommer@gmail.com \
--cc=hpa@zytor.com \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rostedt@goodmis.org \
--cc=rusty@rustcorp.com.au \
--cc=tglx@linutronix.de \
--cc=virtualization@lists.linux-foundation.org \
/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).