From: Robin Murphy <robin.murphy@arm.com>
To: Anvesh Jain P <quic_ajainp@quicinc.com>,
Joerg Roedel <joro@8bytes.org>, Will Deacon <will@kernel.org>
Cc: iommu@lists.linux.dev, linux-kernel@vger.kernel.org,
Venkata Rao Kakani <quic_vkakani@quicinc.com>,
Vagdhan Kumar <quic_vagdhank@quicinc.com>
Subject: Re: [PATCH] iommu: export iommu_set_default_translated function
Date: Thu, 15 Jun 2023 10:39:06 +0100 [thread overview]
Message-ID: <685ec543-56d0-7a9c-4a15-3072746c2f91@arm.com> (raw)
In-Reply-To: <20230615093308.24989-1-quic_ajainp@quicinc.com>
On 2023-06-15 10:33, Anvesh Jain P wrote:
> export iommu_set_default_translated function to be used by other modules.
Which modules? The only reason these functions are public at all is to
support the legacy x86 command-line options. No *new* code outside the
core API should have any reason to be messing with core API policy. If
an IOMMU driver needs to special-case particular devices we have
.def_domain_type for that.
Thanks,
Robin.
> Signed-off-by: Anvesh Jain P <quic_ajainp@quicinc.com>
> Signed-off-by: Venkata Rao Kakani <quic_vkakani@quicinc.com>
> Signed-off-by: Vagdhan Kumar <quic_vagdhank@quicinc.com>
> ---
> drivers/iommu/iommu.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/iommu/iommu.c b/drivers/iommu/iommu.c
> index f1dcfa3f1a1b..1b4a5db58d66 100644
> --- a/drivers/iommu/iommu.c
> +++ b/drivers/iommu/iommu.c
> @@ -2730,6 +2730,7 @@ void iommu_set_default_translated(bool cmd_line)
> iommu_cmd_line |= IOMMU_CMD_LINE_DMA_API;
> iommu_def_domain_type = IOMMU_DOMAIN_DMA;
> }
> +EXPORT_SYMBOL_GPL(iommu_set_default_translated);
>
> bool iommu_default_passthrough(void)
> {
>
> base-commit: b6dad5178ceaf23f369c3711062ce1f2afc33644
next prev parent reply other threads:[~2023-06-15 9:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-15 9:33 Anvesh Jain P
2023-06-15 9:39 ` Robin Murphy [this message]
2023-06-16 2:14 ` Baolu Lu
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=685ec543-56d0-7a9c-4a15-3072746c2f91@arm.com \
--to=robin.murphy@arm.com \
--cc=iommu@lists.linux.dev \
--cc=joro@8bytes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_ajainp@quicinc.com \
--cc=quic_vagdhank@quicinc.com \
--cc=quic_vkakani@quicinc.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®