From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH][WIP][RFC] powerpc: fixup lwsync at runtime
Date: Sun, 22 Jun 2008 10:20:36 +1000 [thread overview]
Message-ID: <1214094036.8011.192.camel@pasglop> (raw)
In-Reply-To: <81690AB9-9D0A-4CB4-8A0A-B0D8653FECE7@kernel.crashing.org>
On Sat, 2008-06-21 at 11:07 -0500, Kumar Gala wrote:
>
> > Remind me why we want to do that ? ie. can't we just use lwsync
> > unconditionally ? It's supposed to degrade to sync on CPUs that
> don't
> > support it, or is that broken on some parts ?
>
> I believe its broken on e500v1/v2. However I'll double check.
An option is that if you get a program check instead, you can "fixup"
the sync from the exception too...
Ben.
next prev parent reply other threads:[~2008-06-22 0:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-20 16:36 [PATCH][WIP][RFC] powerpc: fixup lwsync at runtime Kumar Gala
2008-06-20 23:23 ` Benjamin Herrenschmidt
2008-06-21 16:07 ` Kumar Gala
2008-06-22 0:20 ` Benjamin Herrenschmidt [this message]
2008-06-23 15:02 ` Kumar Gala
2008-06-21 10:27 ` Michael Ellerman
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=1214094036.8011.192.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=galak@kernel.crashing.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).