On Thu, May 15, 2025 at 12:54 AM Michael Kelley <[email protected]> wrote:
>
> From: Tianyu Lan <[email protected]> Sent: Tuesday, May 6, 2025 6:07 AM
> >
> >  void __init hv_apic_init(void)
> >  {
> > +     if (cc_platform_has(CC_ATTR_SNP_SECURE_AVIC))
> > +             return;
> > +
> >       if (ms_hyperv.hints & HV_X64_CLUSTER_IPI_RECOMMENDED) {
> >               pr_info("Hyper-V: Using IPI hypercalls\n");
> >               /*
>
> It seems like this patch will cause a bisect problem if a bisect includes
> this patch but none of the subsequent patches in this series. The
> Hyper-V guest VM could see Secure AVIC is enabled, but the VM
> wouldn't boot because the code to allow Hyper-V to inject an interrupt
> haven't been added yet.
>
> This patch probably should come later in the patch series after Secure
> AVIC can be functional in a Hyper-V guest.
>

Good idea! Will rework patch order.

-- 
Thanks
Tianyu Lan

Reply via email to