From: Roman Kisel <romank@linux.microsoft.com>
To: Nuno Das Neves <nunodasneves@linux.microsoft.com>
Cc: kys@microsoft.com, haiyangz@microsoft.com, wei.liu@kernel.org,
mhklinux@outlook.com, decui@microsoft.com,
catalin.marinas@arm.com, will@kernel.org, tglx@linutronix.de,
mingo@redhat.com, bp@alien8.de, dave.hansen@linux.intel.com,
hpa@zytor.com, lpieralisi@kernel.org, kw@linux.com,
manivannan.sadhasivam@linaro.org, robh@kernel.org,
bhelgaas@google.com, jinankjain@linux.microsoft.com,
skinsburskii@linux.microsoft.com, mrathor@linux.microsoft.com,
x86@kernel.org, linux-hyperv@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org
Subject: Re: [PATCH 0/4] Nested virtualization fixes for root partition
Date: Wed, 11 Jun 2025 10:55:35 -0700 [thread overview]
Message-ID: <2c8d534b-02c5-4149-882b-40eb27671614@linux.microsoft.com> (raw)
In-Reply-To: <1749599526-19963-1-git-send-email-nunodasneves@linux.microsoft.com>
On 6/10/2025 4:52 PM, Nuno Das Neves wrote:
> Fixes for running as nested root partition on the Microsoft Hypervisor.
>
> The first patch prevents the vmbus driver being registered on baremetal, since
> there's no vmbus in this scenario.
>
> The second patch changes vmbus to make hypercalls to the L0 hypervisor instead
> of the L1. This is needed because L0 hypervisor, not the L1, is the one hosting
> the Windows root partition with the VMM that provides vmbus.
>
> The 3rd and 4th patches fix interrupt unmasking on nested. In this scenario,
> the L1 (nested) hypervisor does the interrupt mapping to root partition cores.
> The vectors just need to be mapped with MAP_DEVICE_INTERRUPT instead of
> affinitized with RETARGET_INTERRUPT.
>
> Mukesh Rathor (1):
> PCI: hv: Do not do vmbus initialization on baremetal
>
> Nuno Das Neves (1):
> Drivers: hv: Use nested hypercall for post message and signal event
>
> Stanislav Kinsburskii (2):
> x86: hyperv: Expose hv_map_msi_interrupt function
> PCI: hv: Use the correct hypercall for unmasking interrupts on nested
>
> arch/arm64/include/asm/mshyperv.h | 10 ++++++
> arch/x86/hyperv/irqdomain.c | 47 +++++++++++++++++++++--------
> arch/x86/include/asm/mshyperv.h | 2 ++
> drivers/hv/connection.c | 3 ++
> drivers/hv/hv.c | 3 ++
> drivers/pci/controller/pci-hyperv.c | 21 +++++++++++--
> 6 files changed, 71 insertions(+), 15 deletions(-)
>
Very cool stuff :) LGTM.
For the patch series:
Reviewed-by: Roman Kisel <romank@linux.microsoft.com>
--
Thank you,
Roman
prev parent reply other threads:[~2025-06-11 17:55 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-10 23:52 [PATCH 0/4] Nested virtualization fixes for root partition Nuno Das Neves
2025-06-10 23:52 ` [PATCH 1/4] PCI: hv: Do not do vmbus initialization on baremetal Nuno Das Neves
2025-06-11 23:06 ` Michael Kelley
2025-06-16 20:06 ` Nuno Das Neves
2025-06-10 23:52 ` [PATCH 2/4] Drivers: hv: Use nested hypercall for post message and signal event Nuno Das Neves
2025-06-11 23:06 ` Michael Kelley
2025-06-16 20:18 ` Nuno Das Neves
2025-06-10 23:52 ` [PATCH 3/4] x86: hyperv: Expose hv_map_msi_interrupt function Nuno Das Neves
2025-06-11 23:07 ` Michael Kelley
2025-06-18 21:08 ` Nuno Das Neves
2025-06-19 22:02 ` Michael Kelley
2025-06-20 16:19 ` Thomas Gleixner
2025-06-23 22:13 ` Nuno Das Neves
2025-06-10 23:52 ` [PATCH 4/4] PCI: hv: Use the correct hypercall for unmasking interrupts on nested Nuno Das Neves
2025-06-11 23:07 ` Michael Kelley
2025-06-18 21:24 ` Nuno Das Neves
2025-06-13 19:36 ` Bjorn Helgaas
2025-06-18 22:45 ` Nuno Das Neves
2025-06-11 17:55 ` Roman Kisel [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2c8d534b-02c5-4149-882b-40eb27671614@linux.microsoft.com \
--to=romank@linux.microsoft.com \
--cc=bhelgaas@google.com \
--cc=bp@alien8.de \
--cc=catalin.marinas@arm.com \
--cc=dave.hansen@linux.intel.com \
--cc=decui@microsoft.com \
--cc=haiyangz@microsoft.com \
--cc=hpa@zytor.com \
--cc=jinankjain@linux.microsoft.com \
--cc=kw@linux.com \
--cc=kys@microsoft.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-hyperv@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=mhklinux@outlook.com \
--cc=mingo@redhat.com \
--cc=mrathor@linux.microsoft.com \
--cc=nunodasneves@linux.microsoft.com \
--cc=robh@kernel.org \
--cc=skinsburskii@linux.microsoft.com \
--cc=tglx@linutronix.de \
--cc=wei.liu@kernel.org \
--cc=will@kernel.org \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox