From: Michael Neuling <mikey@neuling.org>
To: Jimi Xenidis <jimix@pobox.com>
Cc: Andrew T Tauferner <ataufer@us.ibm.com>,
Kumar Gala <kumar.gala@gmail.com>,
Jay Bryant <jsbryant@us.ibm.com>,
Josh Boyer <jwboyer@linux.vnet.ibm.com>,
Todd Inglett <tinglett@us.ibm.com>,
linuxppc-dev <linuxppc-dev@lists.ozlabs.org>
Subject: Re: [RFC] Add IBM Blue Gene/Q Platform
Date: Mon, 10 Dec 2012 17:06:06 +1100 [thread overview]
Message-ID: <12948.1355119566@neuling.org> (raw)
In-Reply-To: <FAE4A73A-BDC0-43E3-A416-E8F0F161C5B4@pobox.com>
Jimi Xenidis <jimix@pobox.com> wrote:
>
>
> On Dec 9, 2012, at 6:47 PM, Michael Neuling <mikey@neuling.org> wrote:
>
> > Jimi Xenidis <jimix@pobox.com> wrote:
> >
> >>
> >> On Dec 7, 2012, at 7:38 AM, Jimi Xenidis <jimix@pobox.com> wrote:
> >>
> >>>
> >>> On Dec 6, 2012, at 11:54 PM, Michael Neuling <mikey@neuling.org> wrote:
> >>>
> >>>>> commit 279c0615917b959a652e81f4ad0d886e2d426d85
> >>>>> Author: Jimi Xenidis <jimix@pobox.com>
> >>>>> Date: Wed Dec 5 13:43:22 2012 -0500
> >>>>>
> >>>>> powerpc/book3e: IBM Blue Gene/Q Quad Processing eXtention (QPX)
> >>>>>
> >>>>> This enables kernel support for the QPX extention and is intended for
> >>>>> processors that support it, usually an IBM Blue Gene processor.
> >>>>> Turning it on does not effect other processors but it does add code
> >>>>> and will quadruple the per thread save and restore area for the FPU
> >>>>> (hense the name). If you have enabled VSX it will only double the
> >>>>> space.
> >>>>>
> >>>>> Signed-off-by: Jimi Xenidis <jimix@pobox.com>
> >>
> >> <<snip>>
> >>>>
> >>>>
> >>>>
> >>>> +BEGIN_FTR_SECTION \
> >>>> + SAVE_32VSRS(n,c,base); \
> >>>> +END_FTR_SECTION_IFSET(CPU_FTR_VSX); \
> >>>> +BEGIN_FTR_SECTION \
> >>>> + SAVE_32QRS(n,c,base); \
> >>>> +END_FTR_SECTION_IFSET(CPU_FTR_QPX);
> >>>>
> >>>> I don't think we want to do this. We are going to end up with 64
> >>>> NOPS here somewhere.
> >>>
> >>> Excellent point, NOPs are cheap on most processors but not A2 and a lot of embedded, I can wrap some branches with the FTR instead.
> >>> Do you have a concern on the code size?
> >>
> >> Thought about it a bit and came up with this solution for arch/powerpc/kernel/fpu.S.
> >> This should address the following issues
> >> - MSR_VSX vs MSR_VEC
> >> - Big chunks of NOPs in the code path
> >> - Less FTR space fixups at boot time.
> >> - IMNHSO easier to read especially when disassembled
> >
> > Indeed, I think it looks better. I was going to mention that it was
> > already pretty complex to read, so a rewrite like this was probably
> > needed. So thanks!!
> >
> > That being said, there is a pretty complex testing matrix of
> > CONFIG_VSX/VMX/FPU/QPX/SMP/64/32 CPU_FTR/VSX/FPU/QPX/VMX so I'd need to
> > look/test more carefully to make sure all of these are covered.
> >
> > Also, transactional memory (see
> > http://lists.ozlabs.org/pipermail/linuxppc-dev/2012-November/102216.html)
> > will change this code. You should rebase on top of that if you really
> > want it considered for upstream.
>
> Is this in a git tree anywhere? perhaps BenH's next branch?
It's not in benh's tree as yet (so could change).
Grab the power8 branch here git://github.com/mikey/linux.git
or checkout https://github.com/mikey/linux/commits/power8.
It's about 20 patches on top of benh's next tree. Also includes the
power8 doorbell changes from Ian.
Mikey
next prev parent reply other threads:[~2012-12-10 6:06 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-07 1:53 [RFC] Add IBM Blue Gene/Q Platform Jimi Xenidis
2012-12-07 5:41 ` Michael Neuling
2012-12-07 13:12 ` Jimi Xenidis
2012-12-10 0:12 ` Michael Neuling
2012-12-07 5:54 ` Michael Neuling
2012-12-07 5:55 ` Michael Neuling
2012-12-07 13:38 ` Jimi Xenidis
2012-12-08 22:22 ` Jimi Xenidis
2012-12-10 0:47 ` Michael Neuling
2012-12-10 5:56 ` Jimi Xenidis
2012-12-10 6:06 ` Michael Neuling [this message]
2012-12-10 0:18 ` Michael Neuling
2012-12-07 5:56 ` Michael Neuling
2012-12-07 13:44 ` Jimi Xenidis
2012-12-07 14:31 ` Andrew Tauferner
2012-12-10 21:32 ` Jimi Xenidis
2012-12-10 21:33 ` Jimi Xenidis
2012-12-10 0:26 ` Michael Neuling
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=12948.1355119566@neuling.org \
--to=mikey@neuling.org \
--cc=ataufer@us.ibm.com \
--cc=jimix@pobox.com \
--cc=jsbryant@us.ibm.com \
--cc=jwboyer@linux.vnet.ibm.com \
--cc=kumar.gala@gmail.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=tinglett@us.ibm.com \
/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).