All of lore.kernel.org
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Alistair Popple <alistair@popple.id.au>
Cc: linuxppc-dev@ozlabs.org, linuxppc-dev@lists.ozlabs.org,
	Jeremy Kerr <jeremy.kerr@au1.ibm.com>
Subject: Re: [PATCH] powerpc/powernv: Support OPAL requested heartbeat
Date: Fri, 14 Nov 2014 15:26:34 +1100	[thread overview]
Message-ID: <1415939194.666.30.camel@kernel.crashing.org> (raw)
In-Reply-To: <40458133.nYBXtuXJmS@mexican>

On Fri, 2014-11-14 at 14:01 +1100, Alistair Popple wrote:
> Hi Ben,
> 
> On Wed, 12 Nov 2014 17:03:14 Benjamin Herrenschmidt wrote:
> 
> <snip>
> 
> > +
> > +static int kopald(void *unused)
> > +{
> > +	set_freezable();
> > +	do {
> > +		try_to_freeze();
> > +		opal_poll_events(NULL);
> 
> Do we need to check for outstanding events (and call opal_do_notifier)? The 
> Linux OPAL-IPMI interface signals an event which the interrupt handler 
> (opal_interrupt) checks for, but if interrupts aren't functional no event will 
> be signalled and hence the Linux IPMI layer won't get a response.
> 
> It's probably only an issue for lab bring up though as I would expect 
> interrupts to generally be working...

Well, it would somewhat double up with the OCC interrupt ... OPAL will
sent a local OCC interrupt if we change the event mask as a result of a
call that isn't opal_handle_interrupts() ... but yes, I suppose if that
doesn't work either... though this is not known to be problematic unless
the external one.

> > +		msleep_interruptible(opal_heartbeat);
> > +	} while (!kthread_should_stop());
> > +
> > +	return 0;
> > +}
> > +
> 
> Regards,
> 
> Alistair

      reply	other threads:[~2014-11-14  4:26 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-12  6:03 [PATCH] powerpc/powernv: Support OPAL requested heartbeat Benjamin Herrenschmidt
2014-11-13  5:29 ` Michael Ellerman
2014-11-13  6:42   ` Benjamin Herrenschmidt
2014-11-13  6:46     ` Jeremy Kerr
2014-11-13 16:59 ` [PATCH] " Paul Clarke
2014-11-13 20:35   ` Benjamin Herrenschmidt
2014-11-14  3:01 ` Alistair Popple
2014-11-14  4:26   ` Benjamin Herrenschmidt [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=1415939194.666.30.camel@kernel.crashing.org \
    --to=benh@kernel.crashing.org \
    --cc=alistair@popple.id.au \
    --cc=jeremy.kerr@au1.ibm.com \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=linuxppc-dev@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.