From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Wei Liu <wei.liu@kernel.org>
Cc: longli@linuxonhyperv.com, "K. Y. Srinivasan" <kys@microsoft.com>,
Haiyang Zhang <haiyangz@microsoft.com>,
Dexuan Cui <decui@microsoft.com>,
linux-hyperv@vger.kernel.org, linux-kernel@vger.kernel.org,
Long Li <longli@microsoft.com>
Subject: Re: [Patch v3] uio_hv_generic: Set event for all channels on the device
Date: Tue, 25 Mar 2025 12:39:54 -0400 [thread overview]
Message-ID: <2025032533-sassy-blinker-85de@gregkh> (raw)
In-Reply-To: <Z-LVk8jWkalG5KdD@liuwe-devbox-ubuntu-v2.lamzopl0uupeniq2etz1fddiyg.xx.internal.cloudapp.net>
On Tue, Mar 25, 2025 at 04:10:59PM +0000, Wei Liu wrote:
> On Mon, Mar 10, 2025 at 03:12:01PM -0700, longli@linuxonhyperv.com wrote:
> > From: Long Li <longli@microsoft.com>
> >
> > Hyper-V may offer a non latency sensitive device with subchannels without
> > monitor bit enabled. The decision is entirely on the Hyper-V host not
> > configurable within guest.
> >
> > When a device has subchannels, also signal events for the subchannel
> > if its monitor bit is disabled.
> >
> > This patch also removes the memory barrier when monitor bit is enabled
> > as it is not necessary. The memory barrier is only needed between
> > setting up interrupt mask and calling vmbus_set_event() when monitor
> > bit is disabled.
> >
> > Signed-off-by: Long Li <longli@microsoft.com>
>
> Greg, are you going to take this patch?
>
> I can take it if you want.
It's the merge window right now, neither of us should be taking it. Let
me look into it after -rc1 is out.
thanks,
greg k-h
next prev parent reply other threads:[~2025-03-25 16:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-10 22:12 [Patch v3] uio_hv_generic: Set event for all channels on the device longli
2025-03-11 3:47 ` Michael Kelley
2025-03-11 4:12 ` Saurabh Singh Sengar
2025-03-25 16:10 ` Wei Liu
2025-03-25 16:39 ` Greg Kroah-Hartman [this message]
2025-03-25 17:59 ` 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=2025032533-sassy-blinker-85de@gregkh \
--to=gregkh@linuxfoundation.org \
--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@linuxonhyperv.com \
--cc=longli@microsoft.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 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.