From: Paul Mackerras <paulus@ozlabs.org>
To: "Cédric Le Goater" <clg@kaod.org>
Cc: kvm-ppc@vger.kernel.org,
David Gibson <david@gibson.dropbear.id.au>,
kvm@vger.kernel.org
Subject: Re: [PATCH 0/3] KVM: PPC: Book3S HV: XIVE: assorted fixes on vCPU and RAM limits
Date: Fri, 31 May 2019 16:33:38 +1000 [thread overview]
Message-ID: <20190531063338.GC26651@blackberry> (raw)
In-Reply-To: <20190520071514.9308-1-clg@kaod.org>
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.
>
> 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
Thanks, series applied to my kvm-ppc-fixes branch.
Paul.
prev parent reply other threads:[~2019-05-31 6:38 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
2019-05-23 12:44 ` Greg Kurz
2019-05-23 6:06 ` Cédric Le Goater
2019-05-31 6:33 ` Paul Mackerras [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=20190531063338.GC26651@blackberry \
--to=paulus@ozlabs.org \
--cc=clg@kaod.org \
--cc=david@gibson.dropbear.id.au \
--cc=kvm-ppc@vger.kernel.org \
--cc=kvm@vger.kernel.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