From: Easwar Hariharan <eahariha@linux.microsoft.com>
To: mhklinux@outlook.com, haiyangz@microsoft.com, wei.liu@kernel.org,
decui@microsoft.com, kys@microsoft.com, corbet@lwn.net,
linux-kernel@vger.kernel.org, linux-hyperv@vger.kernel.org,
linux-doc@vger.kernel.org
Subject: Re: [PATCH v2 2/2] Documentation: hyperv: Improve synic and interrupt handling description
Date: Mon, 13 May 2024 09:05:12 -0700 [thread overview]
Message-ID: <f072acf6-0c25-4199-aaec-f599530d10b2@linux.microsoft.com> (raw)
In-Reply-To: <20240511133818.19649-2-mhklinux@outlook.com>
On 5/11/2024 6:38 AM, mhkelley58@gmail.com wrote:
> From: Michael Kelley <mhklinux@outlook.com>
>
> Current documentation does not describe how Linux handles the synthetic
> interrupt controller (synic) that Hyper-V provides to guest VMs, nor how
> VMBus or timer interrupts are handled. Add text describing the synic and
> reorganize existing text to make this more clear.
>
> Signed-off-by: Michael Kelley <mhklinux@outlook.com>
> ---
> Changes in v2:
> * In clocks.rst, made a hyperlink for the reference to VMBus documentation
> [Easwar Hariharan]
>
> Documentation/virt/hyperv/clocks.rst | 21 +++++---
> Documentation/virt/hyperv/vmbus.rst | 79 ++++++++++++++++++----------
> 2 files changed, 66 insertions(+), 34 deletions(-)
>
LGTM,
Reviewed-by: Easwar Hariharan <eahariha@linux.microsoft.com>
next prev parent reply other threads:[~2024-05-13 16:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-11 13:38 [PATCH v2 1/2] Documentation: hyperv: Update spelling and fix typo mhkelley58
2024-05-11 13:38 ` [PATCH v2 2/2] Documentation: hyperv: Improve synic and interrupt handling description mhkelley58
2024-05-13 16:05 ` Easwar Hariharan [this message]
2024-05-15 12:36 ` Bagas Sanjaya
2024-05-15 11:56 ` [PATCH v2 1/2] Documentation: hyperv: Update spelling and fix typo Bagas Sanjaya
2024-05-28 5:28 ` Wei Liu
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=f072acf6-0c25-4199-aaec-f599530d10b2@linux.microsoft.com \
--to=eahariha@linux.microsoft.com \
--cc=corbet@lwn.net \
--cc=decui@microsoft.com \
--cc=haiyangz@microsoft.com \
--cc=kys@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=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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).