From mboxrd@z Thu Jan 1 00:00:00 1970 From: Benjamin Herrenschmidt Subject: Re: [PATCH 00/19] KVM: PPC: Book3S HV: add XIVE native exploitation mode Date: Thu, 24 Jan 2019 08:35:41 +1100 Message-ID: References: <20190107184331.8429-1-clg@kaod.org> <20190122044654.GA15124@blackberry> <2f9b4420-ef90-20b8-d31b-dc547a6aa6b4@kaod.org> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8bit Cc: linuxppc-dev@lists.ozlabs.org, kvm@vger.kernel.org, kvm-ppc@vger.kernel.org, David Gibson To: =?ISO-8859-1?Q?C=E9dric?= Le Goater , Paul Mackerras Return-path: In-Reply-To: <2f9b4420-ef90-20b8-d31b-dc547a6aa6b4@kaod.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: linuxppc-dev-bounces+glppe-linuxppc-embedded-2=m.gmane.org@lists.ozlabs.org Sender: "Linuxppc-dev" List-Id: kvm.vger.kernel.org On Wed, 2019-01-23 at 20:07 +0100, Cédric Le Goater wrote: > Event Assignment Structure, a.k.a IVE (Interrupt Virtualization Entry) > > All the names changed somewhere between XIVE v1 and XIVE v2. OPAL and > Linux should be adjusted ... All the names changed between the HW design and the "architecture" document. The HW guys use the old names, the architecture the new names, and Linux & OPAL mostly use the old ones because frankly the new names suck big time. > It would be good to talk a little about the nested support (offline > may be) to make sure that we are not missing some major interface that > would require a lot of change. If we need to prepare ground, I think > the timing is good. > > The size of the IRQ number space might be a problem. It seems we > would need to increase it considerably to support multiple nested > guests. That said I haven't look much how nested is designed. The size of the VP space is a bigger concern. Even today. We really need qemu to tell the max #cpu to KVM so we can allocate less of them. As for nesting, I suggest for the foreseeable future we stick to XICS emulation in nested guests. Cheers, Ben.