public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: David Gibson <david@gibson.dropbear.id.au>
To: Greg Kurz <groug@kaod.org>
Cc: "Cédric Le Goater" <clg@kaod.org>,
	kvm-ppc@vger.kernel.org, "Paul Mackerras" <paulus@samba.org>,
	kvm@vger.kernel.org
Subject: Re: [PATCH 0/3] KVM: PPC: Book3S HV: XIVE: assorted fixes on vCPU and RAM limits
Date: Thu, 23 May 2019 16:27:15 +1000	[thread overview]
Message-ID: <20190523062715.GR30423@umbus.fritz.box> (raw)
In-Reply-To: <20190523080123.6e700a1e@bahia.lan>

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

On Thu, May 23, 2019 at 08:01:23AM +0200, Greg Kurz wrote:
> On Thu, 23 May 2019 09:30:43 +1000
> David Gibson <david@gibson.dropbear.id.au> wrote:
> 
> > On Mon, May 20, 2019 at 09:15:11AM +0200, Cédric Le Goater wrote:
> > > Hello,
> > > 
> > > Here are a couple of fixes for issues in the XIVE KVM device when
> > > testing the limits : RAM size and number of vCPUS.  
> > 
> > How serious are the problems these patches fix?  I'm wondering if I
> > need to make a backport for RHEL8.1.
> > 
> 
> Patch 2/3 fixes a QEMU error when hot-unplugging a vCPU:
> 
> qemu-system-ppc64: KVM_SET_DEVICE_ATTR failed: Group 4 attr 0x0000000000000046: Invalid argument
> 
> 
> Patch 3/3 fixes an issue where the guest freezes at some point when doing
> vCPU hot-plug/unplug in a loop.

Oh.. weird.  It's not clear to me how it would do that.

> Both issues have a BZ at IBM. They can be mirrored to RH if needed.

That would be helpful, thanks.




> 
> > > 
> > > Based on 5.2-rc1.
> > > 
> > > Available on GitHub:
> > > 
> > >     https://github.com/legoater/linux/commits/xive-5.2
> > > 
> > > Thanks,
> > > 
> > > C. 
> > > 
> > > Cédric Le Goater (3):
> > >   KVM: PPC: Book3S HV: XIVE: clear file mapping when device is released
> > >   KVM: PPC: Book3S HV: XIVE: do not test the EQ flag validity when
> > >     reseting
> > >   KVM: PPC: Book3S HV: XIVE: fix the enforced limit on the vCPU
> > >     identifier
> > > 
> > >  arch/powerpc/kvm/book3s_xive_native.c | 46 ++++++++++++++++-----------
> > >  1 file changed, 27 insertions(+), 19 deletions(-)
> > >   
> > 
> 



-- 
David Gibson			| I'll have my music baroque, and my code
david AT gibson.dropbear.id.au	| minimalist, thank you.  NOT _the_ _other_
				| _way_ _around_!
http://www.ozlabs.org/~dgibson

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

  reply	other threads:[~2019-05-23 11:56 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-20  7:15 [PATCH 0/3] KVM: PPC: Book3S HV: XIVE: assorted fixes on vCPU and RAM limits Cédric Le Goater
2019-05-20  7:15 ` [PATCH 1/3] KVM: PPC: Book3S HV: XIVE: clear file mapping when device is released Cédric Le Goater
2019-05-20  7:15 ` [PATCH 2/3] KVM: PPC: Book3S HV: XIVE: do not test the EQ flag validity when resetting Cédric Le Goater
2019-05-20  8:06   ` Greg Kurz
2019-05-20  7:15 ` [PATCH 3/3] KVM: PPC: Book3S HV: XIVE: fix the enforced limit on the vCPU identifier Cédric Le Goater
2019-05-20  9:23   ` Greg Kurz
2019-05-22 23:30 ` [PATCH 0/3] KVM: PPC: Book3S HV: XIVE: assorted fixes on vCPU and RAM limits David Gibson
2019-05-23  6:01   ` Greg Kurz
2019-05-23  6:27     ` David Gibson [this message]
2019-05-23 12:44       ` Greg Kurz
2019-05-23  6:06   ` Cédric Le Goater
2019-05-31  6:33 ` Paul Mackerras

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=20190523062715.GR30423@umbus.fritz.box \
    --to=david@gibson.dropbear.id.au \
    --cc=clg@kaod.org \
    --cc=groug@kaod.org \
    --cc=kvm-ppc@vger.kernel.org \
    --cc=kvm@vger.kernel.org \
    --cc=paulus@samba.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