[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250102205246.GG5556@nvidia.com>
Date: Thu, 2 Jan 2025 16:52:46 -0400
From: Jason Gunthorpe <jgg@...dia.com>
To: Nicolin Chen <nicolinc@...dia.com>
Cc: kevin.tian@...el.com, will@...nel.org, corbet@....net, joro@...tes.org,
suravee.suthikulpanit@....com, robin.murphy@....com,
dwmw2@...radead.org, baolu.lu@...ux.intel.com, shuah@...nel.org,
linux-kernel@...r.kernel.org, iommu@...ts.linux.dev,
linux-arm-kernel@...ts.infradead.org,
linux-kselftest@...r.kernel.org, linux-doc@...r.kernel.org,
eric.auger@...hat.com, jean-philippe@...aro.org, mdf@...nel.org,
mshavit@...gle.com, shameerali.kolothum.thodi@...wei.com,
smostafa@...gle.com, ddutile@...hat.com, yi.l.liu@...el.com,
patches@...ts.linux.dev
Subject: Re: [PATCH v3 06/14] iommufd: Add IOMMUFD_OBJ_VIRQ and
IOMMUFD_CMD_VIRQ_ALLOC
On Tue, Dec 17, 2024 at 09:00:19PM -0800, Nicolin Chen wrote:
> +/* An iommufd_virq_header packs a vIOMMU interrupt in an iommufd_virq queue */
> +struct iommufd_virq_header {
> + struct list_head node;
> + ssize_t irq_len;
> + void *irq_data;
> +};
Based on how it is used in iommufd_viommu_report_irq()
+ header = kzalloc(sizeof(*header) + irq_len, GFP_KERNEL);
+ header->irq_data = (void *)header + sizeof(*header);
+ memcpy(header->irq_data, irq_ptr, irq_len);
It should be a flex array and use the various flexarray tools
struct iommufd_virq_header {
ssize_t irq_len;
u64 irq_data[] __counted_by(irq_len);
}
Jason
Powered by blists - more mailing lists