From: Naman Jain <namjain@linux.microsoft.com>
To: mhklinux@outlook.com, haiyangz@microsoft.com, wei.liu@kernel.org,
decui@microsoft.com, corbet@lwn.net, skhan@linuxfoundation.org,
rdunlap@infradead.org, linux-kernel@vger.kernel.org,
linux-hyperv@vger.kernel.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH v2 1/1] Documentation: hyperv: Update docs for PCI pass-thru device support
Date: Fri, 6 Nov 2026 11:11:20 +0530 [thread overview]
Message-ID: <1a768ba9-5848-49d0-b842-b3de2b3e4503@linux.microsoft.com> (raw)
In-Reply-To: <20261105180922.69256-1-mhklinux@outlook.com>
On 11/5/2026 11:39 PM, Michael Kelley wrote:
> Add a section to the documentation describing the IRQ domain and IRQ chip
> hierarchy that is created for virtual PCI devices, including the
> differences on x86 and arm64, and the reasons for those differences.
>
> In the context of the IRQ domain and chip hierarchies, describe how the
> CPU selected for effective affinity is spread across CPUs in the affinity
> masks. Again, account for the differences in x86 and arm64.
>
> Finally, rework existing text on how MSI messages are composed. Provide
> an expanded section on the overall approach that Hyper-V takes to MSI
> messages. The section provides more context on the handling of MSI messages
> in the Hyper-V vPCI driver, and why it is structured the way it is.
>
> Signed-off-by: Michael Kelley <mhklinux@outlook.com>
> ---
> This doc update assumes that the patch to implement effective
> affinity spreading for arm64 SPIs [1] is accepted.
>
> [1] https://lore.kernel.org/linux-hyperv/20261101021928.52649-1-mhklinux@outlook.com/
>
Subject to above patch going in first.
Reviewed-by: Naman Jain <namjain@linux.microsoft.com>
Thanks for addressing the comments Michael.
Regards,
Naman
prev parent reply other threads:[~2026-11-06 5:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-05 18:09 Michael Kelley
2026-11-06 5:41 ` Naman Jain [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=1a768ba9-5848-49d0-b842-b3de2b3e4503@linux.microsoft.com \
--to=namjain@linux.microsoft.com \
--cc=corbet@lwn.net \
--cc=decui@microsoft.com \
--cc=haiyangz@microsoft.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-hyperv@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhklinux@outlook.com \
--cc=rdunlap@infradead.org \
--cc=skhan@linuxfoundation.org \
--cc=wei.liu@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
all inboxes | Powered by JetHome®