Linux IOMMU Development
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgg@nvidia.com>
To: Nicolin Chen <nicolinc@nvidia.com>
Cc: robin.murphy@arm.com, joro@8bytes.org, will@kernel.org,
	kevin.tian@intel.com, baolu.lu@linux.intel.com,
	iommu@lists.linux.dev, linux-kernel@vger.kernel.org,
	nathan@kernel.org, arnd@arndb.de
Subject: Re: [PATCH v5 0/3] iommu: Clean up cookie and sw_msi in struct iommu_domain
Date: Tue, 25 Mar 2025 09:40:56 -0300	[thread overview]
Message-ID: <Z+KkWGwwUHMKxWxm@nvidia.com> (raw)
In-Reply-To: <Z+Itnw4ys6dmDsc+@nvidia.com>

On Mon, Mar 24, 2025 at 09:14:23PM -0700, Nicolin Chen wrote:
> On Mon, Mar 24, 2025 at 09:05:14PM -0700, Nicolin Chen wrote:
> > This is a clean-up series for the previous sw_msi Part-1 core series. It's
> > on github:
> > https://github.com/nicolinc/iommufd/commits/iommufd_msi_cleanup-v5
> > 
> > Changelog
> > v5
> >  * Add IMPORT line for IOMMUFD_INTERNAL and change IOMMUFD_DRIVER_CORE
> >    to a "bool" module, fixing build module errors reported by Arnd:
> >    https://lore.kernel.org/all/20250324210329.2809869-1-arnd@kernel.org/
> >  * In iommu_dma_prepare_msi(), let all IDENTITY DOMAINs pass through,
> >    fixing the regression with IDENTITY domains reported by Nathan:
> >    https://lore.kernel.org/linux-iommu/20250324162558.GA198799@ax162/
> 
> > base-commit: da0c56520e880441d0503d0cf0d6853dcfb5f1a4
> 
> Hi Jason,
> 
> Assuming that you want to replace the commits in your for-next
> tree with these patches, I rebased them on this commit:
> da0c56520e88 iommu/arm-smmu-v3: Set MEV bit in nested STE for DoS mitigations
> 
> Again, sorry for the trouble.

Can you post a v6 please? That is a bit easier

Thanks,
Jason

  reply	other threads:[~2025-03-25 12:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-25  4:05 [PATCH v5 0/3] iommu: Clean up cookie and sw_msi in struct iommu_domain Nicolin Chen
2025-03-25  4:05 ` [PATCH v5 1/3] iommu: Sort out domain user data Nicolin Chen
2025-03-25  4:05 ` [PATCH v5 2/3] iommufd: Move iommufd_sw_msi and related functions to driver.c Nicolin Chen
2025-03-25  4:05 ` [PATCH v5 3/3] iommu: Drop sw_msi from iommu_domain Nicolin Chen
2025-03-25  4:14 ` [PATCH v5 0/3] iommu: Clean up cookie and sw_msi in struct iommu_domain Nicolin Chen
2025-03-25 12:40   ` Jason Gunthorpe [this message]
2025-03-25 13:21 ` 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=Z+KkWGwwUHMKxWxm@nvidia.com \
    --to=jgg@nvidia.com \
    --cc=arnd@arndb.de \
    --cc=baolu.lu@linux.intel.com \
    --cc=iommu@lists.linux.dev \
    --cc=joro@8bytes.org \
    --cc=kevin.tian@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nathan@kernel.org \
    --cc=nicolinc@nvidia.com \
    --cc=robin.murphy@arm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox