From: Muli Ben-Yehuda <muli@il.ibm.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Andi Kleen <ak@suse.de>,
Glauber de Oliveira Costa <gcosta@redhat.com>,
akpm@linux-foundation.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Use wbinvd() macro instead of raw inline assembly in .c files
Date: Sat, 21 Jul 2007 10:32:31 +0300 [thread overview]
Message-ID: <20070721073231.GG4152@rhun.haifa.ibm.com> (raw)
In-Reply-To: <46A0EF4D.6030308@zytor.com>
On Fri, Jul 20, 2007 at 10:22:21AM -0700, H. Peter Anvin wrote:
> Andi Kleen wrote:
> > On Friday 20 July 2007 00:55:40 Glauber de Oliveira Costa wrote:
> >> This patch uses the already-existant wbinvd() macro to replace
> >> raw assembly to perform this very same task in some .c files
> >>
> >> Signed-off-by: Glauber de Oliveira Costa <gcosta@redhat.com>
> >>
> >> diff --git a/arch/x86_64/kernel/tce.c b/arch/x86_64/kernel/tce.c
> >> index f61fb8e..afbb951 100644
> >> --- a/arch/x86_64/kernel/tce.c
> >> +++ b/arch/x86_64/kernel/tce.c
> >> @@ -42,7 +42,7 @@ static inline void flush_tce(void* tceaddr)
> >> if (cpu_has_clflush)
> >> asm volatile("clflush (%0)" :: "r" (tceaddr));
> >> else
> >> - asm volatile("wbinvd":::"memory");
> >> + wbinvd();
> >
> > I guess it can be just removed there. I don' think there are any
> > calgary machines without clflush
> >
> That seems like an unsafe thing to do (unless we err out somewhere);
> lest there is, say, a microcode update disabling clflush due to an
> erratum.
I agree.
Cheers,
Muli
next prev parent reply other threads:[~2007-07-21 7:32 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-19 22:55 Glauber de Oliveira Costa
2007-07-20 11:43 ` Andi Kleen
2007-07-20 17:22 ` H. Peter Anvin
2007-07-21 7:32 ` Muli Ben-Yehuda [this message]
2007-07-20 21:19 ` [PATCH] x86: Create clflush() inline, remove hardcoded wbinvd H. Peter Anvin
2007-07-20 21:27 ` Andi Kleen
2007-07-20 21:33 ` H. Peter Anvin
2007-07-22 9:18 ` Andi Kleen
2007-07-22 18:05 ` H. Peter Anvin
2007-07-22 19:55 ` Andi Kleen
2007-07-22 20:02 ` H. Peter Anvin
2007-07-20 23:37 ` Glauber de Oliveira Costa
2007-07-20 23:43 ` H. Peter Anvin
2007-07-21 18:11 ` Muli Ben-Yehuda
2007-07-21 19:52 ` H. Peter Anvin
2007-07-21 20:16 ` Muli Ben-Yehuda
2007-07-21 20:18 ` H. Peter Anvin
2007-07-21 20:44 ` Muli Ben-Yehuda
2007-07-21 22:09 ` H. Peter Anvin
2007-07-21 22:24 ` H. Peter Anvin
2007-07-22 4:20 ` Muli Ben-Yehuda
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=20070721073231.GG4152@rhun.haifa.ibm.com \
--to=muli@il.ibm.com \
--cc=ak@suse.de \
--cc=akpm@linux-foundation.org \
--cc=gcosta@redhat.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.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
Powered by JetHome