From: John Garry <john.garry@huawei.com>
To: Robin Murphy <robin.murphy@arm.com>, <joro@8bytes.org>
Cc: <will@kernel.org>, <iommu@lists.linux.dev>,
<linux-kernel@vger.kernel.org>,
Thierry Reding <thierry.reding@gmail.com>
Subject: Re: [PATCH] iommu/iova: Fix module config properly
Date: Tue, 13 Sep 2022 14:01:36 +0100 [thread overview]
Message-ID: <4740744e-2e12-520d-8598-188b8d2ebd6b@huawei.com> (raw)
In-Reply-To: <548c2f683ca379aface59639a8f0cccc3a1ac050.1663069227.git.robin.murphy@arm.com>
On 13/09/2022 12:47, Robin Murphy wrote:
> IOMMU_IOVA is intended to be an optional library for users to select as
> and when they desire. Since it can be a module now, this means that
> built-in code which has chosen not to select it should not fail to link
> if it happens to have selected as a module by someone else. Replace
> IS_ENABLED() with IS_REACHABLE() to do the right thing.
Hi Robin,
Recently you mentioned "I wonder if we couldn't replace the IS_ENABLED()
with IS_REACHABLE() and restore some of the previously-conditional
selects", and pointed me to 84db889e6d82 as an example of when a
conditional select was made unconditional.
So will you also restore some previously-conditional selects next?
To me, it seems that any user of IOVA API selects IOMMU_IOVA always.
thanks,
John
>
> CC: Thierry Reding <thierry.reding@gmail.com>
> Reported-by: John Garry <john.garry@huawei.com>
> Fixes: 15bbdec3931e ("iommu: Make the iova library a module")
> Signed-off-by: Robin Murphy <robin.murphy@arm.com>
> ---
>
> Phrased as a fix for the sake of complete honesty, but it seems
> everyone's been making do for years already so by now it's really
> just more of an enhancement.
>
> include/linux/iova.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/include/linux/iova.h b/include/linux/iova.h
> index 8f97a43be834..fe18c3e6a725 100644
> --- a/include/linux/iova.h
> +++ b/include/linux/iova.h
> @@ -75,7 +75,7 @@ static inline unsigned long iova_pfn(struct iova_domain *iovad, dma_addr_t iova)
> return iova >> iova_shift(iovad);
> }
>
> -#if IS_ENABLED(CONFIG_IOMMU_IOVA)
> +#if IS_REACHABLE(CONFIG_IOMMU_IOVA)
> int iova_cache_get(void);
> void iova_cache_put(void);
>
next prev parent reply other threads:[~2022-09-13 13:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-13 11:47 Robin Murphy
2022-09-13 13:01 ` John Garry [this message]
2022-09-13 14:15 ` Robin Murphy
2022-09-14 9:47 ` Thierry Reding
2022-09-15 11:45 ` John Garry
2022-09-16 9:31 ` Thierry Reding
2022-09-14 9:48 ` Thierry Reding
2022-09-26 11:31 ` 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=4740744e-2e12-520d-8598-188b8d2ebd6b@huawei.com \
--to=john.garry@huawei.com \
--cc=iommu@lists.linux.dev \
--cc=joro@8bytes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robin.murphy@arm.com \
--cc=thierry.reding@gmail.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
all inboxes | Powered by JetHome®