All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kurz <groug@kaod.org>
To: Cornelia Huck <cohuck@redhat.com>
Cc: "Laurent Vivier" <lvivier@redhat.com>,
	qemu-devel@nongnu.org, qemu-ppc@nongnu.org,
	"Cédric Le Goater" <clg@kaod.org>,
	"Satheesh Rajendran" <sathnaga@linux.vnet.ibm.com>,
	"David Gibson" <david@gibson.dropbear.id.au>
Subject: Re: [for-5.0 PATCH 0/4] ppc: Fix interrupt controller emulation
Date: Mon, 9 Dec 2019 12:14:55 +0100	[thread overview]
Message-ID: <20191209121455.17193284@bahia.w3ibm.bluemix.net> (raw)
In-Reply-To: <20191209120735.4fe6e4ea.cohuck@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 1496 bytes --]

On Mon, 9 Dec 2019 12:07:35 +0100
Cornelia Huck <cohuck@redhat.com> wrote:

> On Mon, 9 Dec 2019 11:59:47 +0100
> Greg Kurz <groug@kaod.org> wrote:
> 
> > On Mon, 9 Dec 2019 12:14:28 +1100
> > David Gibson <david@gibson.dropbear.id.au> wrote:
> > 
> > > On Wed, Dec 04, 2019 at 08:43:31PM +0100, Greg Kurz wrote:  
> > > > Guest hangs have been observed recently on POWER9 hosts, specifically LC92x
> > > > "Boston" systems, when the guests are being rebooted multiple times. The
> > > > issue isn't POWER9 specific though. It is caused by a very long standing bug
> > > > when using the uncommon accel=kvm,kernel-irqchip=off machine configuration
> > > > which happens to be enforced on LC92x because of a host FW limitation. This
> > > > affects both the XICS and XIVE emulated interrupt controllers.
> > > > 
> > > > The actual fix is in patch 1. Patch 2 is a followup cleanup. The other
> > > > patches are unrelated cleanups I came up with while investigating.
> > > > 
> > > > Since this bug always existed and we're already in rc4, I think it is better
> > > > to fix it in 5.0 and possibly backport it to stable and downstream if needed.  
> > > 
> > > Applied to ppc-for-5.0.
> > > 
> > >   
> > 
> > According to Cornelia's comments, it seems I need to respin this against
> > the s390-next branch to avoid conflicts.
> 
> 
> Aren't these ppc-only patches, though? Confused.

Oops... I've mixed up with the CPUReset series, sorry for the confusion :-)

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      reply	other threads:[~2019-12-09 11:16 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-04 19:43 [for-5.0 PATCH 0/4] ppc: Fix interrupt controller emulation Greg Kurz
2019-12-04 19:43 ` [for-5.0 PATCH 1/4] ppc: Deassert the external interrupt pin in KVM on reset Greg Kurz
2019-12-04 19:43 ` [for-5.0 PATCH 2/4] xics: Don't deassert outputs Greg Kurz
2019-12-04 19:43 ` [for-5.0 PATCH 3/4] ppc: Don't use CPUPPCState::irq_input_state with modern Book3s CPU models Greg Kurz
2019-12-04 19:43 ` [for-5.0 PATCH 4/4] ppc: Ignore the CPU_INTERRUPT_EXITTB interrupt with KVM Greg Kurz
2019-12-09  1:14 ` [for-5.0 PATCH 0/4] ppc: Fix interrupt controller emulation David Gibson
2019-12-09 10:59   ` Greg Kurz
2019-12-09 11:07     ` Cornelia Huck
2019-12-09 11:14       ` Greg Kurz [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=20191209121455.17193284@bahia.w3ibm.bluemix.net \
    --to=groug@kaod.org \
    --cc=clg@kaod.org \
    --cc=cohuck@redhat.com \
    --cc=david@gibson.dropbear.id.au \
    --cc=lvivier@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-ppc@nongnu.org \
    --cc=sathnaga@linux.vnet.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 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.