qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: qemu-devel@nongnu.org
Cc: qemu-block@nongnu.org, "Thomas Huth" <thuth@redhat.com>,
	qemu-s390x@nongnu.org, qemu-riscv@nongnu.org,
	qemu-arm@nongnu.org,
	"Richard Henderson" <richard.henderson@linaro.org>,
	qemu-ppc@nongnu.org, "Philippe Mathieu-Daudé" <philmd@linaro.org>
Subject: [PATCH v3 2/9] target/tricore: Remove pointless CONFIG_SOFTMMU guard
Date: Tue, 13 Jun 2023 15:33:40 +0200	[thread overview]
Message-ID: <20230613133347.82210-3-philmd@linaro.org> (raw)
In-Reply-To: <20230613133347.82210-1-philmd@linaro.org>

We don't build any user emulation target for Tricore,
only the system emulation. No need to check for it as
it is always defined.

Signed-off-by: Philippe Mathieu-Daudé <philmd@linaro.org>
Reviewed-by: Richard Henderson <richard.henderson@linaro.org>
---
 target/tricore/helper.c | 2 --
 1 file changed, 2 deletions(-)

diff --git a/target/tricore/helper.c b/target/tricore/helper.c
index 284a749e50..951024d491 100644
--- a/target/tricore/helper.c
+++ b/target/tricore/helper.c
@@ -31,7 +31,6 @@ enum {
     TLBRET_MATCH = 0
 };
 
-#if defined(CONFIG_SOFTMMU)
 static int get_physical_address(CPUTriCoreState *env, hwaddr *physical,
                                 int *prot, target_ulong address,
                                 MMUAccessType access_type, int mmu_idx)
@@ -57,7 +56,6 @@ hwaddr tricore_cpu_get_phys_page_debug(CPUState *cs, vaddr addr)
     }
     return phys_addr;
 }
-#endif
 
 /* TODO: Add exeption support*/
 static void raise_mmu_exception(CPUTriCoreState *env, target_ulong address,
-- 
2.38.1



  parent reply	other threads:[~2023-06-13 13:28 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-13 13:33 [PATCH v3 0/9] bulk: Replace CONFIG_SOFTMMU by !CONFIG_USER_ONLY/CONFIG_SYSTEM_ONLY Philippe Mathieu-Daudé
2023-06-13 13:33 ` [PATCH v3 1/9] target/i386: Simplify i386_tr_init_disas_context() Philippe Mathieu-Daudé
2023-06-14  5:15   ` Richard Henderson
2023-06-13 13:33 ` Philippe Mathieu-Daudé [this message]
2023-06-13 20:23   ` [PATCH v3 2/9] target/tricore: Remove pointless CONFIG_SOFTMMU guard Bastian Koppelmann
2023-06-13 13:33 ` [PATCH v3 3/9] target/m68k: Check for USER_ONLY definition instead of SOFTMMU one Philippe Mathieu-Daudé
2023-06-13 13:33 ` [PATCH v3 4/9] target/ppc: " Philippe Mathieu-Daudé
2023-06-14  6:30   ` Nicholas Piggin
2023-06-13 13:33 ` [PATCH v3 5/9] hw/core/cpu: " Philippe Mathieu-Daudé
2023-06-13 13:33 ` [PATCH v3 6/9] accel/tcg: " Philippe Mathieu-Daudé
2023-06-13 13:33 ` [PATCH v3 7/9] meson: Alias CONFIG_SOFTMMU -> CONFIG_SYSTEM_ONLY Philippe Mathieu-Daudé
2023-06-14  5:16   ` Richard Henderson
2023-06-13 13:33 ` [PATCH v3 8/9] meson: Replace " Philippe Mathieu-Daudé
2023-06-14  5:17   ` Richard Henderson
2023-06-13 13:33 ` [PATCH v3 9/9] meson: Replace softmmu_ss -> system_ss Philippe Mathieu-Daudé
2023-06-14  6:41 ` [PATCH v3 0/9] bulk: Replace CONFIG_SOFTMMU by !CONFIG_USER_ONLY/CONFIG_SYSTEM_ONLY Nicholas Piggin

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=20230613133347.82210-3-philmd@linaro.org \
    --to=philmd@linaro.org \
    --cc=qemu-arm@nongnu.org \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-ppc@nongnu.org \
    --cc=qemu-riscv@nongnu.org \
    --cc=qemu-s390x@nongnu.org \
    --cc=richard.henderson@linaro.org \
    --cc=thuth@redhat.com \
    /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;
as well as URLs for NNTP newsgroup(s).