From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: qemu-devel@nongnu.org
Cc: "Richard Henderson" <richard.henderson@linaro.org>,
"Thomas Huth" <thuth@redhat.com>,
qemu-arm@nongnu.org, qemu-ppc@nongnu.org, qemu-s390x@nongnu.org,
"Paolo Bonzini" <pbonzini@redhat.com>,
qemu-riscv@nongnu.org,
"Philippe Mathieu-Daudé" <philmd@linaro.org>
Subject: [RFC PATCH v2 1/9] target/tricore: Remove pointless CONFIG_SOFTMMU guard
Date: Tue, 6 Jun 2023 00:24:12 +0200 [thread overview]
Message-ID: <20230605222420.14776-2-philmd@linaro.org> (raw)
In-Reply-To: <20230605222420.14776-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>
---
target/tricore/helper.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/target/tricore/helper.c b/target/tricore/helper.c
index 114685cce4..cd34b34133 100644
--- a/target/tricore/helper.c
+++ b/target/tricore/helper.c
@@ -30,7 +30,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)
@@ -56,7 +55,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
next prev parent reply other threads:[~2023-06-05 22:26 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-05 22:24 [RFC PATCH v2 0/9] bulk: Replace CONFIG_SOFTMMU by !CONFIG_USER_ONLY/CONFIG_SYSTEM_ONLY Philippe Mathieu-Daudé
2023-06-05 22:24 ` Philippe Mathieu-Daudé [this message]
2023-06-06 14:45 ` [RFC PATCH v2 1/9] target/tricore: Remove pointless CONFIG_SOFTMMU guard Richard Henderson
2023-06-05 22:24 ` [RFC PATCH v2 2/9] target/i386: Check for USER_ONLY definition instead of SOFTMMU one Philippe Mathieu-Daudé
2023-06-06 14:47 ` Richard Henderson
2023-06-05 22:24 ` [RFC PATCH v2 3/9] target/m68k: " Philippe Mathieu-Daudé
2023-06-06 14:48 ` Richard Henderson
2023-06-05 22:24 ` [RFC PATCH v2 4/9] target/ppc: " Philippe Mathieu-Daudé
2023-06-06 14:49 ` Richard Henderson
2023-06-05 22:24 ` [RFC PATCH v2 5/9] hw/core/cpu: " Philippe Mathieu-Daudé
2023-06-06 14:50 ` Richard Henderson
2023-06-05 22:24 ` [RFC PATCH v2 6/9] accel/tcg: " Philippe Mathieu-Daudé
2023-06-06 14:51 ` Richard Henderson
2023-06-05 22:24 ` [RFC PATCH v2 7/9] meson: Alias CONFIG_SOFTMMU -> CONFIG_SYSTEM_ONLY Philippe Mathieu-Daudé
2023-06-05 22:24 ` [RFC PATCH v2 8/9] meson: Replace " Philippe Mathieu-Daudé
2023-06-05 22:24 ` [RFC PATCH v2 9/9] meson: Replace softmmu_ss -> system_ss Philippe Mathieu-Daudé
2023-06-06 14:54 ` Richard Henderson
2023-06-05 22:28 ` [RFC PATCH v2 0/9] bulk: Replace CONFIG_SOFTMMU by !CONFIG_USER_ONLY/CONFIG_SYSTEM_ONLY Philippe Mathieu-Daudé
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=20230605222420.14776-2-philmd@linaro.org \
--to=philmd@linaro.org \
--cc=pbonzini@redhat.com \
--cc=qemu-arm@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).