linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Nicholas Piggin <npiggin@gmail.com>
To: linuxppc-dev@lists.ozlabs.org, skiboot@lists.ozlabs.org
Cc: Nicholas Piggin <npiggin@gmail.com>,
	Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	Alistair Popple <alistair@popple.id.au>
Subject: [RFC PATCH 0/2] NMI IPI work in progress for Linux and OPAL
Date: Wed, 13 Sep 2017 02:05:51 +1000	[thread overview]
Message-ID: <20170912160553.13422-1-npiggin@gmail.com> (raw)

Hi,

I have Linux and OPAL patches that make the NMI IPI facility work on
a POWER9 DD1 here, lightly tested. It works for threads that are running
and are in stop (at least the stop0_lite state enabled in DD1).

Comments on the OPAL patch in particular would be good. Next step will
be more testing with DD2 and different idle states.

This was taken mostly from pdbg but I have ended up changing a few
things (e.g., to make it work in idle state).

Thanks,
Nick

             reply	other threads:[~2017-09-12 16:05 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-12 16:05 Nicholas Piggin [this message]
2017-09-12 16:05 ` [RFC PATCH 1/2] core: implement OPAL_SIGNAL_SYSTEM_RESET with POWER9 scoms Nicholas Piggin
2017-09-12 23:18   ` Benjamin Herrenschmidt
2017-09-13 13:27     ` Nicholas Piggin
2017-09-14  2:27       ` Benjamin Herrenschmidt
2017-09-12 16:05 ` [RFC PATCH 2/2] powerpc/powernv: implement NMI IPIs with OPAL_SIGNAL_SYSTEM_RESET Nicholas Piggin
2017-09-13 13:13   ` Nicholas Piggin
2017-09-14  2:24     ` Benjamin Herrenschmidt
2017-09-14  6:32       ` Nicholas Piggin
2017-09-14  6:43         ` Alistair Popple
2017-09-14 11:26   ` Nicholas Piggin

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=20170912160553.13422-1-npiggin@gmail.com \
    --to=npiggin@gmail.com \
    --cc=alistair@popple.id.au \
    --cc=benh@kernel.crashing.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=skiboot@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).