[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240430163733.GT941030@nvidia.com>
Date: Tue, 30 Apr 2024 13:37:33 -0300
From: Jason Gunthorpe <jgg@...dia.com>
To: Nicolin Chen <nicolinc@...dia.com>
Cc: will@...nel.org, robin.murphy@....com, joro@...tes.org,
thierry.reding@...il.com, vdumpa@...dia.com, jonathanh@...dia.com,
linux-kernel@...r.kernel.org, iommu@...ts.linux.dev,
linux-arm-kernel@...ts.infradead.org, linux-tegra@...r.kernel.org
Subject: Re: [PATCH v6 2/6] iommu/arm-smmu-v3: Add CS_NONE quirk
On Tue, Apr 30, 2024 at 09:30:43AM -0700, Nicolin Chen wrote:
> > queue_write(Q_ENT(q, cons), cmd, q->ent_dwords);
>
> Here is the only caller for "msi=false". Maybe we could just do:
> + arm_smmu_cmdq_build_sync_cmd(cmd, smmu, q, cons);
>
> So, no need of "bool msi"? It would slightly change the behavior
> though, a SYNC for ARM_SMMU_OPT_MSIPOLL should be still a SYNC.
I don't know, I didn't try to figure out what to stick for prod in
that case. It is probably OK to convert an error entry into a MSI
sync if it works out?
Jason
Powered by blists - more mailing lists