linux-kernel - RE: [PATCH] PCI: hv: Use nested hypercall for retargeting interrupts

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <BYAPR21MB168827DA138ADE39298FFB37D7989@BYAPR21MB1688.namprd21.prod.outlook.com>
Date:   Thu, 13 Apr 2023 03:05:09 +0000
From:   "Michael Kelley (LINUX)" <mikelley@...rosoft.com>
To:     Wei Liu <wei.liu@...nel.org>,
        Jinank Jain <jinankjain@...ux.microsoft.com>,
        "g@...we-devbox-debian-v2" <g@...we-devbox-debian-v2>
CC:     Jinank Jain <jinankjain@...rosoft.com>,
        KY Srinivasan <kys@...rosoft.com>,
        Haiyang Zhang <haiyangz@...rosoft.com>,
        Dexuan Cui <decui@...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>,
        "nunodasneves@...ux.microsoft.com" <nunodasneves@...ux.microsoft.com>
Subject: RE: [PATCH] PCI: hv: Use nested hypercall for retargeting interrupts

From: Wei Liu <wei.liu@...nel.org> Sent: Wednesday, April 12, 2023 6:23 PM
> 
> On Tue, Apr 04, 2023 at 11:35:46AM +0000, Jinank Jain wrote:
> > In case of nested MSHV, retargeting interrupt hypercall should be sent
> > to L0 hypervisor instead of L1 hypervisor.
> >
> > Signed-off-by: Jinank Jain <jinankjain@...ux.microsoft.com>
> 
> Applied to hyperv-next. Thanks.

I'd like to hold off on taking this change.  Nuno and I are discussing
how best to handle nested hypercalls.  In addition to the proposed
nested changes,  we have hypercall changes coming as part of the
TDX and fully enlightened SNP patch sets.  If possible, I'd like to
avoid adding logic at the hv_do_hypercall() call sites.  It's not clear
whether avoiding such logic will really be feasible, but I'd like to
think about it for a bit before reaching that conclusion.

Michael