From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org, Paul Mackerras <paulus@samba.org>
Subject: Re: [PATCH] powerpc: fixup lwsync at runtime
Date: Tue, 01 Jul 2008 17:15:55 +1000 [thread overview]
Message-ID: <1214896555.20711.112.camel@pasglop> (raw)
In-Reply-To: <1214893402.20711.104.camel@pasglop>
On Tue, 2008-07-01 at 16:23 +1000, Benjamin Herrenschmidt wrote:
> On Tue, 2008-07-01 at 00:32 -0500, Kumar Gala wrote:
> > To allow for a single kernel image on e500 v1/v2/mc we need to fixup lwsync
> > at runtime. On e500v1/v2 lwsync causes an illop so we need to patch up
> > the code. We default to 'sync' since that is always safe and if the cpu
> > is capable we will replace 'sync' with 'lwsync'.
> >
> > We introduce CPU_FTR_LWSYNC as a way to determine at runtime if this is
> > needed. This flag could be moved elsewhere since we dont really use it
> > for the normal CPU_FTR purpose.
> >
> > Finally we only store the relative offset in the fixup section to keep it
> > as small as possible rather than using a full fixup_entry.
> >
> > Signed-off-by: Kumar Gala <galak@kernel.crashing.org>
>
> I'd rather have some more generic "alternatives" stuff but in the
> meantime, Ack.
Hrm... minus mpe's comments...
Cheers,
Ben.
next prev parent reply other threads:[~2008-07-01 7:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-01 5:32 [PATCH] powerpc: fixup lwsync at runtime Kumar Gala
2008-07-01 6:23 ` Benjamin Herrenschmidt
2008-07-01 7:15 ` Benjamin Herrenschmidt [this message]
2008-07-01 6:29 ` Michael Ellerman
2008-07-01 14:48 ` Kumar Gala
2008-07-02 9:34 ` Michael Ellerman
2008-07-02 15:57 ` Kumar Gala
2008-07-03 5:55 ` Michael Ellerman
-- strict thread matches above, loose matches on Subject: below --
2008-06-26 15:30 Kumar Gala
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=1214896555.20711.112.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=galak@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.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).