All of lore.kernel.org
 help / color / mirror / Atom feed
From: Palmer Dabbelt <palmer@rivosinc.com>
To: linux-riscv@lists.infradead.org, arnd@arndb.de, iommu@lists.linux.dev
Cc: Palmer Dabbelt <palmer@rivosinc.com>
Subject: [PATCH] RISC-V: Disable IPMMU_VMSA on rv32
Date: Wed, 14 Dec 2022 10:04:09 -0800	[thread overview]
Message-ID: <20221214180409.7354-1-palmer@rivosinc.com> (raw)

Without this I get a Kconfig warning and then subsequent build failure
when building allmodconfig on rv32.

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])

linux/drivers/iommu/io-pgtable-arm.c: Assembler messages:
linux/drivers/iommu/io-pgtable-arm.c:330: Error: unrecognized opcode `lr.d s4,0(s1)'
linux/drivers/iommu/io-pgtable-arm.c:332: Error: unrecognized opcode `sc.d.rl a5,s6,0(s1)'
make[5]: *** [linux/scripts/Makefile.build:250: drivers/iommu/io-pgtable-arm.o] Error 1
make[4]: *** [linux/scripts/Makefile.build:502: drivers/iommu] Error 2
make[3]: *** [linux/scripts/Makefile.build:502: drivers] Error 2

Signed-off-by: Palmer Dabbelt <palmer@rivosinc.com>

---

This one seems pretty ugly, but I like to at least have a workaround for
the allmodconfig failures before sending up a PR.
---
 arch/riscv/configs/32-bit.config | 1 +
 1 file changed, 1 insertion(+)

diff --git a/arch/riscv/configs/32-bit.config b/arch/riscv/configs/32-bit.config
index f6af0f708df4..7a2fa9b37b1c 100644
--- a/arch/riscv/configs/32-bit.config
+++ b/arch/riscv/configs/32-bit.config
@@ -2,3 +2,4 @@ CONFIG_ARCH_RV32I=y
 CONFIG_32BIT=y
 # CONFIG_PORTABLE is not set
 CONFIG_NONPORTABLE=y
+CONFIG_IPMMU_VMSA=n
-- 
2.38.1


_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

WARNING: multiple messages have this Message-ID (diff)
From: Palmer Dabbelt <palmer@rivosinc.com>
To: linux-riscv@lists.infradead.org, arnd@arndb.de, iommu@lists.linux.dev
Cc: Palmer Dabbelt <palmer@rivosinc.com>
Subject: [PATCH] RISC-V: Disable IPMMU_VMSA on rv32
Date: Wed, 14 Dec 2022 10:04:09 -0800	[thread overview]
Message-ID: <20221214180409.7354-1-palmer@rivosinc.com> (raw)

Without this I get a Kconfig warning and then subsequent build failure
when building allmodconfig on rv32.

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])

linux/drivers/iommu/io-pgtable-arm.c: Assembler messages:
linux/drivers/iommu/io-pgtable-arm.c:330: Error: unrecognized opcode `lr.d s4,0(s1)'
linux/drivers/iommu/io-pgtable-arm.c:332: Error: unrecognized opcode `sc.d.rl a5,s6,0(s1)'
make[5]: *** [linux/scripts/Makefile.build:250: drivers/iommu/io-pgtable-arm.o] Error 1
make[4]: *** [linux/scripts/Makefile.build:502: drivers/iommu] Error 2
make[3]: *** [linux/scripts/Makefile.build:502: drivers] Error 2

Signed-off-by: Palmer Dabbelt <palmer@rivosinc.com>

---

This one seems pretty ugly, but I like to at least have a workaround for
the allmodconfig failures before sending up a PR.
---
 arch/riscv/configs/32-bit.config | 1 +
 1 file changed, 1 insertion(+)

diff --git a/arch/riscv/configs/32-bit.config b/arch/riscv/configs/32-bit.config
index f6af0f708df4..7a2fa9b37b1c 100644
--- a/arch/riscv/configs/32-bit.config
+++ b/arch/riscv/configs/32-bit.config
@@ -2,3 +2,4 @@ CONFIG_ARCH_RV32I=y
 CONFIG_32BIT=y
 # CONFIG_PORTABLE is not set
 CONFIG_NONPORTABLE=y
+CONFIG_IPMMU_VMSA=n
-- 
2.38.1


             reply	other threads:[~2022-12-14 18:32 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-14 18:04 Palmer Dabbelt [this message]
2022-12-14 18:04 ` [PATCH] RISC-V: Disable IPMMU_VMSA on rv32 Palmer Dabbelt
2022-12-14 19:46 ` Conor Dooley
2022-12-14 19:46   ` Conor Dooley
2022-12-14 21:04   ` Robin Murphy
2022-12-14 21:04     ` Robin Murphy
2022-12-14 21:40     ` Prabhakar Mahadev Lad
2022-12-14 21:40       ` Prabhakar Mahadev Lad
2022-12-14 22:07       ` Robin Murphy
2022-12-14 22:07         ` Robin Murphy
2022-12-15  9:04       ` Geert Uytterhoeven
2022-12-15  9:04         ` Geert Uytterhoeven
2022-12-15  9:14         ` Prabhakar Mahadev Lad
2022-12-15  9:14           ` Prabhakar Mahadev Lad

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=20221214180409.7354-1-palmer@rivosinc.com \
    --to=palmer@rivosinc.com \
    --cc=arnd@arndb.de \
    --cc=iommu@lists.linux.dev \
    --cc=linux-riscv@lists.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.