qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Greg Kurz <groug@kaod.org>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: qemu-ppc@nongnu.org,
	"Satheesh Rajendran" <sathnaga@linux.vnet.ibm.com>,
	"Cédric Le Goater" <clg@kaod.org>,
	qemu-devel@nongnu.org
Subject: Re: [PATCH] spapr/irq: Fix migration of older machine types with XIVE
Date: Thu, 26 Sep 2019 10:13:00 +0200	[thread overview]
Message-ID: <20190926101300.6fa73adc@bahia.lan> (raw)
In-Reply-To: <20190926013808.GV17405@umbus>

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

On Thu, 26 Sep 2019 11:38:08 +1000
David Gibson <david@gibson.dropbear.id.au> wrote:

> On Wed, Sep 25, 2019 at 06:07:40PM +0200, Greg Kurz wrote:
> > Recent patch "spapr/irq: Only claim VALID interrupts at the KVM level"
> > broke migration of older machine types started with ic-mode=xive:
> > 
> > qemu-system-ppc64: KVM_SET_DEVICE_ATTR failed: Group 3 attr 0x0000000000001300: Invalid argument
> > qemu-system-ppc64: error while loading state for instance 0x0 of device 'spapr'
> > qemu-system-ppc64: load of migration failed: Operation not permitted
> > 
> > This is because we should set the interrupt source in KVM at post load,
> > since we no longer do it unconditionaly at reset time for all interrupts.
> > 
> > Signed-off-by: Greg Kurz <groug@kaod.org>
> > ---
> > 
> > David,
> > 
> > I guess you should probably fold this fix directly into Cedric's
> > patch (currently SHA1 966d526cdfd9 in ppc-for-4.2) to avoid
> > bisection breakage.
> 
> Done.
> 

Ok, I see it in ppc-for-4.2. Just one cosmetic nit, missing ']' in
the updated changelog:

[dwg: Folded in fix up from Greg Kurz

> > ---
> >  hw/intc/spapr_xive_kvm.c |   11 +++++++++++
> >  1 file changed, 11 insertions(+)
> > 
> > diff --git a/hw/intc/spapr_xive_kvm.c b/hw/intc/spapr_xive_kvm.c
> > index 71b88d7797bc..2006f96aece1 100644
> > --- a/hw/intc/spapr_xive_kvm.c
> > +++ b/hw/intc/spapr_xive_kvm.c
> > @@ -678,6 +678,17 @@ int kvmppc_xive_post_load(SpaprXive *xive, int version_id)
> >              continue;
> >          }
> >  
> > +        /*
> > +         * We can only restore the source config if the source has been
> > +         * previously set in KVM. Since we don't do that for all interrupts
> > +         * at reset time anymore, let's do it now.
> > +         */
> > +        kvmppc_xive_source_reset_one(&xive->source, i, &local_err);
> > +        if (local_err) {
> > +            error_report_err(local_err);
> > +            return -1;
> > +        }
> > +
> >          kvmppc_xive_set_source_config(xive, i, &xive->eat[i], &local_err);
> >          if (local_err) {
> >              error_report_err(local_err);
> > 
> 


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

  reply	other threads:[~2019-09-26  8:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-25 16:07 [PATCH] spapr/irq: Fix migration of older machine types with XIVE Greg Kurz
2019-09-26  1:38 ` David Gibson
2019-09-26  8:13   ` Greg Kurz [this message]
2019-09-26 11:21     ` David Gibson

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=20190926101300.6fa73adc@bahia.lan \
    --to=groug@kaod.org \
    --cc=clg@kaod.org \
    --cc=david@gibson.dropbear.id.au \
    --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 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).