All of lore.kernel.org
 help / color / mirror / Atom feed
From: Will Deacon <will@kernel.org>
To: joro@8bytes.org
Cc: iommu@lists.linux.dev, linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, robin.murphy@arm.com,
	kernel-team@android.com
Subject: [GIT PULL] iommu/arm-smmu: Fixes for 6.2
Date: Fri, 13 Jan 2023 11:03:18 +0000	[thread overview]
Message-ID: <20230113110318.GA12771@willie-the-truck> (raw)

Hi Joerg,

Please can you pull these Arm SMMU fixes for 6.2? The summary is in the
tag, but the main thing is fixing a VFIO regression due to the way in
which IOMMU_CAP_CACHE_COHERENCY is reported for SMMUv2 devices.

Cheers,

Will

--->8

The following changes since commit 1b929c02afd37871d5afb9d498426f83432e71c2:

  Linux 6.2-rc1 (2022-12-25 13:41:39 -0800)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/will/linux.git tags/arm-smmu-fixes

for you to fetch changes up to f1ba05a70f7df4e2e4d2d7fed2d4e63a1e700660:

  iommu/arm-smmu-v3: Don't unregister on shutdown (2023-01-11 12:20:00 +0000)

----------------------------------------------------------------
Arm SMMU fixes for 6.2

- Fix VFIO regression on NXP SoCs by reporting IOMMU_CAP_CACHE_COHERENCY

- Fix SMMU shutdown paths to avoid device unregistration race

----------------------------------------------------------------
Robin Murphy (1):
      iommu/arm-smmu: Report IOMMU_CAP_CACHE_COHERENCY even betterer

Vladimir Oltean (2):
      iommu/arm-smmu: Don't unregister on shutdown
      iommu/arm-smmu-v3: Don't unregister on shutdown

 drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3.c |  4 +++-
 drivers/iommu/arm/arm-smmu/arm-smmu.c       | 32 ++++++++++++++++++++---------
 2 files changed, 25 insertions(+), 11 deletions(-)

WARNING: multiple messages have this Message-ID (diff)
From: Will Deacon <will@kernel.org>
To: joro@8bytes.org
Cc: iommu@lists.linux.dev, linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, robin.murphy@arm.com,
	kernel-team@android.com
Subject: [GIT PULL] iommu/arm-smmu: Fixes for 6.2
Date: Fri, 13 Jan 2023 11:03:18 +0000	[thread overview]
Message-ID: <20230113110318.GA12771@willie-the-truck> (raw)

Hi Joerg,

Please can you pull these Arm SMMU fixes for 6.2? The summary is in the
tag, but the main thing is fixing a VFIO regression due to the way in
which IOMMU_CAP_CACHE_COHERENCY is reported for SMMUv2 devices.

Cheers,

Will

--->8

The following changes since commit 1b929c02afd37871d5afb9d498426f83432e71c2:

  Linux 6.2-rc1 (2022-12-25 13:41:39 -0800)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/will/linux.git tags/arm-smmu-fixes

for you to fetch changes up to f1ba05a70f7df4e2e4d2d7fed2d4e63a1e700660:

  iommu/arm-smmu-v3: Don't unregister on shutdown (2023-01-11 12:20:00 +0000)

----------------------------------------------------------------
Arm SMMU fixes for 6.2

- Fix VFIO regression on NXP SoCs by reporting IOMMU_CAP_CACHE_COHERENCY

- Fix SMMU shutdown paths to avoid device unregistration race

----------------------------------------------------------------
Robin Murphy (1):
      iommu/arm-smmu: Report IOMMU_CAP_CACHE_COHERENCY even betterer

Vladimir Oltean (2):
      iommu/arm-smmu: Don't unregister on shutdown
      iommu/arm-smmu-v3: Don't unregister on shutdown

 drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3.c |  4 +++-
 drivers/iommu/arm/arm-smmu/arm-smmu.c       | 32 ++++++++++++++++++++---------
 2 files changed, 25 insertions(+), 11 deletions(-)

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

             reply	other threads:[~2023-01-13 11:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-13 11:03 Will Deacon [this message]
2023-01-13 11:03 ` [GIT PULL] iommu/arm-smmu: Fixes for 6.2 Will Deacon
2023-01-13 12:19 ` Joerg Roedel
2023-01-13 12:19   ` Joerg Roedel

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=20230113110318.GA12771@willie-the-truck \
    --to=will@kernel.org \
    --cc=iommu@lists.linux.dev \
    --cc=joro@8bytes.org \
    --cc=kernel-team@android.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robin.murphy@arm.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.