From: Conor Dooley <conor@kernel.org>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: kernel test robot <lkp@intel.com>,
Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>,
Paul Gazzillo <paul@pgazz.com>,
Necip Fazil Yildiran <fazilyildiran@gmail.com>,
oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
Geert Uytterhoeven <geert+renesas@glider.be>,
Conor Dooley <conor.dooley@microchip.com>,
Guo Ren <guoren@kernel.org>
Subject: Re: kismet: WARNING: unmet direct dependencies detected for IOMMU_IO_PGTABLE_LPAE when selected by IPMMU_VMSA
Date: Tue, 27 Dec 2022 18:59:12 +0000 [thread overview]
Message-ID: <Y6tAgP7UoP3aYBjq@spud> (raw)
In-Reply-To: <e1680223-2819-172e-20ea-daea3282e9eb@infradead.org>
[-- Attachment #1: Type: text/plain, Size: 3095 bytes --]
Hey Randy,
On Thu, Dec 22, 2022 at 05:00:06PM -0800, Randy Dunlap wrote:
> On 12/21/22 20:49, kernel test robot wrote:
> > tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
> > head: 9d2f6060fe4c3b49d0cdc1dce1c99296f33379c8
> > commit: 8292493c22c8e28b6e67a01e0f5c6db1cf231eb1 riscv: Kconfig.socs: Add ARCH_RENESAS kconfig option
> > date: 6 weeks ago
> > config: riscv-kismet-CONFIG_IOMMU_IO_PGTABLE_LPAE-CONFIG_IPMMU_VMSA-0-0
> > reproduce:
> > # https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=8292493c22c8e28b6e67a01e0f5c6db1cf231eb1
> > git remote add linus https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
> > git fetch --no-tags linus master
> > git checkout 8292493c22c8e28b6e67a01e0f5c6db1cf231eb1
> > # 1. reproduce by kismet
> > # install kmax per https://github.com/paulgazz/kmax/blob/master/README.md
> > kismet --linux-ksrc=linux --selectees CONFIG_IOMMU_IO_PGTABLE_LPAE --selectors CONFIG_IPMMU_VMSA -a=riscv
> > # 2. reproduce by make
> > # save the config file to linux source tree
> > cd linux
> > make ARCH=riscv olddefconfig
> >
> > If you fix the issue, kindly add following tag where applicable
> > | Reported-by: kernel test robot <lkp@intel.com>
> >
> > kismet warnings: (new ones prefixed by >>)
> >>> kismet: WARNING: unmet direct dependencies detected for IOMMU_IO_PGTABLE_LPAE when selected by IPMMU_VMSA
> > .config:4814:warning: symbol value 'ONFIG_ARCH_MMAP_RND_BITS_MI' invalid for ARCH_MMAP_RND_BITS
> >
> > WARNING: unmet direct dependencies detected for IOMMU_IO_PGTABLE_LPAE
> > Depends on [n]: IOMMU_SUPPORT [=y] && (ARM || ARM64 || COMPILE_TEST [=y] && !GENERIC_ATOMIC64 [=y])
> > Selected by [y]:
> > - IPMMU_VMSA [=y] && IOMMU_SUPPORT [=y] && (ARCH_RENESAS [=y] || COMPILE_TEST [=y] && !GENERIC_ATOMIC64 [=y])
> >
>
> Maybe this:
>
> ---
> drivers/iommu/Kconfig | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff -- a/drivers/iommu/Kconfig b/drivers/iommu/Kconfig
> --- a/drivers/iommu/Kconfig
> +++ b/drivers/iommu/Kconfig
> @@ -32,7 +32,8 @@ config IOMMU_IO_PGTABLE
> config IOMMU_IO_PGTABLE_LPAE
> bool "ARMv7/v8 Long Descriptor Format"
> select IOMMU_IO_PGTABLE
> - depends on ARM || ARM64 || (COMPILE_TEST && !GENERIC_ATOMIC64)
> + depends on ARM || ARM64 || ARCH_RENESAS || \
> + (COMPILE_TEST && !GENERIC_ATOMIC64)
> help
> Enable support for the ARM long descriptor pagetable format.
> This allocator supports 4K/2M/1G, 16K/32M and 64K/512M page
>
>
> or is way off?
Apologies for the radio silence here..
Palmer initially sent a workaround and there was some discussion there:
https://lore.kernel.org/all/20221214180409.7354-1-palmer@rivosinc.com/
Guo sent a patch too:
https://lore.kernel.org/linux-riscv/20221215073212.1966823-1-guoren@kernel.org/
I suppose Christmas is doing Christmas things :)
Thanks,
Conor.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2022-12-27 18:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-22 4:49 kismet: WARNING: unmet direct dependencies detected for IOMMU_IO_PGTABLE_LPAE when selected by IPMMU_VMSA kernel test robot
2022-12-23 1:00 ` Randy Dunlap
2022-12-27 18:59 ` Conor Dooley [this message]
2022-12-27 23:04 ` Randy Dunlap
2023-02-25 0:12 ` Randy Dunlap
2023-02-25 0:22 ` Conor Dooley
2023-02-25 0:28 ` Randy Dunlap
2023-02-25 13:43 ` Conor Dooley
2023-03-08 16:08 ` Conor Dooley
2023-03-08 16:58 ` Randy Dunlap
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=Y6tAgP7UoP3aYBjq@spud \
--to=conor@kernel.org \
--cc=conor.dooley@microchip.com \
--cc=fazilyildiran@gmail.com \
--cc=geert+renesas@glider.be \
--cc=guoren@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=paul@pgazz.com \
--cc=prabhakar.mahadev-lad.rj@bp.renesas.com \
--cc=rdunlap@infradead.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 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.