From: Sean Christopherson <seanjc@google.com>
To: Robert Nowotny <rnowotny@rotek.at>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Vitaly Kuznetsov <vkuznets@redhat.com>,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
x86@kernel.org, jostarks@microsoft.com
Subject: Re: [RFC PATCH 0/2] KVM: x86: Relay a nested Hyper-V root's vmbus posts to L0
Date: Wed, 17 Jun 2026 08:53:51 -0700 [thread overview]
Message-ID: <ajLDD6Ck1MF8aD7J@google.com> (raw)
In-Reply-To: <11b87e43-dde8-4fbc-a25e-ee7373c8181d@rotek.at>
On Wed, Jun 17, 2026, Robert Nowotny wrote:
> This RFC asks for direction on a small KVM/x86 addition before adding a
> selftest and an SVM counterpart. It lets a nested Hyper-V root partition's
> vmbus come up when the L1 hypervisor runs under KVM with a userspace VMM that
> owns the host vmbus endpoint.
>
> Patch 1 renames nested_evmcs_l2_tlb_flush_enabled() to
> nested_evmcs_l2_direct_hypercall_enabled(), since the predicate is really
> "L1
> granted this L2 the eVMCS direct-hypercall facility" and a second caller now
> shares it. No functional change.
>
> Patch 2 adds the relay.
I didn't get any patches. Lore doesn't have them either.
next prev parent reply other threads:[~2026-06-17 15:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-17 14:51 [RFC PATCH 0/2] KVM: x86: Relay a nested Hyper-V root's vmbus posts to L0 Robert Nowotny
2026-06-17 15:53 ` Sean Christopherson [this message]
2026-06-17 19:50 ` FW: [RFC PATCH 0/2] KVM: x86: Relay a nested Hyper-V root's vmbus posts to L0 // including patches Robert Nowotny
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=ajLDD6Ck1MF8aD7J@google.com \
--to=seanjc@google.com \
--cc=jostarks@microsoft.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=rnowotny@rotek.at \
--cc=vkuznets@redhat.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.