From: Grant Grundler <grundler@parisc-linux.org>
To: Matthew Wilcox <matthew@wil.cx>
Cc: John David Anglin <dave.anglin@nrc-cnrc.gc.ca>,
linux-parisc@vger.kernel.org
Subject: Re: Another ldcw inline assembler patch
Date: Sun, 29 Jun 2008 14:55:56 -0600 [thread overview]
Message-ID: <20080629205556.GA8381@colo.lackof.org> (raw)
In-Reply-To: <20080628233406.GI14894@parisc-linux.org>
On Sat, Jun 28, 2008 at 05:34:07PM -0600, Matthew Wilcox wrote:
> On Sat, Jun 28, 2008 at 06:07:57PM -0400, John David Anglin wrote:
> > There are two reasons to expose the memory *a in the asm:
> >
> > 1) To prevent the compiler from discarding a preceeding write to *a, and
> > 2) to prevent it from caching *a in a register over the asm.
>
> Do either of those scenarios apply, given that every usage of this is
> preceded by an asm clobbering memory?
>
> I believe the correct thing to do is to take out the two mb()s in the
> various spin_lock routines and make the __ldcw() macro itself clobber
> memory.
I agree. Do you want jda to submit another patch or did you want kyle to
take jda's patch and apply a second one to remove the mb()'s?
thanks.
grant
>
> --
> Intel are signing my paycheques ... these opinions are still mine
> "Bill, look, we understand that you're interested in selling us this
> operating system, but compare it to ours. We can't possibly take such
> a retrograde step."
> --
> To unsubscribe from this list: send the line "unsubscribe linux-parisc" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2008-06-29 20:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-28 22:07 Another ldcw inline assembler patch John David Anglin
2008-06-28 23:34 ` Matthew Wilcox
2008-06-29 0:43 ` John David Anglin
2008-06-29 20:55 ` Grant Grundler [this message]
2008-06-29 21:09 ` James Bottomley
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=20080629205556.GA8381@colo.lackof.org \
--to=grundler@parisc-linux.org \
--cc=dave.anglin@nrc-cnrc.gc.ca \
--cc=linux-parisc@vger.kernel.org \
--cc=matthew@wil.cx \
/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