linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Michael Ellerman <mpe@ellerman.id.au>
To: Daniel Axtens <dja@axtens.net>, linuxppc-dev@ozlabs.org
Cc: Mahesh J Salgaonkar <mahesh.salgaonkar@in.ibm.com>,
	Daniel Axtens <dja@axtens.net>
Subject: Re: [v2] selftests/powerpc: Add script to test HMI functionality
Date: Thu, 17 Dec 2015 22:57:35 +1100 (AEDT)	[thread overview]
Message-ID: <20151217115735.46CE71401DA@ozlabs.org> (raw)
In-Reply-To: <1449445851-6822-1-git-send-email-dja@axtens.net>

On Sun, 2015-06-12 at 23:50:51 UTC, Daniel Axtens wrote:
> HMIs (Hypervisor Management|Maintenance Interrupts) are a class of interrupt
> on POWER systems.
> 
> HMI support has traditionally been exceptionally difficult to test, however
> Skiboot ships a tool that, with the correct magic numbers, will inject them.
> 
> This, therefore, is a first pass at a script to inject HMIs and monitor
> Linux's response. It injects an HMI on each core on every chip in turn
> It then watches dmesg to see if it's acknowledged by Linux.
> 
> On a Tuletta, I observed that we see 8 (or sometimes 9 or more) events per
> injection, regardless of SMT setting, so we wait for 8 before progressing.
> 
> It sits in a new scripts/ directory in selftests/powerpc, because it's not
> designed to be run as part of the regular make selftests process. In
> particular, it is quite possibly going to end up garding lots of your CPUs,
> so it should only be run if you know how to undo that.
> 
> CC: Mahesh J Salgaonkar <mahesh.salgaonkar@in.ibm.com>
> Signed-off-by: Daniel Axtens <dja@axtens.net>

Applied to powerpc next, thanks.

https://git.kernel.org/powerpc/c/a8da474ec18f4c4c39f83202d6

cheers

      reply	other threads:[~2015-12-17 11:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-06 23:50 [PATCH v2] selftests/powerpc: Add script to test HMI functionality Daniel Axtens
2015-12-17 11:57 ` Michael Ellerman [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=20151217115735.46CE71401DA@ozlabs.org \
    --to=mpe@ellerman.id.au \
    --cc=dja@axtens.net \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=mahesh.salgaonkar@in.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).