From: Gabriel Paubert <paubert@iram.es>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Olof Johansson <olof@lixom.net>,
linuxppc-dev@ozlabs.org, Paul Mackerras <paulus@samba.org>
Subject: Re: [PATCH] Lazy interrupt disabling for 64-bit machines
Date: Tue, 26 Sep 2006 12:31:04 +0200 [thread overview]
Message-ID: <20060926103104.GA19065@iram.es> (raw)
In-Reply-To: <1159261926.5462.54.camel@localhost.localdomain>
On Tue, Sep 26, 2006 at 07:12:06PM +1000, Benjamin Herrenschmidt wrote:
>
> > I like it. Got any benchmarks that show a difference?
> >
> > At first glance I found it a bit hard to follow, since the old+new
> > terminology is a bit complicated. There's softe, proc_enabled and
> > hard_enabled. A s/proc_enabled/soft_enabled/g (and similar for
> > asm-offsets) might make it a little more intuitive, since you're
> > touching most uses of it already?
>
> Now think about using -ffixed=crN ... reserve a CR field and use that
> for per-cpu flags like that :)
>
Actually cr5 is never used by GCC on any PPC. Look at the source
code in config/rs6000.h, it is marked fixed and never allocated
as far as I understand.
Regards,
Gabriel "an unused register is a wasted register"
next prev parent reply other threads:[~2006-09-26 10:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-26 4:55 [PATCH] Lazy interrupt disabling for 64-bit machines Paul Mackerras
2006-09-26 5:30 ` Michael Ellerman
2006-09-26 6:10 ` Olof Johansson
2006-09-26 9:12 ` Benjamin Herrenschmidt
2006-09-26 10:31 ` Gabriel Paubert [this message]
2006-09-26 15:43 ` Olof Johansson
-- strict thread matches above, loose matches on Subject: below --
2006-10-04 6:47 Paul Mackerras
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=20060926103104.GA19065@iram.es \
--to=paubert@iram.es \
--cc=benh@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=olof@lixom.net \
--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).