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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



From: Wei Liu <wei.liu@xxxxxxxxxx> 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@xxxxxxxxxxxxxxxxxxx>
> 
> 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





[Index of Archives]     [Linux Samsung SoC]     [Linux Rockchip SoC]     [Linux Actions SoC]     [Linux for Synopsys ARC Processors]     [Linux NFS]     [Linux NILFS]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]


  Powered by Linux