From: Wei Liu <wei.liu@kernel.org>
To: longli@linuxonhyperv.com
Cc: "K. Y. Srinivasan" <kys@microsoft.com>,
Haiyang Zhang <haiyangz@microsoft.com>,
Wei Liu <wei.liu@kernel.org>, Dexuan Cui <decui@microsoft.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-hyperv@vger.kernel.org, linux-kernel@vger.kernel.org,
Long Li <longli@microsoft.com>
Subject: Re: [Patch v3 0/5] Fix uio_hv_generic on systems with >4k page sizes
Date: Tue, 13 May 2025 04:49:50 +0000 [thread overview]
Message-ID: <aCLPbob_vVopoMt9@liuwe-devbox-ubuntu-v2.tail21d00.ts.net> (raw)
In-Reply-To: <aBz8fBWQKfH04g2u@liuwe-devbox-ubuntu-v2.tail21d00.ts.net>
On Thu, May 08, 2025 at 06:48:28PM +0000, Wei Liu wrote:
> On Mon, May 05, 2025 at 05:56:32PM -0700, longli@linuxonhyperv.com wrote:
> > From: Long Li <longli@microsoft.com>
> >
> > UIO framework requires the device memory aligned to page boundary.
> > Hyper-V may allocate some memory that is Hyper-V page aligned (4k)
> > but not system page aligned.
> >
> > Fix this by having Hyper-V always allocate those pages on system page
> > boundary and expose them to user-mode.
> >
> > Change in v2:
> > Added two more patches to the series:
> > "uio_hv_generic: Adjust ring size according to system page alignment"
> > "Drivers: hv: Remove hv_free/alloc_* helpers"
> >
> > Added more details in the commit message of
> > "uio_hv_generic: Use correct size for interrupt and monitor pages"
> >
> > Change in v3:
> > Rearranged the patch on removing hv_alloc/free* helpers
> > Added "Drivers: hv: Use kzalloc for panic page allocation"
> > Fixed typos.
> >
> > Long Li (5):
> > Drivers: hv: Allocate interrupt and monitor pages aligned to system
> > page boundary
> > uio_hv_generic: Use correct size for interrupt and monitor pages
> > uio_hv_generic: Align ring size to system page
>
> These patches to UIO look like small bug fixes to me.
>
> Greg, let me know if you care enough to review them.
>
> Given the patches surround these bug fixes, I propose to let me take
> them via the Hyper-V tree.
Series applied to hyperv-next-staging. Thanks.
prev parent reply other threads:[~2025-05-13 4:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-06 0:56 [Patch v3 0/5] Fix uio_hv_generic on systems with >4k page sizes longli
2025-05-06 0:56 ` [Patch v3 1/5] Drivers: hv: Allocate interrupt and monitor pages aligned to system page boundary longli
2025-05-07 15:47 ` Michael Kelley
2025-05-06 0:56 ` [Patch v3 2/5] uio_hv_generic: Use correct size for interrupt and monitor pages longli
2025-05-07 15:47 ` Michael Kelley
2025-05-06 0:56 ` [Patch v3 3/5] uio_hv_generic: Align ring size to system page longli
2025-05-07 15:48 ` Michael Kelley
2025-05-06 0:56 ` [Patch v3 4/5] Drivers: hv: Use kzalloc for panic page allocation longli
2025-05-07 15:48 ` Michael Kelley
2025-05-06 0:56 ` [Patch v3 5/5] Drivers: hv: Remove hv_alloc/free_* helpers longli
2025-05-07 15:49 ` Michael Kelley
2025-05-08 18:48 ` [Patch v3 0/5] Fix uio_hv_generic on systems with >4k page sizes Wei Liu
2025-05-13 4: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=aCLPbob_vVopoMt9@liuwe-devbox-ubuntu-v2.tail21d00.ts.net \
--to=wei.liu@kernel.org \
--cc=decui@microsoft.com \
--cc=gregkh@linuxfoundation.org \
--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 \
/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 NNTP newsgroup(s).