From: Eric Farman <farman@linux.ibm.com>
To: Jason Gunthorpe <jgg@nvidia.com>,
Alexander Gordeev <agordeev@linux.ibm.com>,
Christian Borntraeger <borntraeger@linux.ibm.com>,
Vasily Gorbik <gor@linux.ibm.com>,
Heiko Carstens <hca@linux.ibm.com>,
iommu@lists.linux.dev, Joerg Roedel <joro@8bytes.org>,
linux-s390@vger.kernel.org, Robin Murphy <robin.murphy@arm.com>,
Sven Schnelle <svens@linux.ibm.com>,
Will Deacon <will@kernel.org>
Cc: Matthew Rosato <mjrosato@linux.ibm.com>,
Anthony Krowiak <akrowiak@linux.ibm.com>,
"Jason J. Herne" <jjherne@linux.ibm.com>
Subject: Re: [PATCH] iommu/s390: Get rid of S390_CCW_IOMMU
Date: Mon, 01 May 2023 11:06:51 -0400 [thread overview]
Message-ID: <07a891513e1083eab901af4dfa630bd60f93479d.camel@linux.ibm.com> (raw)
In-Reply-To: <0-v1-11a50d289ac9+b6-rm_iommu_ccw_jgg@nvidia.com>
On Fri, 2023-04-28 at 16:28 -0300, Jason Gunthorpe wrote:
> This doesn't do anything anymore, the only user of the symbol was
> VFIO_CCW
> which already "depends on VFIO" and VFIO selects IOMMU_API.
The "depends on VFIO" statement came from commit de858a05c9d8 ("vfio-
mdev: add back CONFIG_VFIO dependency"). This isn't really a fix to
that one, but it does follow that set of changes.
>
> When this was added VFIO was wrongly doing "depends on IOMMU_API"
(later fixed by commit 179209fa1270 ("vfio: IOMMU_API should be
selected"))
> which
> required some mess like this to ensure IOMMU_API was turned on.
>
> Signed-off-by: Jason Gunthorpe <jgg@nvidia.com>
What of S390_AP_IOMMU? Seems to have been borrowed from the _CCW hunks
being removed here, and is now equally redundant (though I have not
tried).
Regardless, for this:
Reviewed-by: Eric Farman <farman@linux.ibm.com>
> ---
> arch/s390/Kconfig | 1 -
> arch/s390/configs/debug_defconfig | 1 -
> arch/s390/configs/defconfig | 1 -
> drivers/iommu/Kconfig | 8 --------
> 4 files changed, 11 deletions(-)
>
> diff --git a/arch/s390/Kconfig b/arch/s390/Kconfig
> index 9809c74e124060..9334500078f978 100644
> --- a/arch/s390/Kconfig
> +++ b/arch/s390/Kconfig
> @@ -714,7 +714,6 @@ config EADM_SCH
> config VFIO_CCW
> def_tristate n
> prompt "Support for VFIO-CCW subchannels"
> - depends on S390_CCW_IOMMU
> depends on VFIO
> select VFIO_MDEV
> help
> diff --git a/arch/s390/configs/debug_defconfig
> b/arch/s390/configs/debug_defconfig
> index 4ccf66d29fc24b..77b886e1b867d4 100644
> --- a/arch/s390/configs/debug_defconfig
> +++ b/arch/s390/configs/debug_defconfig
> @@ -591,7 +591,6 @@ CONFIG_VIRTIO_BALLOON=m
> CONFIG_VIRTIO_INPUT=y
> CONFIG_VHOST_NET=m
> CONFIG_VHOST_VSOCK=m
> -CONFIG_S390_CCW_IOMMU=y
> CONFIG_S390_AP_IOMMU=y
> CONFIG_EXT4_FS=y
> CONFIG_EXT4_FS_POSIX_ACL=y
> diff --git a/arch/s390/configs/defconfig
> b/arch/s390/configs/defconfig
> index 693297a2e89733..36ab9b1956245c 100644
> --- a/arch/s390/configs/defconfig
> +++ b/arch/s390/configs/defconfig
> @@ -580,7 +580,6 @@ CONFIG_VIRTIO_BALLOON=m
> CONFIG_VIRTIO_INPUT=y
> CONFIG_VHOST_NET=m
> CONFIG_VHOST_VSOCK=m
> -CONFIG_S390_CCW_IOMMU=y
> CONFIG_S390_AP_IOMMU=y
> CONFIG_EXT4_FS=y
> CONFIG_EXT4_FS_POSIX_ACL=y
> diff --git a/drivers/iommu/Kconfig b/drivers/iommu/Kconfig
> index db98c3f86e8c8b..b1f9d82b4ec9ae 100644
> --- a/drivers/iommu/Kconfig
> +++ b/drivers/iommu/Kconfig
> @@ -417,14 +417,6 @@ config S390_IOMMU
> help
> Support for the IOMMU API for s390 PCI devices.
>
> -config S390_CCW_IOMMU
> - bool "S390 CCW IOMMU Support"
> - depends on S390 && CCW || COMPILE_TEST
> - select IOMMU_API
> - help
> - Enables bits of IOMMU API required by VFIO. The iommu_ops
> - is not implemented as it is not necessary for VFIO.
> -
> config S390_AP_IOMMU
> bool "S390 AP IOMMU Support"
> depends on S390 && ZCRYPT || COMPILE_TEST
>
> base-commit: 57d60ea1868f36586c85f6f6692cf4bc49affecd
next prev parent reply other threads:[~2023-05-01 15:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-28 19:28 [PATCH] iommu/s390: Get rid of S390_CCW_IOMMU Jason Gunthorpe
2023-05-01 15:06 ` Eric Farman [this message]
2023-05-01 15:25 ` 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=07a891513e1083eab901af4dfa630bd60f93479d.camel@linux.ibm.com \
--to=farman@linux.ibm.com \
--cc=agordeev@linux.ibm.com \
--cc=akrowiak@linux.ibm.com \
--cc=borntraeger@linux.ibm.com \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=iommu@lists.linux.dev \
--cc=jgg@nvidia.com \
--cc=jjherne@linux.ibm.com \
--cc=joro@8bytes.org \
--cc=linux-s390@vger.kernel.org \
--cc=mjrosato@linux.ibm.com \
--cc=robin.murphy@arm.com \
--cc=svens@linux.ibm.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