From: Wei Liu <wei.liu@kernel.org>
To: Anirudh Rayabharam <anirudh@anirudhrb.com>
Cc: kys@microsoft.com, haiyangz@microsoft.com, wei.liu@kernel.org,
decui@microsoft.com, longli@microsoft.com,
linux-hyperv@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v6 0/2] ARM64 support for doorbell and intercept SINTs
Date: Wed, 25 Feb 2026 19:49:23 +0000 [thread overview]
Message-ID: <20260225194923.GB413976@liuwe-devbox-debian-v2.local> (raw)
In-Reply-To: <20260225124403.2187880-1-anirudh@anirudhrb.com>
On Wed, Feb 25, 2026 at 12:44:01PM +0000, Anirudh Rayabharam wrote:
> From: "Anirudh Rayabharam (Microsoft)" <anirudh@anirudhrb.com>
>
> On x86, the HYPERVISOR_CALLBACK_VECTOR is used to receive synthetic
> interrupts (SINTs) from the hypervisor for doorbells and intercepts.
> There is no such vector reserved for arm64.
>
> On arm64, the hypervisor exposes a synthetic register that can be read
> to find the INTID that should be used for SINTs. This INTID is in the
> PPI range.
>
[...]
> Anirudh Rayabharam (Microsoft) (2):
> mshv: refactor synic init and cleanup
> mshv: add arm64 support for doorbell & intercept SINTs
>
> drivers/hv/mshv_root.h | 5 +-
> drivers/hv/mshv_root_main.c | 64 ++----------
> drivers/hv/mshv_synic.c | 188 +++++++++++++++++++++++++++++++++---
> include/hyperv/hvgdk_mini.h | 2 +
> 4 files changed, 185 insertions(+), 74 deletions(-)
Applied to hyperv-fixes.
I debated a bit whether this is a new feature or a fix and decided it
fixes an important gap in arm64 support.
Wei
>
> --
> 2.34.1
>
>
prev parent reply other threads:[~2026-02-25 19:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-25 12:44 [PATCH v6 0/2] ARM64 support for doorbell and intercept SINTs Anirudh Rayabharam
2026-02-25 12:44 ` [PATCH v6 1/2] mshv: refactor synic init and cleanup Anirudh Rayabharam
2026-02-25 19:05 ` Wei Liu
2026-02-25 12:44 ` [PATCH v6 2/2] mshv: add arm64 support for doorbell & intercept SINTs Anirudh Rayabharam
2026-02-25 19:49 ` Wei Liu [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=20260225194923.GB413976@liuwe-devbox-debian-v2.local \
--to=wei.liu@kernel.org \
--cc=anirudh@anirudhrb.com \
--cc=decui@microsoft.com \
--cc=haiyangz@microsoft.com \
--cc=kys@microsoft.com \
--cc=linux-hyperv@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=longli@microsoft.com \
/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