> -----Original Message-----
> From: Michael Kelley <[email protected]>
> Sent: Wednesday, April 30, 2025 6:56 PM
> To: [email protected]; KY Srinivasan <[email protected]>; Haiyang
> Zhang <[email protected]>; Wei Liu <[email protected]>; Dexuan Cui
> <[email protected]>; Greg Kroah-Hartman
> <[email protected]>; [email protected]; linux-
> [email protected]
> Cc: Long Li <[email protected]>; [email protected]
> Subject: [EXTERNAL] RE: [Patch v2 1/4] Drivers: hv: Allocate interrupt and
> monitor pages aligned to system page boundary
>
> From: [email protected] <[email protected]> Sent:
> Wednesday, April 30, 2025 3:06 PM
> >
> > There are use cases that interrupt and monitor pages are mapped to
> > user-mode through UIO, they need to be system page aligned. Some
> > Hyper-V
>
> s/UIO, they/UIO, so they/
>
> > allocation APIs introduced earlier broke those requirements.
> >
> > Fix those APIs by always allocating Hyper-V page at system page boundaries.
>
> This patch modifies hv_alloc_hyperv_page() and friends. Then Patch 4 of the
> series deletes them, including the modifications. It would be less code motion
> to do the first part of Patch 4 (i.e., the use of __get_free_page directly in
> connection.c) here in Patch 1, and leave hv_alloc_hyperv_page() and friends
> unmodified. Continue to make the change to hv_kmsg_dump_register() here
> in Patch 1 as well.
>
> Then have Patch 2 simply delete hv_alloc_hyperv_page() and friends because
> they are no longer used. The modifications to hv_alloc_hyperv_page() and
> friends would not be needed.
>
> Patch 3 and 4 would be the additional changes in uio_hv_generic.c.
>
> Michael
I have sent v3 of the patch series.
Long
