[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <SA1PR21MB1335F2B44DBF989580A96DB7BF609@SA1PR21MB1335.namprd21.prod.outlook.com>
Date: Fri, 21 Apr 2023 01:36:45 +0000
From: Dexuan Cui <decui@...rosoft.com>
To: Wei Liu <wei.liu@...nel.org>,
"Michael Kelley (LINUX)" <mikelley@...rosoft.com>
CC: KY Srinivasan <kys@...rosoft.com>,
Haiyang Zhang <haiyangz@...rosoft.com>,
"lpieralisi@...nel.org" <lpieralisi@...nel.org>,
"kw@...ux.com" <kw@...ux.com>, "robh@...nel.org" <robh@...nel.org>,
"bhelgaas@...gle.com" <bhelgaas@...gle.com>,
"linux-hyperv@...r.kernel.org" <linux-hyperv@...r.kernel.org>,
"linux-pci@...r.kernel.org" <linux-pci@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: [PATCH] PCI: hv: Replace retarget_msi_interrupt_params with
hyperv_pcpu_input_arg
> From: Wei Liu <wei.liu@...nel.org>
> Sent: Wednesday, April 12, 2023 6:42 PM
> > > ...
> > > The change here is required for PCI device assignment to work for
> > > Confidential VMs (CVMs), because otherwise we would have to call
> > > set_memory_decrypted() for "hbus->retarget_msi_interrupt_params"
> > > before calling the hypercall HVCALL_RETARGET_INTERRUPT.
> >
> > Well, not all CVMs. It's not required for SEV-SNP vTOM VMs on
> > Hyper-V because of the paravisor. Is it more accurate to say
> > "for Confidential VMs (CVMs) running without a paravisor"?
>
> Let me know how this text should be reworded.
Thanks, I just posted v2:
https://lwn.net/ml/linux-kernel/20230421013025.17152-1-decui%40microsoft.com/
Powered by blists - more mailing lists