public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Muli Ben-Yehuda <muli@il.ibm.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Andi Kleen <andi@firstfloor.org>,
	Glauber de Oliveira Costa <gcosta@redhat.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] x86: Create clflush() inline, remove hardcoded wbinvd
Date: Sat, 21 Jul 2007 23:44:58 +0300	[thread overview]
Message-ID: <20070721204458.GG1193@rhun.ibm.com> (raw)
In-Reply-To: <46A26A2E.7070305@zytor.com>

On Sat, Jul 21, 2007 at 01:18:54PM -0700, H. Peter Anvin wrote:
> Muli Ben-Yehuda wrote:
> > 
> > So it looks like we have a purely syntactic patch that does something
> > different than the original code in one of the above places. What am I
> > missing?
> > 
> 
> +static inline void clflush(volatile void *__p)
> +{
> +	asm volatile("clflush %0" : "+m" (*(char __force *)__p));
>                                           ^
> +}

Ok, let's try again:

You're changing this (pageattr.c)

                asm volatile("clflush (%0)" :: "r" (adr + i));

into this:

		asm volatile("clflush %0" : "+m" (*(char __force*)(adr + i)));

The original one calls clflush with (adr + i), the new one with (*(adr
+ i)). Are these calls equivalent? if not, and I don't think they are,
you are changing the semantics of the code (presumably, because it
fixes a bug), and *that should be a separate patch*.

Cheers,
Muli


  reply	other threads:[~2007-07-21 20:45 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-19 22:55 [PATCH] Use wbinvd() macro instead of raw inline assembly in .c files 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
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 [this message]
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=20070721204458.GG1193@rhun.ibm.com \
    --to=muli@il.ibm.com \
    --cc=andi@firstfloor.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