From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: SeongJae Park <sj38.park@gmail.com>
Cc: perfbook@vger.kernel.org
Subject: Re: [PATCH] appendix/whymb: Fix a typo, smb_wmb into smp_wmb
Date: Sun, 19 Feb 2017 14:14:04 -0800 [thread overview]
Message-ID: <20170219221404.GL30506@linux.vnet.ibm.com> (raw)
In-Reply-To: <20170217015415.32519-1-sj38.park@gmail.com>
On Fri, Feb 17, 2017 at 10:54:15AM +0900, SeongJae Park wrote:
> Signed-off-by: SeongJae Park <sj38.park@gmail.com>
Good eyes, applied, thank you!
Thanx, Paul
> ---
> appendix/whymb/whymemorybarriers.tex | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/appendix/whymb/whymemorybarriers.tex b/appendix/whymb/whymemorybarriers.tex
> index 9002047a9878..3a22e46beb0c 100644
> --- a/appendix/whymb/whymemorybarriers.tex
> +++ b/appendix/whymb/whymemorybarriers.tex
> @@ -2265,7 +2265,7 @@ a write to a given MMIO register affects the value that will next be
> read from {\em some other} MMIO register.
>
> It is not clear why SPARC does not define \co{wmb()} to be
> -\co{membar #MemIssue} and \co{smb_wmb()} to be
> +\co{membar #MemIssue} and \co{smp_wmb()} to be
> \co{membar #StoreStore},
> as the current definitions seem vulnerable to bugs in some drivers.
> It is quite possible that all the SPARC CPUs that Linux runs on
> --
> 2.10.0
>
> --
> To unsubscribe from this list: send the line "unsubscribe perfbook" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
prev parent reply other threads:[~2017-02-19 22:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-17 1:54 [PATCH] appendix/whymb: Fix a typo, smb_wmb into smp_wmb SeongJae Park
2017-02-19 22:14 ` Paul E. McKenney [this message]
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=20170219221404.GL30506@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=perfbook@vger.kernel.org \
--cc=sj38.park@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.