From: Paul Mackerras Date: Fri, 31 May 2019 06:33:38 +0000 Subject: Re: [PATCH 0/3] KVM: PPC: Book3S HV: XIVE: assorted fixes on vCPU and RAM limits Message-Id: <20190531063338.GC26651@blackberry> List-Id: References: <20190520071514.9308-1-clg@kaod.org> In-Reply-To: <20190520071514.9308-1-clg@kaod.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable To: =?iso-8859-1?Q?C=E9dric?= Le Goater Cc: kvm-ppc@vger.kernel.org, David Gibson , kvm@vger.kernel.org On Mon, May 20, 2019 at 09:15:11AM +0200, C=E9dric Le Goater wrote: > Hello, >=20 > Here are a couple of fixes for issues in the XIVE KVM device when > testing the limits : RAM size and number of vCPUS. >=20 > Based on 5.2-rc1. >=20 > Available on GitHub: >=20 > https://github.com/legoater/linux/commits/xive-5.2 >=20 > Thanks, >=20 > C.=20 >=20 > C=E9dric 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.