On Mon, Oct 25, 2021 at 06:28:09AM +0000, Liu, Yi L wrote:
> thanks for the guiding. will also refer to your vfio_group_cdev series.
>
> Need to double confirm here. Not quite following on the kfree. Is
> this kfree to free the vfio_device structure? But now the
> vfio_device pointer is provided by callers (e.g. vfio-pci). Do
> you want to let vfio core allocate the vfio_device struct and
> return the pointer to callers?
There are several common patterns for this problem, two that would be
suitable:
- Require each driver to provide a release op inside vfio_device_ops
that does the kfree. Have the core provide a struct device release
op that calls this one. Keep the kalloc/kfree in the drivers
- Move the kalloc into the core and have the core provide the kfree
with an optional release callback for anydriver specific cleanup
This requires some macro to make the memory layout work. RDMA has
a version of this:
struct ib_device *_ib_alloc_device(size_t size);
#define ib_alloc_device(drv_struct, member) \
container_of(_ib_alloc_device(sizeof(struct drv_struct) + \
BUILD_BUG_ON_ZERO(offsetof( \
struct drv_struct, member))), \
struct drv_struct, member)
In part the choice is how many drivers require a release callback
anyhow, if they all do then the first is easier to understand. If only
few or none do then the latter is less code in drivers, and never
exposes the driver to the tricky transition from alloc to refcount
cleanup.
Jason
