From: Michael Ellerman <mpe@ellerman.id.au>
To: Michael Neuling <mikey@neuling.org>,
Jack Miller <jack@codezen.org>,
linuxppc-dev@lists.ozlabs.org
Cc: anton@samba.org
Subject: Re: [PATCH 3/3] powerpc: Load Monitor Register Tests
Date: Wed, 04 May 2016 21:31:04 +1000 [thread overview]
Message-ID: <1462361464.1846.3.camel@ellerman.id.au> (raw)
In-Reply-To: <1462358630.4115.76.camel@neuling.org>
On Wed, 2016-05-04 at 20:43 +1000, Michael Neuling wrote:
> On Mon, 2016-04-18 at 16:08 -0500, Jack Miller wrote:
> > +int ebb_lmr(void)
> > +{
> > + int i;
> > +
> > + SKIP_IF(!ebb_is_supported());
>
> We skip this test currently as EBB is not enabled on POWER9.
>
> On POWER8 we enable EBB in the PMU code. Should we do this elsewhere for
> POWER9 since EBB doesn't directly require the PMU?
Probably. But we will need to check that if the PMU code is *not* enabled we
still do the context switching of EBB regs correctly. We probably do, but I
don't now for sure.
cheers
next prev parent reply other threads:[~2016-05-04 11:31 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-18 19:07 [v2] P9 ldmx support Jack Miller
2016-04-18 19:08 ` [PATCH 1/3] powerpc: Complete FSCR context switch Jack Miller
2016-04-18 19:08 ` [PATCH 2/3] powerpc: Load Monitor Register Support Jack Miller
2016-04-18 20:47 ` kbuild test robot
2016-04-18 21:08 ` [v3] P9 ldmx support Jack Miller
2016-04-18 21:08 ` [PATCH 1/3] powerpc: Complete FSCR context switch Jack Miller
2016-05-04 11:16 ` [PATCH v4] " Michael Neuling
2016-05-06 2:30 ` [PATCH v5 0/3] POWER9 Load Monitor Support Michael Neuling
2016-05-06 2:30 ` [PATCH v5 1/3] powerpc: Improve FSCR init and context switching Michael Neuling
2016-05-06 2:30 ` [PATCH v5 2/3] powerpc: Load Monitor Register Support Michael Neuling
2016-05-06 2:30 ` [PATCH v5 3/3] powerpc: Load Monitor Register Tests Michael Neuling
2016-06-08 10:38 ` [PATCH v6 0/3] POWER9 Load Monitor Support Michael Neuling
2016-06-08 10:38 ` [PATCH v6 1/3] powerpc: Improve FSCR init and context switching Michael Neuling
2016-06-08 10:38 ` [PATCH v6 2/3] powerpc: Load Monitor Register Support Michael Neuling
2016-06-08 10:38 ` [PATCH v6 3/3] powerpc: Load Monitor Register Tests Michael Neuling
2016-06-09 2:31 ` [PATCH v7 0/3] POWER9 Load Monitor Support Michael Neuling
2016-06-09 2:31 ` [PATCH v7 1/3] powerpc: Improve FSCR init and context switching Michael Neuling
2016-06-21 12:27 ` [v7,1/3] " Michael Ellerman
2016-06-09 2:31 ` [PATCH v7 2/3] powerpc: Load Monitor Register Support Michael Neuling
2016-06-21 12:27 ` [v7,2/3] " Michael Ellerman
2016-06-09 2:31 ` [PATCH v7 3/3] powerpc: Load Monitor Register Tests Michael Neuling
2016-06-21 12:27 ` [v7,3/3] " Michael Ellerman
2016-04-18 21:08 ` [PATCH 2/3] powerpc: Load Monitor Register Support Jack Miller
2016-04-18 21:08 ` [PATCH 3/3] powerpc: Load Monitor Register Tests Jack Miller
2016-05-04 10:43 ` Michael Neuling
2016-05-04 11:31 ` Michael Ellerman [this message]
2016-05-04 11:41 ` Michael Neuling
2016-04-18 19:08 ` Jack Miller
-- strict thread matches above, loose matches on Subject: below --
2016-04-11 18:57 [RFC] P9 ldmx support Jack Miller
2016-04-11 18:57 ` [PATCH 3/3] powerpc: Load Monitor Register Tests Jack Miller
2016-04-15 10:34 ` Madhavan Srinivasan
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=1462361464.1846.3.camel@ellerman.id.au \
--to=mpe@ellerman.id.au \
--cc=anton@samba.org \
--cc=jack@codezen.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mikey@neuling.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).