All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nicolin Chen <nicolinc@nvidia.com>
To: Aahil Awatramani <aahila@google.com>, <mshavit@google.com>
Cc: <robin.murphy@arm.com>, <will@kernel.org>, <jgg@nvidia.com>,
	<joro@8bytes.org>, <shameerali.kolothum.thodi@huawei.com>,
	<yangyicong@hisilicon.com>, <jean-philippe@linaro.org>,
	<linux-arm-kernel@lists.infradead.org>, <iommu@lists.linux.dev>,
	<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v1] iommu/arm-smmu-v3: Allow default substream bypass with a pasid support
Date: Wed, 13 Sep 2023 18:02:50 -0700	[thread overview]
Message-ID: <ZQJbunPj6Q8XRcpV@Asurada-Nvidia> (raw)
In-Reply-To: <CAGfWUPziSWNMc_px4E-i+_V_Jxdb_WSwOLXHZ+PANz2Tv5pFPA@mail.gmail.com>

On Tue, Sep 12, 2023 at 03:13:25PM -0700, Aahil Awatramani wrote:
> 
> We have a use-case for this patch to help in avoiding the map/unmap
> overhead in some cases but still maintaining support for PASIDs.

This has another version [1] rebased on top of Michael's refactor
series [2]. We'd need Michael to respin the refactor sereis and I
will resend mine.

[1] https://lore.kernel.org/linux-iommu/cover.1692959239.git.nicolinc@nvidia.com/
[2] https://lore.kernel.org/linux-iommu/ZPEpl9D%2FCqQWYhzk@Asurada-Nvidia/

Thanks
Nicolin

WARNING: multiple messages have this Message-ID (diff)
From: Nicolin Chen <nicolinc@nvidia.com>
To: Aahil Awatramani <aahila@google.com>, <mshavit@google.com>
Cc: <robin.murphy@arm.com>, <will@kernel.org>, <jgg@nvidia.com>,
	<joro@8bytes.org>, <shameerali.kolothum.thodi@huawei.com>,
	<yangyicong@hisilicon.com>, <jean-philippe@linaro.org>,
	<linux-arm-kernel@lists.infradead.org>, <iommu@lists.linux.dev>,
	<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v1] iommu/arm-smmu-v3: Allow default substream bypass with a pasid support
Date: Wed, 13 Sep 2023 18:02:50 -0700	[thread overview]
Message-ID: <ZQJbunPj6Q8XRcpV@Asurada-Nvidia> (raw)
In-Reply-To: <CAGfWUPziSWNMc_px4E-i+_V_Jxdb_WSwOLXHZ+PANz2Tv5pFPA@mail.gmail.com>

On Tue, Sep 12, 2023 at 03:13:25PM -0700, Aahil Awatramani wrote:
> 
> We have a use-case for this patch to help in avoiding the map/unmap
> overhead in some cases but still maintaining support for PASIDs.

This has another version [1] rebased on top of Michael's refactor
series [2]. We'd need Michael to respin the refactor sereis and I
will resend mine.

[1] https://lore.kernel.org/linux-iommu/cover.1692959239.git.nicolinc@nvidia.com/
[2] https://lore.kernel.org/linux-iommu/ZPEpl9D%2FCqQWYhzk@Asurada-Nvidia/

Thanks
Nicolin

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

  reply	other threads:[~2023-09-14  1:03 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-27  3:33 [PATCH v1] iommu/arm-smmu-v3: Allow default substream bypass with a pasid support Nicolin Chen
2023-06-27  3:33 ` Nicolin Chen
2023-06-27  9:00 ` Robin Murphy
2023-06-27  9:00   ` Robin Murphy
2023-06-27 17:06   ` Nicolin Chen
2023-06-27 17:06     ` Nicolin Chen
2023-06-27 23:29     ` Robin Murphy
2023-06-27 23:29       ` Robin Murphy
2023-06-28  0:13       ` Nicolin Chen
2023-06-28  0:13         ` Nicolin Chen
2023-06-28 15:39         ` Robin Murphy
2023-06-28 15:39           ` Robin Murphy
2023-06-28 15:43           ` Jason Gunthorpe
2023-06-28 15:43             ` Jason Gunthorpe
2023-06-28 15:59           ` Nicolin Chen
2023-06-28 15:59             ` Nicolin Chen
2023-09-12 22:13 ` Aahil Awatramani
2023-09-12 22:13   ` Aahil Awatramani
2023-09-14  1:02   ` Nicolin Chen [this message]
2023-09-14  1:02     ` Nicolin Chen
2023-09-14  9:01     ` Michael Shavit
2023-09-14  9:01       ` Michael Shavit
2023-09-14 10:26       ` Nicolin Chen
2023-09-14 10:26         ` Nicolin Chen

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=ZQJbunPj6Q8XRcpV@Asurada-Nvidia \
    --to=nicolinc@nvidia.com \
    --cc=aahila@google.com \
    --cc=iommu@lists.linux.dev \
    --cc=jean-philippe@linaro.org \
    --cc=jgg@nvidia.com \
    --cc=joro@8bytes.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mshavit@google.com \
    --cc=robin.murphy@arm.com \
    --cc=shameerali.kolothum.thodi@huawei.com \
    --cc=will@kernel.org \
    --cc=yangyicong@hisilicon.com \
    /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.