From: Olof Johansson <olof@lixom.net>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: linuxppc-dev list <linuxppc-dev@ozlabs.org>
Subject: Re: [PATCH 1/4] powerpc: consolidate feature fixup code
Date: Thu, 12 Oct 2006 09:56:49 -0500 [thread overview]
Message-ID: <20061012095649.23bb6b35@localhost.localdomain> (raw)
In-Reply-To: <1160664449.4792.147.camel@localhost.localdomain>
On Fri, 13 Oct 2006 00:47:29 +1000 Benjamin Herrenschmidt <benh@kernel.crashing.org> wrote:
>
> > > +void do_feature_fixups(unsigned long offset, unsigned long value,
> > > + void *fixup_start, void *fixup_end)
> > > +{
> > > + struct fixup_entry {
> > > + unsigned long mask;
> > > + unsigned long value;
> > > + unsigned int *start;
> > > + unsigned int *end;
> > > + } *fcur, *fend;
> >
> > Shouldn't there be a better place to keep this struct definition than
> > in the function it's used? Some header file?
>
> It's not used anywhere else.... which header would you put it in ?
Near where the asm-corresponding ones are located (cputable.h).
-Olof
> > Ok, now it's in C, no reason to do a dcbst/icbi for every word. We did
> > it in asm for simplicity's sake. Split it in two loops, one to nop,
> > second to step per line and do the flushes. :-)
>
> Do we care ? :) But yah, I suppose I can do that.
Close call. :-) It's just easier to do now, might as well do it. But
yeah, no big deal.
It will also be easier to graft in a branch forward instead of a large
amount of nops for large feature sections. I guess it will take some
benchmarking to see what the breakeven point is.
-Olof
next prev parent reply other threads:[~2006-10-12 14:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-12 8:29 [PATCH 1/4] powerpc: consolidate feature fixup code Benjamin Herrenschmidt
2006-10-12 9:56 ` Michael Ellerman
2006-10-12 10:48 ` Benjamin Herrenschmidt
2006-10-12 13:56 ` Olof Johansson
2006-10-12 14:47 ` Benjamin Herrenschmidt
2006-10-12 14:56 ` Olof Johansson [this message]
2006-10-12 15:24 ` Benjamin Herrenschmidt
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=20061012095649.23bb6b35@localhost.localdomain \
--to=olof@lixom.net \
--cc=benh@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 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.