From: "Cédric Le Goater" <clg@redhat.com>
To: mhonap@nvidia.com, alex@shazbot.org, ankita@nvidia.com,
jic23@kernel.org, dave.jiang@intel.com,
alejandro.lucero-palau@amd.com, smadhavan@nvidia.com,
pierrick.bouvier@oss.qualcomm.com, mst@redhat.com,
imammedo@redhat.com, anisinha@redhat.com, pbonzini@redhat.com,
eric.auger@redhat.com, peter.maydell@linaro.org,
richard.henderson@linaro.org, cohuck@redhat.com
Cc: kjaju@nvidia.com, vsethi@nvidia.com, zhiw@nvidia.com,
qemu-devel@nongnu.org, qemu-arm@nongnu.org,
linux-cxl@vger.kernel.org
Subject: Re: [PATCH v2 02/10] hw/vfio/region: Add vfio_region_setup_with_ops()
Date: Thu, 17 Sep 2026 15:27:29 +0200 [thread overview]
Message-ID: <3d799d0d-1365-4bbb-a159-c8d926f2863c@redhat.com> (raw)
In-Reply-To: <20260916184412.3825713-3-mhonap@nvidia.com>
On 9/16/26 20:44, mhonap@nvidia.com wrote:
> From: Manish Honap <mhonap@nvidia.com>
>
> A CXL Type-2 device traps its HDM decoder block, so that region needs
> custom MemoryRegionOps rather than the pass-through default. Split the
> setup body out and let a caller supply the ops; NULL keeps the existing
> behaviour.
>
> AI-used-for: code (prototype)
> Signed-off-by: Manish Honap <mhonap@nvidia.com>
> ---
> hw/vfio/region.c | 27 ++++++++++++++++++++++++---
> hw/vfio/vfio-region.h | 3 +++
> 2 files changed, 27 insertions(+), 3 deletions(-)
>
> diff --git a/hw/vfio/region.c b/hw/vfio/region.c
> index 54ad11a6c8..21b54978b5 100644
> --- a/hw/vfio/region.c
> +++ b/hw/vfio/region.c
> @@ -228,8 +228,9 @@ static int vfio_setup_region_sparse_mmaps(VFIORegion *region,
> return 0;
> }
>
> -int vfio_region_setup(Object *obj, VFIODevice *vbasedev, VFIORegion *region,
> - int index, const char *name, Error **errp)
> +static int vfio_region_do_setup(Object *obj, VFIODevice *vbasedev,
> + VFIORegion *region, int index, const char *name,
> + const MemoryRegionOps *ops, Error **errp)
> {
> struct vfio_region_info *info = NULL;
> int ret;
> @@ -249,7 +250,7 @@ int vfio_region_setup(Object *obj, VFIODevice *vbasedev, VFIORegion *region,
>
> if (region->size) {
> region->mem = g_new0(MemoryRegion, 1);
> - memory_region_init_io(region->mem, obj, &vfio_region_ops,
> + memory_region_init_io(region->mem, obj, ops,
> region, name, region->size);
>
> if (!vbasedev->no_mmap &&
> @@ -273,6 +274,26 @@ int vfio_region_setup(Object *obj, VFIODevice *vbasedev, VFIORegion *region,
> return 0;
> }
>
> +int vfio_region_setup(Object *obj, VFIODevice *vbasedev, VFIORegion *region,
> + int index, const char *name, Error **errp)
> +{
> + return vfio_region_do_setup(obj, vbasedev, region, index, name,
> + &vfio_region_ops, errp);
> +}
> +
> +/*
> + * Like vfio_region_setup() but traps the region through @ops instead of the
> + * default pass-through, so a caller can intercept accesses (the CXL HDM
> + * decoder block). A NULL @ops keeps the default.
> + */
> +int vfio_region_setup_with_ops(Object *obj, VFIODevice *vbasedev,
> + VFIORegion *region, int index, const char *name,
> + const MemoryRegionOps *ops, Error **errp)
> +{
> + return vfio_region_do_setup(obj, vbasedev, region, index, name,
> + ops ? ops : &vfio_region_ops, errp);
if you're calling _with_ops(), you have custom ops, that's whole point.
Passing NULL is a caller bug, no need to have a fall back. Or assert().
Thanks,
C.
> +}
> +
> static void vfio_subregion_unmap(VFIORegion *region, int index)
> {
> trace_vfio_region_unmap(memory_region_name(®ion->mmaps[index].mem),
> diff --git a/hw/vfio/vfio-region.h b/hw/vfio/vfio-region.h
> index 58b236f113..8d5699013a 100644
> --- a/hw/vfio/vfio-region.h
> +++ b/hw/vfio/vfio-region.h
> @@ -39,6 +39,9 @@ uint64_t vfio_region_read(void *opaque,
> hwaddr addr, unsigned size);
> int vfio_region_setup(Object *obj, VFIODevice *vbasedev, VFIORegion *region,
> int index, const char *name, Error **errp);
> +int vfio_region_setup_with_ops(Object *obj, VFIODevice *vbasedev,
> + VFIORegion *region, int index, const char *name,
> + const MemoryRegionOps *ops, Error **errp);
> int vfio_region_mmap(VFIORegion *region);
> void vfio_region_mmaps_set_enabled(VFIORegion *region, bool enabled);
> void vfio_region_exit(VFIORegion *region);
next prev parent reply other threads:[~2026-09-17 13:27 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-16 18:44 [PATCH v2 00/10] QEMU: CXL Type-2 device passthrough via vfio-pci mhonap
2026-09-16 18:44 ` [PATCH v2 01/10] linux-headers: Update vfio.h for CXL Type-2 passthrough mhonap
2026-09-16 18:44 ` [PATCH v2 02/10] hw/vfio/region: Add vfio_region_setup_with_ops() mhonap
2026-09-17 13:27 ` Cédric Le Goater [this message]
2026-09-21 10:48 ` Manish Honap
2026-09-16 18:44 ` [PATCH v2 03/10] hw/vfio/pci: Detect a CXL Type-2 device and read its geometry mhonap
2026-09-17 16:04 ` Cédric Le Goater
2026-09-21 10:49 ` Manish Honap
2026-09-16 18:44 ` [PATCH v2 04/10] hw/vfio/pci: Enforce the passthrough topology for a CXL device mhonap
2026-09-17 13:20 ` Cédric Le Goater
2026-09-21 10:45 ` Manish Honap
2026-09-16 18:44 ` [PATCH v2 05/10] hw/vfio/pci: Back the CXL memory with a RAM-device region mhonap
2026-09-17 13:56 ` Cédric Le Goater
2026-09-21 10:55 ` Manish Honap
2026-09-16 18:44 ` [PATCH v2 06/10] hw/vfio/pci: Bind a CXL device to its fixed memory window mhonap
2026-09-17 16:00 ` Cédric Le Goater
2026-09-21 11:03 ` Manish Honap
2026-09-16 18:44 ` [PATCH v2 07/10] hw/vfio/pci: Map the CXL memory on the guest decoder commit mhonap
2026-09-18 16:08 ` Cédric Le Goater
2026-09-21 11:14 ` Manish Honap
2026-09-20 9:14 ` Junjie Cao
2026-09-21 11:17 ` Manish Honap
2026-09-16 18:44 ` [PATCH v2 08/10] docs/cxl: Document CXL Type-2 device passthrough mhonap
2026-09-16 18:44 ` [PATCH v2 09/10] hw/arm/smmu-common: Allow pxb-cxl as an SMMUv3 primary bus mhonap
2026-09-16 18:44 ` [PATCH v2 10/10] hw/pci-host: Emit a _DSM on pxb-cxl to preserve firmware PCI config mhonap
2026-09-20 9:14 ` Junjie Cao
2026-09-21 11:20 ` Manish Honap
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=3d799d0d-1365-4bbb-a159-c8d926f2863c@redhat.com \
--to=clg@redhat.com \
--cc=alejandro.lucero-palau@amd.com \
--cc=alex@shazbot.org \
--cc=anisinha@redhat.com \
--cc=ankita@nvidia.com \
--cc=cohuck@redhat.com \
--cc=dave.jiang@intel.com \
--cc=eric.auger@redhat.com \
--cc=imammedo@redhat.com \
--cc=jic23@kernel.org \
--cc=kjaju@nvidia.com \
--cc=linux-cxl@vger.kernel.org \
--cc=mhonap@nvidia.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=pierrick.bouvier@oss.qualcomm.com \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=smadhavan@nvidia.com \
--cc=vsethi@nvidia.com \
--cc=zhiw@nvidia.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