[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <bfe244a08572b1d57dcb5c538bcb70e9f45761f6.camel@infradead.org>
Date: Wed, 18 Jan 2023 14:43:13 +0000
From: David Woodhouse <dwmw2@...radead.org>
To: Andrew Cooper <Andrew.Cooper3@...rix.com>,
Juergen Gross <jgross@...e.com>,
Stefano Stabellini <sstabellini@...nel.org>,
xen-devel <xen-devel@...ts.xenproject.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Thomas Gleixner <tglx@...utronix.de>,
Paul Durrant <paul@....org>
Subject: Re: [PATCH] xen: Allow platform PCI interrupt to be shared
On Wed, 2023-01-18 at 14:39 +0000, Andrew Cooper wrote:
> On 18/01/2023 2:26 pm, David Woodhouse wrote:?
> > > There is no actual thing called PVHVM. That diagram has caused far more
> > > damage than good...
> > >
> > > There's HVM (and by this, I mean the hypervisor's interpretation meaning
> > > VT-x or SVM), and a spectrum of things the guest kernel can do if it
> > > desires.
> > >
> > > I'm pretty sure Linux knows all of them.
> >
> > But don't we want to refrain from providing the legacy PC platform devices?
>
> That also exists and works fine (and is one slice on the spectrum). KVM
> even borrowed our PVH boot API because we'd already done the hard work
> in Linux.
Ah, but it doesn't exist in qemu (on KVM) yet ;)
Download attachment "smime.p7s" of type "application/pkcs7-signature" (5965 bytes)
Powered by blists - more mailing lists