From: Michael Neuling <mikey@neuling.org>
To: Jack Miller <jack@codezen.org>, linuxppc-dev@lists.ozlabs.org
Subject: Re: [RFC] P9 ldmx support
Date: Tue, 12 Apr 2016 11:05:36 +1000 [thread overview]
Message-ID: <1460423136.24701.30.camel@neuling.org> (raw)
In-Reply-To: <1460401065-10540-1-git-send-email-jack@codezen.org>
> Re: [RFC] P9 ldmx support
These are good to go and don't need to be marked as RFC.
FWIW, we've been testing these internally and they've been solid.
> These are patches based on next to support the forthcoming ldmx
> instruction through the existing P8 EBB infrastructure. Obviously it
> doesn't actually *work* without some other patches and a P9 system,
> but with the context switch change to FSCR it makes sense to get
> this upstream for testing ASAP.
Yep.
Thanks,
Mikey
> The first patch context switches FSCR per thread so that the second patch=
can
> lazily enable this feature (FSCR.LM) with a facility unavailable exceptio=
n
> and context switch two new ldmx registers (LMRR / LMSER) per thread as we=
ll.
> Third patch is a couple of basic tests.
prev parent reply other threads:[~2016-04-12 1:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-11 18:57 [RFC] P9 ldmx support Jack Miller
2016-04-11 18:57 ` [PATCH 1/3] powerpc: Complete FSCR context switch Jack Miller
2016-04-12 23:42 ` [1/3] " Michael Ellerman
2016-04-13 10:51 ` [PATCH 1/3] " Anton Blanchard
2016-04-13 17:52 ` Jack Miller
2016-04-13 23:49 ` Michael Neuling
2016-04-14 18:39 ` Jack Miller
2016-04-14 23:11 ` Michael Neuling
2016-04-11 18:57 ` [PATCH 2/3] powerpc: Load Monitor Register Support Jack Miller
2016-04-12 5:40 ` Segher Boessenkool
2016-04-13 17:39 ` Jack Miller
2016-04-11 18:57 ` [PATCH 3/3] powerpc: Load Monitor Register Tests Jack Miller
2016-04-15 10:34 ` Madhavan Srinivasan
2016-04-12 1:05 ` Michael Neuling [this message]
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=1460423136.24701.30.camel@neuling.org \
--to=mikey@neuling.org \
--cc=jack@codezen.org \
--cc=linuxppc-dev@lists.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).