All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgg@nvidia.com>
To: Nicolin Chen <nicolinc@nvidia.com>
Cc: will@kernel.org, robin.murphy@arm.com, joro@8bytes.org,
	thierry.reding@gmail.com, vdumpa@nvidia.com,
	jonathanh@nvidia.com, linux-kernel@vger.kernel.org,
	iommu@lists.linux.dev, linux-arm-kernel@lists.infradead.org,
	linux-tegra@vger.kernel.org
Subject: Re: [PATCH v6 2/6] iommu/arm-smmu-v3: Add CS_NONE quirk
Date: Tue, 30 Apr 2024 13:37:33 -0300	[thread overview]
Message-ID: <20240430163733.GT941030@nvidia.com> (raw)
In-Reply-To: <ZjEcs4rY1HpPz4Oa@Asurada-Nvidia>

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

WARNING: multiple messages have this Message-ID (diff)
From: Jason Gunthorpe <jgg@nvidia.com>
To: Nicolin Chen <nicolinc@nvidia.com>
Cc: will@kernel.org, robin.murphy@arm.com, joro@8bytes.org,
	thierry.reding@gmail.com, vdumpa@nvidia.com,
	jonathanh@nvidia.com, linux-kernel@vger.kernel.org,
	iommu@lists.linux.dev, linux-arm-kernel@lists.infradead.org,
	linux-tegra@vger.kernel.org
Subject: Re: [PATCH v6 2/6] iommu/arm-smmu-v3: Add CS_NONE quirk
Date: Tue, 30 Apr 2024 13:37:33 -0300	[thread overview]
Message-ID: <20240430163733.GT941030@nvidia.com> (raw)
In-Reply-To: <ZjEcs4rY1HpPz4Oa@Asurada-Nvidia>

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

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2024-04-30 16:37 UTC|newest]

Thread overview: 56+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-30  4:43 [PATCH v6 0/6] Add Tegra241 (Grace) CMDQV Support (part 1/2) Nicolin Chen
2024-04-30  4:43 ` Nicolin Chen
2024-04-30  4:43 ` [PATCH v6 1/6] iommu/arm-smmu-v3: Pass in cmdq pointer to arm_smmu_cmdq_issue_cmdlist() Nicolin Chen
2024-04-30  4:43   ` Nicolin Chen
2024-04-30 13:54   ` Jason Gunthorpe
2024-04-30 13:54     ` Jason Gunthorpe
2024-04-30  4:43 ` [PATCH v6 2/6] iommu/arm-smmu-v3: Add CS_NONE quirk Nicolin Chen
2024-04-30  4:43   ` Nicolin Chen
2024-04-30 14:22   ` Jason Gunthorpe
2024-04-30 14:22     ` Jason Gunthorpe
2024-04-30 16:30     ` Nicolin Chen
2024-04-30 16:30       ` Nicolin Chen
2024-04-30 16:37       ` Jason Gunthorpe [this message]
2024-04-30 16:37         ` Jason Gunthorpe
2024-04-30 16:43         ` Nicolin Chen
2024-04-30 16:43           ` Nicolin Chen
2024-04-30  4:43 ` [PATCH v6 3/6] iommu/arm-smmu-v3: Make arm_smmu_cmdq_init reusable Nicolin Chen
2024-04-30  4:43   ` Nicolin Chen
2024-04-30 14:24   ` Jason Gunthorpe
2024-04-30 14:24     ` Jason Gunthorpe
2024-04-30 15:50     ` Nicolin Chen
2024-04-30 15:50       ` Nicolin Chen
2024-04-30  4:43 ` [PATCH v6 4/6] iommu/arm-smmu-v3: Make __arm_smmu_cmdq_skip_err reusable Nicolin Chen
2024-04-30  4:43   ` Nicolin Chen
2024-04-30 14:06   ` Jason Gunthorpe
2024-04-30 14:06     ` Jason Gunthorpe
2024-04-30 15:48     ` Nicolin Chen
2024-04-30 15:48       ` Nicolin Chen
2024-04-30  4:43 ` [PATCH v6 5/6] iommu/arm-smmu-v3: Add in-kernel support for NVIDIA Tegra241 (Grace) CMDQV Nicolin Chen
2024-04-30  4:43   ` Nicolin Chen
2024-04-30 16:35   ` Jason Gunthorpe
2024-04-30 16:35     ` Jason Gunthorpe
2024-04-30 18:08     ` Nicolin Chen
2024-04-30 18:08       ` Nicolin Chen
2024-05-01 13:00       ` Jason Gunthorpe
2024-05-01 13:00         ` Jason Gunthorpe
2024-05-01 17:43         ` Nicolin Chen
2024-05-01 17:43           ` Nicolin Chen
2024-05-02 12:41           ` Jason Gunthorpe
2024-05-02 12:41             ` Jason Gunthorpe
2024-05-02 19:26             ` Nicolin Chen
2024-05-02 19:26               ` Nicolin Chen
2024-04-30  4:43 ` [PATCH v6 6/6] iommu/tegra241-cmdqv: Limit CMDs for guest owned VINTF Nicolin Chen
2024-04-30  4:43   ` Nicolin Chen
2024-04-30 17:06   ` Jason Gunthorpe
2024-04-30 17:06     ` Jason Gunthorpe
2024-04-30 18:58     ` Nicolin Chen
2024-04-30 18:58       ` Nicolin Chen
2024-05-01  0:17       ` Jason Gunthorpe
2024-05-01  0:17         ` Jason Gunthorpe
2024-05-01 16:32         ` Nicolin Chen
2024-05-01 16:32           ` Nicolin Chen
2024-05-06  3:52         ` Nicolin Chen
2024-05-06  3:52           ` Nicolin Chen
2024-05-06 13:00           ` Jason Gunthorpe
2024-05-06 13:00             ` Jason Gunthorpe

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=20240430163733.GT941030@nvidia.com \
    --to=jgg@nvidia.com \
    --cc=iommu@lists.linux.dev \
    --cc=jonathanh@nvidia.com \
    --cc=joro@8bytes.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=nicolinc@nvidia.com \
    --cc=robin.murphy@arm.com \
    --cc=thierry.reding@gmail.com \
    --cc=vdumpa@nvidia.com \
    --cc=will@kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.