All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nicolin Chen <nicolinc@nvidia.com>
To: Pranjal Shrivastava <praan@google.com>
Cc: Joerg Roedel <joro@8bytes.org>, Will Deacon <will@kernel.org>,
	"Robin Murphy" <robin.murphy@arm.com>,
	Mostafa Saleh <smostafa@google.com>, <iommu@lists.linux.dev>
Subject: Re: [PATCH v3 2/2] iommu/arm-smmu-v3: Adopt arm_smmu_event in handlers
Date: Mon, 30 Sep 2024 12:32:21 -0700	[thread overview]
Message-ID: <Zvr8xUEHNg1GiA8V@Asurada-Nvidia> (raw)
In-Reply-To: <20240928005143.2378938-3-praan@google.com>

On Sat, Sep 28, 2024 at 12:51:43AM +0000, Pranjal Shrivastava wrote:
>  /* IRQ and event handlers */
> -static int arm_smmu_handle_evt(struct arm_smmu_device *smmu, u64 *evt)
> +static int arm_smmu_handle_evt(struct arm_smmu_device *smmu, struct arm_smmu_event *event)

Looks like we could stuff an smmu pointer in the event:

struct arm_smmu_event {
+	struct arm_smmu_device *smmu;
	struct arm_smmu_master		*master;
	const char			*master_name;

Then both this arm_smmu_handle_evt and arm_smmu_dump_event can be
slightly cleaner.

> 
>         mutex_lock(&smmu->streams_mutex);
> -       master = arm_smmu_find_master(smmu, sid);
> -       if (!master) {
> +       event->master = arm_smmu_find_master(smmu, event->sid);
> +       if (!event->master) {
>                 ret = -EINVAL;
> +               event->master_name = "(unassigned sid)";
>                 goto out_unlock;
>         }

The PATCH-1 already did arm_smmu_find_master() to event->master in
arm_smmu_get_evt_info()?

Maybe we still need a wider mutex to lock arm_smmu_get_evt_info and
arm_smmu_handle_evt.

Thanks
Nicolin

  reply	other threads:[~2024-09-30 19:32 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-28  0:51 [PATCH v3 0/2] Parse out event records Pranjal Shrivastava
2024-09-28  0:51 ` [PATCH v3 1/2] iommu/arm-smmu-v3: Print better events records Pranjal Shrivastava
2024-09-30 19:15   ` Nicolin Chen
2024-10-01 20:52     ` Pranjal Shrivastava
2024-10-01 23:04       ` Nicolin Chen
2024-10-02 13:57     ` Jason Gunthorpe
2024-10-02 16:55       ` Nicolin Chen
2024-10-02 17:10         ` Jason Gunthorpe
2024-10-02 17:22           ` Nicolin Chen
2024-10-03 21:26             ` Pranjal Shrivastava
2024-10-03 22:50               ` Nicolin Chen
2024-10-11  7:53                 ` Pranjal Shrivastava
2024-10-11 10:02                   ` Pranjal Shrivastava
2024-09-28  0:51 ` [PATCH v3 2/2] iommu/arm-smmu-v3: Adopt arm_smmu_event in handlers Pranjal Shrivastava
2024-09-30 19:32   ` Nicolin Chen [this message]
2024-10-01 21:02     ` Pranjal Shrivastava
2024-10-01 22:59       ` Nicolin Chen
2024-10-03 21:34         ` Pranjal Shrivastava
2024-10-03 22:53           ` Nicolin Chen
2024-10-11  7:55             ` Pranjal Shrivastava
2024-10-11 10:21               ` Robin Murphy
2024-10-11 10:45                 ` Pranjal Shrivastava
2024-10-11 11:06                   ` Pranjal Shrivastava
2024-10-11 12:59                     ` Robin Murphy
2024-10-11 20:31                       ` Pranjal Shrivastava
2024-10-15 18:34                       ` Pranjal Shrivastava
2024-10-15 20:03                         ` Robin Murphy
2024-10-17  8:06                           ` Pranjal Shrivastava

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=Zvr8xUEHNg1GiA8V@Asurada-Nvidia \
    --to=nicolinc@nvidia.com \
    --cc=iommu@lists.linux.dev \
    --cc=joro@8bytes.org \
    --cc=praan@google.com \
    --cc=robin.murphy@arm.com \
    --cc=smostafa@google.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.