From: Conor Dooley <conor.dooley@microchip.com>
To: Alexandre Ghiti <alex@ghiti.fr>
Cc: Randy Dunlap <rdunlap@infradead.org>,
Robin Murphy <robin.murphy@arm.com>,
<linux-kernel@vger.kernel.org>, Joerg Roedel <joro@8bytes.org>,
Will Deacon <will@kernel.org>, <iommu@lists.linux.dev>,
Conor Dooley <conor@kernel.org>,
<linux-riscv@lists.infradead.org>
Subject: Re: [PATCH] iommu: PGTABLE_LPAE is also for RISCV
Date: Tue, 16 May 2023 08:12:10 +0100 [thread overview]
Message-ID: <20230516-gristle-spill-e27c58770a47@wendy> (raw)
In-Reply-To: <280c0994-f7cd-bb0e-8c68-62f72a4a38ca@ghiti.fr>
[-- Attachment #1: Type: text/plain, Size: 2000 bytes --]
On Tue, May 16, 2023 at 09:02:50AM +0200, Alexandre Ghiti wrote:
> Hi Randy,
>
>
> On 3/30/23 18:49, Randy Dunlap wrote:
> >
> > On 3/30/23 09:34, Robin Murphy wrote:
> > > On 2023-03-30 07:01, Randy Dunlap wrote:
> > > > On riscv64, linux-next-20233030 (and for several days earlier),
> > > > there is a kconfig warning:
> > > >
> > > > WARNING: unmet direct dependencies detected for IOMMU_IO_PGTABLE_LPAE
> > > > Depends on [n]: IOMMU_SUPPORT [=y] && (ARM || ARM64 || COMPILE_TEST [=n]) && !GENERIC_ATOMIC64 [=n]
> > > > Selected by [y]:
> > > > - IPMMU_VMSA [=y] && IOMMU_SUPPORT [=y] && (ARCH_RENESAS [=y] || COMPILE_TEST [=n]) && !GENERIC_ATOMIC64 [=n]
> > > >
> > > > and build errors:
> > > >
> > > > riscv64-linux-ld: drivers/iommu/io-pgtable-arm.o: in function `.L140':
> > > > io-pgtable-arm.c:(.init.text+0x1e8): undefined reference to `alloc_io_pgtable_ops'
> > > > riscv64-linux-ld: drivers/iommu/io-pgtable-arm.o: in function `.L168':
> > > > io-pgtable-arm.c:(.init.text+0xab0): undefined reference to `free_io_pgtable_ops'
> > > > riscv64-linux-ld: drivers/iommu/ipmmu-vmsa.o: in function `.L140':
> > > > ipmmu-vmsa.c:(.text+0xbc4): undefined reference to `free_io_pgtable_ops'
> > > > riscv64-linux-ld: drivers/iommu/ipmmu-vmsa.o: in function `.L0 ':
> > > > ipmmu-vmsa.c:(.text+0x145e): undefined reference to `alloc_io_pgtable_ops'
> > > >
> > > > Add RISCV as an allowed ARCH dependency to fix these problems.
> > > >
> > > > Fixes: d286a58bc8f4 ("iommu: Tidy up io-pgtable dependencies")
> > > BTW that doesn't look like the right fix target - this presumably dates back as far as when ARCH_RENESAS was added to RISCV, such that it was possible to start selecting IPMMU_VMSA without COMPILE_TEST?
> > OK, I can go with that. Thanks for your help.
> >
>
> Any updates on this fix?
Superseeded by
https://lore.kernel.org/linux-iommu/20230330165817.21920-1-rdunlap@infradead.org/
I guess that never went anywhere?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
prev parent reply other threads:[~2023-05-16 7:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-30 6:01 [PATCH] iommu: PGTABLE_LPAE is also for RISCV Randy Dunlap
2023-03-30 6:25 ` Conor Dooley
2023-03-30 7:31 ` Geert Uytterhoeven
2023-03-30 10:43 ` Robin Murphy
2023-03-30 15:48 ` Randy Dunlap
2023-03-30 16:11 ` Geert Uytterhoeven
2023-03-30 16:33 ` Randy Dunlap
2023-03-30 16:34 ` Robin Murphy
2023-03-30 16:49 ` Randy Dunlap
2023-05-16 7:02 ` Alexandre Ghiti
2023-05-16 7:12 ` Conor Dooley [this message]
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=20230516-gristle-spill-e27c58770a47@wendy \
--to=conor.dooley@microchip.com \
--cc=alex@ghiti.fr \
--cc=conor@kernel.org \
--cc=iommu@lists.linux.dev \
--cc=joro@8bytes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=rdunlap@infradead.org \
--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