From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Anton Blanchard <anton@samba.org>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] powerpc: inline ppc64_runlatch_off
Date: Fri, 06 Aug 2010 16:25:49 +1000 [thread overview]
Message-ID: <1281075949.2168.31.camel@pasglop> (raw)
In-Reply-To: <20100806055640.GS29316@kryten>
On Fri, 2010-08-06 at 15:56 +1000, Anton Blanchard wrote:
> Unfortunately we still need to prevent continual writes to it with a per thread
> flag because on some CPUs a write to the SPR in low priority mode will stall
> another SMT thread. So we could get rid of the cpu feature comparison but
> we would still need the thread bit check (or perhaps replace it with a per cpu
> variable).
remind me why we need to do that runlatch thing on these CPUs at all ?
Cheers,
Ben.
next prev parent reply other threads:[~2010-08-06 6:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-06 4:53 [PATCH] powerpc: inline ppc64_runlatch_off Anton Blanchard
2010-08-06 5:17 ` Benjamin Herrenschmidt
2010-08-06 5:56 ` Anton Blanchard
2010-08-06 6:25 ` Benjamin Herrenschmidt [this message]
2010-08-06 6:51 ` Anton Blanchard
2010-08-06 8:02 ` Olof Johansson
2010-08-06 13:28 ` Anton Blanchard
2010-08-09 2:44 ` Olof Johansson
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=1281075949.2168.31.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=anton@samba.org \
--cc=linuxppc-dev@ozlabs.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).