Support disabling TCG on ARM (part 2)
Subsystems (2)
v3 cover Support disabling TCG on ARM (part 2)
Cover from Samuel Ortiz from (part 1) [1]:
This patchset allows for building and running ARM targets with TCG disabled. [...]
The rationale behind this work comes from the NEMU project where we're trying to only support x86 and ARM 64-bit architectures, without including the TCG code base. We can only do so if we can build and run ARM binaries with TCG disabled.
v3 almost 18 months later:
- Rebased
- Addressed Thomas review comments
- Added Travis-CI job to keep building --disable-tcg on ARM
v2 [2]:
- Addressed review comments from Richard and Thomas from v1 [3]
Regards,
Phil.
[1]: https://lists.gnu.org/archive/html/qemu-devel/2018-11/msg02451.html
[2]: https://www.mail-archive.com/[email protected]/msg641796.html
[3]: https://lists.gnu.org/archive/html/qemu-devel/2019-08/msg05003.html
Based-on: <[email protected]> "accel: Allow targets to use Kconfig, disable semihosting by default"
https://lists.gnu.org/archive/html/qemu-devel/2020-03/msg04653.html
Philippe Mathieu-Daudé (15):
target/arm: Rename KVM set_feature() as kvm_set_feature() target/arm: Restrict DC-CVAP instruction to TCG accel target/arm: Restric the Address Translate operations to TCG accel target/arm: Restrict Virtualization Host Extensions instructions to
TCG
target/arm: Move Makefile variable restricted to CONFIG_TCG target/arm: Add semihosting stub to allow building without TCG target/arm: Move ARM_V7M Kconfig from hw/ to target/ target/arm: Restrict ARMv4 cpus to TCG accel
target/arm: Restrict ARMv5 cpus to TCG accel
target/arm: Restrict ARMv6 cpus to TCG accel
target/arm: Restrict ARMv7 R-profile cpus to TCG accel target/arm: Restrict ARMv7 M-profile cpus to TCG accel hw/arm: Automatically select the 'virt' machine on KVM hw/arm: Do not build to 'virt' machine on Xen .travis.yml: Add a KVM-only Aarch64 job
Samuel Ortiz (1):
target/arm: Do not build TCG objects when TCG is off
Thomas Huth (3):
target/arm: Make set_feature() available for other files target/arm: Make cpu_register() available for other files target/arm: Make m_helper.c optional via CONFIG_ARM_V7M
default-configs/aarch64-softmmu.mak | 1 - default-configs/arm-softmmu.mak | 30 -- target/arm/cpu-qom.h | 9 +- target/arm/cpu.h | 7 + target/arm/internals.h | 10 + target/arm/arm-semi-stub.c | 13 + target/arm/cpu.c | 651 +--------------------------- target/arm/cpu64.c | 19 +- target/arm/cpu_v4.c | 65 +++ target/arm/cpu_v5.c | 266 ++++++++++++ target/arm/cpu_v6.c | 171 ++++++++ target/arm/cpu_v7m.c | 207 +++++++++ target/arm/cpu_v7r.c | 83 ++++ target/arm/helper.c | 54 +-- target/arm/kvm32.c | 10 +- target/arm/kvm64.c | 16 +- target/arm/m_helper-stub.c | 59 +++ .travis.yml | 32 ++ hw/arm/Kconfig | 17 +- target/Kconfig | 2 +- target/arm/Kconfig | 19 + target/arm/Makefile.objs | 17 +- 22 files changed, 1016 insertions(+), 742 deletions(-) create mode 100644 target/arm/arm-semi-stub.c create mode 100644 target/arm/cpu_v4.c create mode 100644 target/arm/cpu_v5.c create mode 100644 target/arm/cpu_v6.c create mode 100644 target/arm/cpu_v7m.c create mode 100644 target/arm/cpu_v7r.c create mode 100644 target/arm/m_helper-stub.c create mode 100644 target/arm/Kconfig
Signature · 1 line
2.21.1
PATCH v3 1/19 target/arm: Rename KVM set_feature() as kvm_set_feature()
--- target/arm/kvm32.c | 10 +++++----- target/arm/kvm64.c | 16 ++++++++-------- 2 files changed, 13 insertions(+), 13 deletions(-)
target/arm/kvm32.c +5 -5
@@ -22,7 +22,7 @@#include "internals.h" #include "qemu/log.h" -static inline void set_feature (uint64_t *features,int feature) +static inline void kvm_set_feature (uint64_t *features,int feature) { *features |=1ULL << feature; }
@@ -146,14 +146,14 @@ bool kvm_arm_get_host_cpu_features(ARMHostCPUFeatures *ahcf)* timers; this in turn implies most of the other feature * bits, but a few must be tested. */ -set_feature (&features,ARM_FEATURE_V7VE ); -set_feature (&features,ARM_FEATURE_GENERIC_TIMER ); +kvm_set_feature (&features,ARM_FEATURE_V7VE ); +kvm_set_feature (&features,ARM_FEATURE_GENERIC_TIMER );if (extract32 (id_pfr0,12 ,4 ) ==1 ) { -set_feature (&features,ARM_FEATURE_THUMB2EE ); +kvm_set_feature (&features,ARM_FEATURE_THUMB2EE ); }if (extract32 (ahcf->isar.mvfr1,12 ,4 ) ==1 ) { -set_feature (&features,ARM_FEATURE_NEON ); +kvm_set_feature (&features,ARM_FEATURE_NEON ); } ahcf->features = features;
target/arm/kvm64.c +8 -8
@@ -447,12 +447,12 @@ void kvm_arm_pmu_set_irq(CPUState *cs, int irq) } } -static inline void set_feature (uint64_t *features,int feature) +static inline void kvm_set_feature (uint64_t *features,int feature) { *features |=1ULL << feature; } -static inline void unset_feature (uint64_t *features,int feature) +static inline void kvm_unset_feature (uint64_t *features,int feature) { *features &= ~(1ULL << feature); }
@@ -648,11 +648,11 @@ bool kvm_arm_get_host_cpu_features(ARMHostCPUFeatures *ahcf)* with VFPv4+Neon; this in turn implies most of the other * feature bits. */ -set_feature (&features,ARM_FEATURE_V8 ); -set_feature (&features,ARM_FEATURE_NEON ); -set_feature (&features,ARM_FEATURE_AARCH64 ); -set_feature (&features,ARM_FEATURE_PMU ); -set_feature (&features,ARM_FEATURE_GENERIC_TIMER ); +kvm_set_feature (&features,ARM_FEATURE_V8 ); +kvm_set_feature (&features,ARM_FEATURE_NEON ); +kvm_set_feature (&features,ARM_FEATURE_AARCH64 ); +kvm_set_feature (&features,ARM_FEATURE_PMU ); +kvm_set_feature (&features,ARM_FEATURE_GENERIC_TIMER ); ahcf->features = features;
@@ -802,7 +802,7 @@ int kvm_arch_init_vcpu(CPUState *cs)if (cpu->has_pmu) { cpu->kvm_init_features[0 ] |=1 <<KVM_ARM_VCPU_PMU_V3 ; }else { -unset_feature (&env->features,ARM_FEATURE_PMU ); +kvm_unset_feature (&env->features,ARM_FEATURE_PMU ); }if (cpu_isar_feature (aa64_sve, cpu)) {assert (kvm_arm_sve_supported (cs));
Signature · 1 line
2.21.1
Re: [PATCH v3 01/19] target/arm: Rename KVM set_feature() as kvm_set_feature()
target/arm/kvm32.c line 25
Quoted 7 lines · Philippe Mathieu-Daudé
+++
b/target/arm/kvm32.ctarget/arm/kvm32.c +1
-1@@ -22,7 +22,7 @@#include "internals.h" #include "qemu/log.h" -static inline void set_feature (uint64_t *features,int feature) +static inline void kvm_set_feature (uint64_t *features,int feature)
Why, what's wrong with the existing name?
Plus, with patch 2, you can just remove these.
r~
Re: [PATCH v3 01/19] target/arm: Rename KVM set_feature() as kvm_set_feature()
Quoted 11 lines · Richard Henderson
target/arm/kvm32.c line 25
Quoted 7 lines · Philippe Mathieu-Daudé
+++
b/target/arm/kvm32.ctarget/arm/kvm32.c +1
-1@@ -22,7 +22,7 @@#include "internals.h" #include "qemu/log.h" -static inline void set_feature (uint64_t *features,int feature) +static inline void kvm_set_feature (uint64_t *features,int feature)Why, what's wrong with the existing name?
Plus, with patch 2, you can just remove these.
The prototypes are different:
void set_feature(uint64_t *features, int feature)
void set_feature(CPUARMState *env, int feature)
Anyway you are right, I'll use the later prototype instead, thanks.
Re: [PATCH v3 01/19] target/arm: Rename KVM set_feature() as kvm_set_feature()
Quoted 10 lines · Philippe Mathieu-Daudé
Quoted 9 lines · Richard Henderson
target/arm/kvm32.c line 24
Quoted 6 lines · Philippe Mathieu-Daudé
+++
b/target/arm/kvm32.ctarget/arm/kvm32.c +1
-1@@ -22,7 +22,7 @@ #include "internals.h" #include "qemu/log.h" -static inline void set_feature (uint64_t *features,int feature) +static inline void kvm_set_feature (uint64_t *features,int feature)Why, what's wrong with the existing name?
Peter suggested the rename here:
https://www.mail-archive.com/[email protected]/msg641931.html
Quoted 1 line
Quoted 1 line
Plus, with patch 2, you can just remove these.
Since they don't have the same prototype, they clash:
target/arm/kvm64.c:450:20: error: conflicting types for ‘set_feature’
static inline void set_feature(uint64_t *features, int feature)
^~~~~~~~~~~
In file included from target/arm/kvm64.c:30:0:
target/arm/internals.h:30:20: note: previous definition of ‘set_feature’ was here
static inline void set_feature(CPUARMState *env, int feature)
^~~~~~~~~~~
target/arm/kvm64.c:455:20: error: conflicting types for ‘unset_feature’
static inline void unset_feature(uint64_t *features, int feature)
^~~~~~~~~~~~~
In file included from target/arm/kvm64.c:30:0:
target/arm/internals.h:35:20: note: previous definition of ‘unset_feature’ was here
static inline void unset_feature(CPUARMState *env, int feature)
^~~~~~~~~~~~~rules.mak:69: recipe for target 'target/arm/kvm64.o' failed make[1]: *** [target/arm/kvm64.o] Error 1
Quoted 8 lines
The prototypes are different:
void
set_feature(uint64_t *features, int feature)void
set_feature(CPUARMState *env, int feature)Anyway you are right, I'll use the later prototype instead, thanks.
There are ~180 uses of set_feature(CPUARMState,...) and 10 of set_feature(uint64_t,...) (kvm32:4 kvm64:6).
We are going to remove kvm32, so replacing 180 set_feature(env) by set_feature(env->features) seems a waste.
If you prefer to avoid renaming as kvm_set_feature() another option is to move the declaration in a local "features.h" header that would not be included by kvm*.c.
The main problem is the use of the ARMHostCPUFeatures structure which apparently was introduced similar to a CPUClass (commit a96c0514ab7) then lost this in commit c4487d76d52.
Re: [PATCH v3 01/19] target/arm: Rename KVM set_feature() as kvm_set_feature()
Quoted 13 lines · Philippe Mathieu-Daudé
Quoted 10 lines · Philippe Mathieu-Daudé
Quoted 9 lines · Richard Henderson
target/arm/kvm32.c line 24
Quoted 6 lines · Philippe Mathieu-Daudé
+++
b/target/arm/kvm32.ctarget/arm/kvm32.c +1
-1@@ -22,7 +22,7 @@#include "internals.h" #include "qemu/log.h" -static inline void set_feature (uint64_t *features,int feature) +static inline void kvm_set_feature (uint64_t *features,int feature)Why, what's wrong with the existing name?
Quoted 2 lines
Peter suggested the rename here:
https://www.mail-archive.com/[email protected]/msg641931.html
In that message I suggest that if you move the set_feature() function to cpu.h (which is included in lots of places) then that is too generic a name to use for it. The function of the same name here in kvm32.c is fine, because it's 'static inline' and only visible in this file, so the bar for naming is lower. (In fact, it's a demonstration of why you don't want a generic name like 'set_feature' in a widely included header file.)
thanks
-- PMM
Re: [PATCH v3 01/19] target/arm: Rename KVM set_feature() as kvm_set_feature()
Quoted 17 lines · Peter Maydell
Quoted 13 lines · Philippe Mathieu-Daudé
Quoted 10 lines · Philippe Mathieu-Daudé
Quoted 9 lines · Richard Henderson
target/arm/kvm32.c line 24
Quoted 6 lines · Philippe Mathieu-Daudé
+++
b/target/arm/kvm32.ctarget/arm/kvm32.c +1
-1@@ -22,7 +22,7 @@#include "internals.h" #include "qemu/log.h" -static inline void set_feature (uint64_t *features,int feature) +static inline void kvm_set_feature (uint64_t *features,int feature)Why, what's wrong with the existing name?
Quoted 2 lines
Peter suggested the rename here:
https://www.mail-archive.com/[email protected]/msg641931.html
Quoted 8 lines
In that message I suggest that if you move the
set_feature()function tocpu.h(which is included in lots of places) then that is too generic a name to use for it. The function of the same name here inkvm32.cis fine, because it's 'static inline' and only visible in this file, so the bar for naming is lower. (In fact, it's a demonstration of why you don't want a generic name like 'set_feature' in a widely included header file.)
And your suggestion is indeed obviously correct...
Apparently after 19 months rebasing this work I'm not seeing clearly.
Thanks again!
PATCH v3 2/19 target/arm: Make set_feature() available for other files
In reply to Philippe Mathieu-DaudéFrom: Thomas Huth <[email protected]>
Move the common set_feature() and unset_feature() functions from cpu.c and cpu64.c to internals.h.
Message-ID: <[email protected]>
--- target/arm/internals.h | 10 ++++++++++ target/arm/cpu.c | 10 ---------- target/arm/cpu64.c | 11 +---------- 3 files changed, 11 insertions(+), 20 deletions(-)
target/arm/internals.h +10 -0
@@ -27,6 +27,16 @@#include "hw/registerfields.h" +static inline void set_feature (CPUARMState *env,int feature) +{ + env->features |=1ULL << feature; +} + +static inline void unset_feature (CPUARMState *env,int feature) +{ + env->features &= ~(1ULL << feature); +} +/* register banks for CPU modes */ #define BANK_USRSYS 0#define BANK_SVC 1
target/arm/cpu.c +0 -10
@@ -723,16 +723,6 @@ static bool arm_cpu_virtio_is_big_endian(CPUState *cs)#endif -static inline void set_feature (CPUARMState *env,int feature) -{ - env->features |=1ULL << feature; -} - -static inline void unset_feature (CPUARMState *env,int feature) -{ - env->features &= ~(1ULL << feature); -} -static int print_insn_thumb1 (bfd_vma pc,disassemble_info *info) {
target/arm/cpu64.c +1 -10
@@ -21,6 +21,7 @@#include "qemu/osdep.h" #include "qapi/error.h" #include "cpu.h" +#include "internals.h" #include "qemu/module.h" #if !defined(CONFIG_USER_ONLY )#include "hw/loader.h"
@@ -29,16 +30,6 @@#include "kvm_arm.h" #include "qapi/visitor.h" -static inline void set_feature (CPUARMState *env,int feature) -{ - env->features |=1ULL << feature; -} - -static inline void unset_feature (CPUARMState *env,int feature) -{ - env->features &= ~(1ULL << feature); -} -#ifndef CONFIG_USER_ONLY static uint64_t a57_a53_l2ctlr_read (CPUARMState *env,const ARMCPRegInfo *ri) {
Signature · 1 line
2.21.1
PATCH v3 3/19 target/arm: Restrict DC-CVAP instruction to TCG accel
In reply to Philippe Mathieu-DaudéUnder KVM the 'Data or unified Cache line Clean by VA to PoP' instruction will trap.
--- target/arm/helper.c | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-)
target/arm/helper.c +6 -6
@@ -6777,7 +6777,7 @@ static const ARMCPRegInfo rndr_reginfo[] = {REGINFO_SENTINEL }; -#ifndef CONFIG_USER_ONLY +#if !defined(CONFIG_USER_ONLY ) && defined(CONFIG_TCG )static void dccvap_writefn (CPUARMState *env,const ARMCPRegInfo *opaque,uint64_t value) {
@@ -6820,9 +6820,9 @@ static const ARMCPRegInfo dcpodp_reg[] = { .accessfn = aa64_cacheop_poc_access, .writefn = dccvap_writefn },REGINFO_SENTINEL }; -#endif /*CONFIG_USER_ONLY*/ +#endif /* !CONFIG_USER_ONLY && CONFIG_TCG */ -#endif +#endif /* TARGET_AARCH64 */ static CPAccessResult access_predinv (CPUARMState *env,const ARMCPRegInfo *ri,bool isread)
@@ -7929,7 +7929,7 @@ void register_cp_regs_for_features(ARMCPU *cpu)if (cpu_isar_feature (aa64_rndr, cpu)) {define_arm_cp_regs (cpu, rndr_reginfo); } -#ifndef CONFIG_USER_ONLY +#if !defined(CONFIG_USER_ONLY ) && defined(CONFIG_TCG )/* Data Cache clean instructions up to PoP */ if (cpu_isar_feature (aa64_dcpop, cpu)) {define_one_arm_cp_reg (cpu, dcpop_reg);
@@ -7938,8 +7938,8 @@ void register_cp_regs_for_features(ARMCPU *cpu)define_one_arm_cp_reg (cpu, dcpodp_reg); } } -#endif /*CONFIG_USER_ONLY*/ -#endif +#endif /* !CONFIG_USER_ONLY && CONFIG_TCG */ +#endif /* TARGET_AARCH64 */ if (cpu_isar_feature (any_predinv, cpu)) {define_arm_cp_regs (cpu, predinv_reginfo);
Signature · 1 line
2.21.1
Re: [PATCH v3 03/19] target/arm: Restrict DC-CVAP instruction to TCG accel
Quoted 23 lines · Philippe Mathieu-Daudé
Under KVM the 'Data or unified Cache line Clean by VA to PoP' instruction will trap.
Fixes 0d57b4999 ("Add support for DC CVAP & DC CVADP ins")Signed-off-by Philippe Mathieu-Daudé <[email protected]>--- target/arm/helper.c | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-)target/arm/helper.c +1
-1@@ -6777,7 +6777,7 @@ static const ARMCPRegInfo rndr_reginfo[] = {REGINFO_SENTINEL }; -#ifndef CONFIG_USER_ONLY +#if !defined(CONFIG_USER_ONLY ) && defined(CONFIG_TCG )static void dccvap_writefn (CPUARMState *env,const ARMCPRegInfo *opaque,uint64_t value) {
target/arm/helper.c static const ARMCPRegInfo dcpodp_reg[] = { · line 6823
Quoted 5 lines
target/arm/helper.c +1
-1@@ -6820,9 +6820,9 @@ static const ARMCPRegInfo dcpodp_reg[] = { .accessfn = aa64_cacheop_poc_access, .writefn = dccvap_writefn },REGINFO_SENTINEL }; -#endif /*CONFIG_USER_ONLY*/ +#endif /* !CONFIG_USER_ONLY && CONFIG_TCG */
I'm not 100% sure how the system regs function under kvm.
If they are not used at all, then we should avoid them all en masse an not piecemeal like this.
If they are used for something, then we should keep them registered and change the writefn like so:
#ifdef CONFIG_TCG
/* existing stuff */
#else
/* Handled by hardware accelerator. */
g_assert_not_reached();#endif
r~
Quoted 27 lines
target/arm/helper.c +4
-4-#endif +#endif /* TARGET_AARCH64 */ static CPAccessResult access_predinv (CPUARMState *env,const ARMCPRegInfo *ri,bool isread)@@ -7929,7 +7929,7 @@ void register_cp_regs_for_features(ARMCPU *cpu)if (cpu_isar_feature (aa64_rndr, cpu)) {define_arm_cp_regs (cpu, rndr_reginfo); } -#ifndef CONFIG_USER_ONLY +#if !defined(CONFIG_USER_ONLY ) && defined(CONFIG_TCG )/* Data Cache clean instructions up to PoP */ if (cpu_isar_feature (aa64_dcpop, cpu)) {define_one_arm_cp_reg (cpu, dcpop_reg);@@ -7938,8 +7938,8 @@ void register_cp_regs_for_features(ARMCPU *cpu)define_one_arm_cp_reg (cpu, dcpodp_reg); } } -#endif /*CONFIG_USER_ONLY*/ -#endif +#endif /* !CONFIG_USER_ONLY && CONFIG_TCG */ +#endif /* TARGET_AARCH64 */ if (cpu_isar_feature (any_predinv, cpu)) {define_arm_cp_regs (cpu, predinv_reginfo);
Re: [PATCH v3 03/19] target/arm: Restrict DC-CVAP instruction to TCG accel
Quoted 8 lines · Richard Henderson
I'm not 100% sure how the system regs function under kvm.
If they are not used at all, then we should avoid them all en masse an not piecemeal like this.
If they are used for something, then we should keep them registered and change the writefn like so:
Quoted 6 lines
#ifdef CONFIG_TCG /* existing stuff */ #else /* Handled by hardware accelerator. */ g_assert_not_reached();#endif
(1) for those registers where we need to know the value within QEMU code (notably anything involved in VA-to-PA translation, as this is used by gdbstub accesses, etc, but sometimes we want other register values too): the sysreg struct is what lets us map from the KVM register to the field in the CPU struct when we do a sync of data to/from the kernel.
(2) for other registers, the sync lets us make the register visible as an r/o register in the gdbstub. (this is not very important, but it's nice)
(3) Either way, the sync works via the raw_read/raw_write accessors (this is a big part of what they're for), which are supposed to just stuff the data into/out of the underlying CPU struct field. (But watch out because we fall back to using the non-raw read/writefn if there's no raw version provided for a particular register.) If a regdef is marked as NO_RAW then it means there is no raw access and we don't sync the value.
(4) I think that in KVM mode we won't deliberately do non-raw accesses, and a quick grep through of the places that do 'readfn' accesses supports that.
thanks
-- PMM
Re: [PATCH v3 03/19] target/arm: Restrict DC-CVAP instruction to TCG accel
Quoted 10 lines · Peter Maydell
Quoted 8 lines · Richard Henderson
I'm not 100% sure how the system regs function under kvm.
If they are not used at all, then we should avoid them all en masse an not piecemeal like this.
If they are used for something, then we should keep them registered and change the writefn like so:
Quoted 6 lines
Quoted 6 lines
#ifdef CONFIG_TCG /* existing stuff */ #else /* Handled by hardware accelerator. */ g_assert_not_reached();#endif
I ended with that patch because dccvap_writefn() calls probe_read() which is an inlined call to probe_access(), which itself is only defined when using TCG. So with KVM either linking fails or I get:
target/arm/helper.c: In function ‘dccvap_writefn’:target/arm/helper.c:6898:13: error: implicit declaration of function ‘probe_read’;
haddr = probe_read(env, vaddr, dline_size, mem_idx, GETPC());
^~~~~~~~~~I'll use your suggestion which works for me:
-- >8 --
include/exec/exec-all.h +2 -0
@@ -330,8 +330,20 @@ static inline void tlb_flush_by_mmuidx_all_cpus_synced(CPUState *cpu, { }#endif + +#ifdef CONFIG_TCG void *probe_access (CPUArchState *env,target_ulong addr,int size, MMUAccessType access_type, int mmu_idx, uintptr_t
retaddr);
+#else
+static inline void *probe_access(CPUArchState *env,
+ target_ulong addr, int size, + MMUAccessType access_type, + int mmu_idx, uintptr_t retaddr)
+{
+ /* Handled by hardware accelerator. */
+ g_assert_not_reached();
+}
+#endif /* CONFIG_TCG */
static inline void *probe_write(CPUArchState *env, target_ulong addr,
int size,
int mmu_idx, uintptr_t retaddr)
---
Quoted 28 lines
(1) for those registers where we need to know the value within QEMU code (notably anything involved in VA-to-PA translation, as this is used by gdbstub accesses, etc, but sometimes we want other register values too): the sysreg struct is what lets us map from the KVM register to the field in the CPU struct when we do a sync of data to/from the kernel.
(2) for other registers, the sync lets us make the register visible as an r/o register in the gdbstub. (this is not very important, but it's nice)
(3) Either way, the sync works via the raw_read/raw_write accessors (this is a big part of what they're for), which are supposed to just stuff the data into/out of the underlying CPU struct field. (But watch out because we fall back to using the non-raw read/writefn if there's no raw version provided for a particular register.) If a regdef is marked as
NO_RAWthen it means there is no raw access and we don't sync the value.(4) I think that in KVM mode we won't deliberately do non-raw accesses, and a quick grep through of the places that do 'readfn' accesses supports that.
thanks
-- PMM
Re: [PATCH v3 03/19] target/arm: Restrict DC-CVAP instruction to TCG accel
Quoted 23 lines · Philippe Mathieu-Daudé
Quoted 10 lines · Peter Maydell
Quoted 8 lines · Richard Henderson
I'm not 100% sure how the system regs function under kvm.
If they are not used at all, then we should avoid them all en masse an not piecemeal like this.
If they are used for something, then we should keep them registered and change the writefn like so:
Quoted 6 lines
Quoted 6 lines
#ifdef CONFIG_TCG /* existing stuff */ #else /* Handled by hardware accelerator. */ g_assert_not_reached();#endif
I ended with that patch because
dccvap_writefn()callsprobe_read()which is an inlined call toprobe_access(), which itself is only defined when using TCG. So with KVM either linking fails or I get:
Quoted 5 lines
target/arm/helper.c: In function ‘dccvap_writefn’:target/arm/helper.c:6898:13: error: implicit declaration of function‘probe_read’; haddr = probe_read(env, vaddr, dline_size, mem_idx, GETPC()); ^~~~~~~~~~
IN this particular case, DC CVAP is really a system insn rather than a 'register'; our register struct for it is marked up as ARM_CP_NO_RAW, which means we'll effectively ignore it when running KVM (it will not be migrated, have its state synced against the kernel, or be visible in gdb). If dccvap_writefn() ever gets called somehow that's a bug, so having it end up with an assert is the right thing.
Quoted 1 line
I'll use your suggestion which works for me:
Your suggested patch isn't quite the same as RTH's suggestion, because it puts the assert inside a stub probe_read() implementation rather than having the ifdef at the level of the writefn body. I have no opinion on whether one or the other of these is preferable.
thanks
-- PMM
Re: [PATCH v3 03/19] target/arm: Restrict DC-CVAP instruction to TCG accel
Quoted 38 lines · Peter Maydell
Quoted 23 lines · Philippe Mathieu-Daudé
Quoted 10 lines · Peter Maydell
Quoted 8 lines · Richard Henderson
I'm not 100% sure how the system regs function under kvm.
If they are not used at all, then we should avoid them all en masse an not piecemeal like this.
If they are used for something, then we should keep them registered and change the writefn like so:
Quoted 6 lines
Quoted 6 lines
#ifdef CONFIG_TCG /* existing stuff */ #else /* Handled by hardware accelerator. */ g_assert_not_reached();#endif
I ended with that patch because
dccvap_writefn()callsprobe_read()which is an inlined call toprobe_access(), which itself is only defined when using TCG. So with KVM either linking fails or I get:Quoted 5 lines
target/arm/helper.c: In function ‘dccvap_writefn’:target/arm/helper.c:6898:13: error: implicit declaration of function‘probe_read’; haddr = probe_read(env, vaddr, dline_size, mem_idx, GETPC()); ^~~~~~~~~~IN this particular case, DC CVAP is really a system insn rather than a 'register'; our register struct for it is marked up as
ARM_CP_NO_RAW, which means we'll effectively ignore it when running KVM (it will not be migrated, have its state synced against the kernel, or be visible in gdb). Ifdccvap_writefn()ever gets called somehow that's a bug, so having it end up with an assert is the right thing.
Quoted 7 lines
Quoted 1 line
I'll use your suggestion which works for me:
Your suggested patch isn't quite the same as RTH's suggestion, because it puts the assert inside a stub
probe_read()implementation rather than having the ifdef at the level of the writefn body. I have no opinion on whether one or the other of these is preferable.
I'll let Richard modify the writefn() bodies if required, as he understand what they do :)
Btw since we have this rule:
obj-$(call lnot,$(CONFIG_TCG)) += tcg-stub.o
I'll use the following patch which is less intrusive:
-- >8 --
index 677191a69c..e4bbf997aa 100644
accel/stubs/tcg-stub.c +7 -0
@@ -22,3 +22,10 @@ void tb_flush(CPUState *cpu)void tlb_set_dirty (CPUState *cpu,target_ulong vaddr) { } + +void *probe_access (CPUArchState *env,target_ulong addr,int size, +MMUAccessType access_type,int mmu_idx,uintptr_t retaddr) +{ +/* Handled by hardware accelerator. */ +g_assert_not_reached (); +}
---
Quoted 4 lines
thanks
-- PMM
Re: [PATCH v3 03/19] target/arm: Restrict DC-CVAP instruction to TCG accel
Quoted 10 lines · Philippe Mathieu-Daudé
Quoted 5 lines · Peter Maydell
Your suggested patch isn't quite the same as RTH's suggestion, because it puts the assert inside a stub
probe_read()implementation rather than having the ifdef at the level of the writefn body. I have no opinion on whether one or the other of these is preferable.I'll let Richard modify the
writefn()bodies if required, as he understand what they do :)
RTH is suggesting
static void dccvap_writefn(CPUARMState *env, const ARMCPRegInfo *opaque,
uint64_t value)
{
#ifdef CONFIG_TCG
entire current body of function goes here
#else
g_assert_not_reached();#endif
}
If we take that approach then the stub probe_read() would be pointless, so we should do one or the other, not both.
Quoted 5 lines
Btw since we have this rule:
obj-$(call lnot,$(CONFIG_TCG)) += tcg-stub.o
I'll use the following patch which is less intrusive:
This is temptingly less ifdeffery, certainly
-- PMM
PATCH v3 4/19 target/arm: Restric the Address Translate operations to TCG accel
In reply to Philippe Mathieu-DaudéUnder KVM the ATS instruction will trap.
--- target/arm/helper.c | 20 +++++++++++--------- 1 file changed, 11 insertions(+), 9 deletions(-)
target/arm/helper.c +11 -9
@@ -3322,7 +3322,7 @@ static void par_write(CPUARMState *env, const ARMCPRegInfo *ri, uint64_t value) } } -#ifndef CONFIG_USER_ONLY +#if !defined(CONFIG_USER_ONLY ) && defined(CONFIG_TCG )/* get_phys_addr() isn't present for user-mode-only targets */ static CPAccessResult ats_access(CPUARMState *env, const ARMCPRegInfo *ri,
@@ -3631,7 +3631,7 @@ static void ats_write64(CPUARMState *env, const ARMCPRegInfo *ri, env->cp15.par_el[1 ] =do_ats_write (env, value, access_type, mmu_idx); } -#endif +#endif /* !CONFIG_USER_ONLY && CONFIG_TCG */ static const ARMCPRegInfo vapa_cp_reginfo[] = { { .name ="PAR" , .cp =15 , .crn =7 , .crm =4 , .opc1 =0 , .opc2 =0 ,
@@ -3639,7 +3639,7 @@ static const ARMCPRegInfo vapa_cp_reginfo[] = { .bank_fieldoffsets = { offsetoflow32(CPUARMState, cp15.par_s), offsetoflow32(CPUARMState, cp15.par_ns) }, .writefn = par_write }, -#ifndef CONFIG_USER_ONLY +#if !defined(CONFIG_USER_ONLY) && defined(CONFIG_TCG)/* This underdecoding is safe because the reginfo is NO_RAW. */ { .name = "ATS", .cp = 15, .crn = 7, .crm = 8, .opc1 = 0, .opc2 = CP_ANY, .access = PL1_W, .accessfn = ats_access,
@@ -4880,7 +4880,8 @@ static const ARMCPRegInfo v8_cp_reginfo[] = { .opc0 = 1, .opc1 = 4, .crn = 8, .crm = 7, .opc2 = 6, .access = PL2_W, .type = ARM_CP_NO_RAW, .writefn = tlbi_aa64_alle1is_write }, -#ifndef CONFIG_USER_ONLY + +#if !defined(CONFIG_USER_ONLY ) && defined(CONFIG_TCG )/* 64 bit address translation operations */ { .name = "AT_S1E1R", .state = ARM_CP_STATE_AA64, .opc0 = 1, .opc1 = 0, .crn = 7, .crm = 8, .opc2 = 0,
@@ -4929,7 +4930,8 @@ static const ARMCPRegInfo v8_cp_reginfo[] = { .access = PL1_RW, .resetvalue = 0, .fieldoffset = offsetof(CPUARMState, cp15.par_el[1]), .writefn = par_write }, -#endif +#endif /* !CONFIG_USER_ONLY && CONFIG_TCG */ +/* TLB invalidate last level of translation table walk */ { .name = "TLBIMVALIS", .cp = 15, .opc1 = 0, .crn = 8, .crm = 3, .opc2 = 5, .type = ARM_CP_NO_RAW, .access = PL1_W, .accessfn = access_ttlb,
@@ -5536,7 +5538,7 @@ static const ARMCPRegInfo el2_cp_reginfo[] = { .opc0 = 1, .opc1 = 4, .crn = 8, .crm = 3, .opc2 = 5, .access = PL2_W, .type = ARM_CP_NO_RAW, .writefn = tlbi_aa64_vae2is_write }, -#ifndef CONFIG_USER_ONLY +#if !defined(CONFIG_USER_ONLY ) && defined(CONFIG_TCG )/* Unlike the other EL2-related AT operations, these must * UNDEF from EL3 if EL2 is not implemented, which is why we * define them here rather than with the rest of the AT ops.
@@ -6992,7 +6994,7 @@ static const ARMCPRegInfo vhe_reginfo[] = {REGINFO_SENTINEL }; -#ifndef CONFIG_USER_ONLY +#if !defined(CONFIG_USER_ONLY) && defined(CONFIG_TCG) static const ARMCPRegInfo ats1e1_reginfo[] = { { .name = "AT_S1E1R", .state = ARM_CP_STATE_AA64, .opc0 = 1, .opc1 = 0, .crn = 7, .crm = 9, .opc2 = 0,
@@ -7894,14 +7896,14 @@ void register_cp_regs_for_features(ARMCPU *cpu)if (cpu_isar_feature (aa64_pan, cpu)) {define_one_arm_cp_reg (cpu, &pan_reginfo); } -#ifndef CONFIG_USER_ONLY +#if !defined(CONFIG_USER_ONLY ) && defined(CONFIG_TCG )if (cpu_isar_feature (aa64_ats1e1, cpu)) {define_arm_cp_regs (cpu, ats1e1_reginfo); }if (cpu_isar_feature (aa32_ats1e1, cpu)) {define_arm_cp_regs (cpu, ats1cp_reginfo); } -#endif +#endif /* !CONFIG_USER_ONLY && CONFIG_TCG */ if (cpu_isar_feature (aa64_uao, cpu)) {define_one_arm_cp_reg (cpu, &uao_reginfo); }
Signature · 1 line
2.21.1
Re: [PATCH v3 04/19] target/arm: Restric the Address Translate operations to TCG accel
Quoted 1 line · Philippe Mathieu-Daudé
Under KVM the ATS instruction will trap.
Not trap, they'll just work.
Otherwise similar comment as for dcpop.
r~
Quoted 93 lines
Signed-off-by Philippe Mathieu-Daudé <[email protected]>--- target/arm/helper.c | 20 +++++++++++--------- 1 file changed, 11 insertions(+), 9 deletions(-)target/arm/helper.c +11
-9@@ -3322,7 +3322,7 @@ static void par_write(CPUARMState *env, const ARMCPRegInfo *ri, uint64_t value) } } -#ifndef CONFIG_USER_ONLY +#if !defined(CONFIG_USER_ONLY ) && defined(CONFIG_TCG )/* get_phys_addr() isn't present for user-mode-only targets */ static CPAccessResult ats_access(CPUARMState *env, const ARMCPRegInfo *ri,@@ -3631,7 +3631,7 @@ static void ats_write64(CPUARMState *env, const ARMCPRegInfo *ri, env->cp15.par_el[1 ] =do_ats_write (env, value, access_type, mmu_idx); } -#endif +#endif /* !CONFIG_USER_ONLY && CONFIG_TCG */ static const ARMCPRegInfo vapa_cp_reginfo[] = { { .name ="PAR" , .cp =15 , .crn =7 , .crm =4 , .opc1 =0 , .opc2 =0 ,@@ -3639,7 +3639,7 @@ static const ARMCPRegInfo vapa_cp_reginfo[] = { .bank_fieldoffsets = { offsetoflow32(CPUARMState, cp15.par_s), offsetoflow32(CPUARMState, cp15.par_ns) }, .writefn = par_write }, -#ifndef CONFIG_USER_ONLY +#if !defined(CONFIG_USER_ONLY) && defined(CONFIG_TCG)/* This underdecoding is safe because the reginfo is NO_RAW. */ { .name = "ATS", .cp = 15, .crn = 7, .crm = 8, .opc1 = 0, .opc2 = CP_ANY, .access = PL1_W, .accessfn = ats_access,@@ -4880,7 +4880,8 @@ static const ARMCPRegInfo v8_cp_reginfo[] = { .opc0 = 1, .opc1 = 4, .crn = 8, .crm = 7, .opc2 = 6, .access = PL2_W, .type = ARM_CP_NO_RAW, .writefn = tlbi_aa64_alle1is_write }, -#ifndef CONFIG_USER_ONLY + +#if !defined(CONFIG_USER_ONLY ) && defined(CONFIG_TCG )/* 64 bit address translation operations */ { .name = "AT_S1E1R", .state = ARM_CP_STATE_AA64, .opc0 = 1, .opc1 = 0, .crn = 7, .crm = 8, .opc2 = 0,@@ -4929,7 +4930,8 @@ static const ARMCPRegInfo v8_cp_reginfo[] = { .access = PL1_RW, .resetvalue = 0, .fieldoffset = offsetof(CPUARMState, cp15.par_el[1]), .writefn = par_write }, -#endif +#endif /* !CONFIG_USER_ONLY && CONFIG_TCG */ +/* TLB invalidate last level of translation table walk */ { .name = "TLBIMVALIS", .cp = 15, .opc1 = 0, .crn = 8, .crm = 3, .opc2 = 5, .type = ARM_CP_NO_RAW, .access = PL1_W, .accessfn = access_ttlb,@@ -5536,7 +5538,7 @@ static const ARMCPRegInfo el2_cp_reginfo[] = { .opc0 = 1, .opc1 = 4, .crn = 8, .crm = 3, .opc2 = 5, .access = PL2_W, .type = ARM_CP_NO_RAW, .writefn = tlbi_aa64_vae2is_write }, -#ifndef CONFIG_USER_ONLY +#if !defined(CONFIG_USER_ONLY ) && defined(CONFIG_TCG )/* Unlike the other EL2-related AT operations, these must * UNDEF from EL3 if EL2 is not implemented, which is why we * define them here rather than with the rest of the AT ops. @@ -6992,7 +6994,7 @@ static const ARMCPRegInfo vhe_reginfo[] = {REGINFO_SENTINEL }; -#ifndef CONFIG_USER_ONLY +#if !defined(CONFIG_USER_ONLY) && defined(CONFIG_TCG) static const ARMCPRegInfo ats1e1_reginfo[] = { { .name = "AT_S1E1R", .state = ARM_CP_STATE_AA64, .opc0 = 1, .opc1 = 0, .crn = 7, .crm = 9, .opc2 = 0,@@ -7894,14 +7896,14 @@ void register_cp_regs_for_features(ARMCPU *cpu)if (cpu_isar_feature (aa64_pan, cpu)) {define_one_arm_cp_reg (cpu, &pan_reginfo); } -#ifndef CONFIG_USER_ONLY +#if !defined(CONFIG_USER_ONLY ) && defined(CONFIG_TCG )if (cpu_isar_feature (aa64_ats1e1, cpu)) {define_arm_cp_regs (cpu, ats1e1_reginfo); }if (cpu_isar_feature (aa32_ats1e1, cpu)) {define_arm_cp_regs (cpu, ats1cp_reginfo); } -#endif +#endif /* !CONFIG_USER_ONLY && CONFIG_TCG */ if (cpu_isar_feature (aa64_uao, cpu)) {define_one_arm_cp_reg (cpu, &uao_reginfo); }
PATCH v3 5/19 target/arm: Restrict Virtualization Host Extensions instructions to TCG
In reply to Philippe Mathieu-DaudéUnder KVM the ARMv8.1-VHE instruction will trap.
--- target/arm/helper.c | 22 ++++++++++++---------- 1 file changed, 12 insertions(+), 10 deletions(-)
target/arm/helper.c +12 -10
@@ -2897,16 +2897,6 @@ static void gt_virt_ctl_write(CPUARMState *env, const ARMCPRegInfo *ri,gt_ctl_write (env, ri,GTIMER_VIRT , value); } -static void gt_cntvoff_write (CPUARMState *env,const ARMCPRegInfo *ri, -uint64_t value) -{ -ARMCPU *cpu =env_archcpu (env); - -trace_arm_gt_cntvoff_write (value); -raw_write (env, ri, value); -gt_recalc_timer (cpu,GTIMER_VIRT ); -} -static uint64_t gt_virt_redir_cval_read (CPUARMState *env,const ARMCPRegInfo *ri) {
@@ -2949,6 +2939,17 @@ static void gt_virt_redir_ctl_write(CPUARMState *env, const ARMCPRegInfo *ri,gt_ctl_write (env, ri, timeridx, value); } +#if !defined(CONFIG_USER_ONLY ) && defined(CONFIG_TCG ) +static void gt_cntvoff_write (CPUARMState *env,const ARMCPRegInfo *ri, +uint64_t value) +{ +ARMCPU *cpu =env_archcpu (env); + +trace_arm_gt_cntvoff_write (value); +raw_write (env, ri, value); +gt_recalc_timer (cpu,GTIMER_VIRT ); +} +static void gt_hyp_timer_reset (CPUARMState *env,const ARMCPRegInfo *ri) {gt_timer_reset (env, ri,GTIMER_HYP );
@@ -2976,6 +2977,7 @@ static void gt_hyp_ctl_write(CPUARMState *env, const ARMCPRegInfo *ri, {gt_ctl_write (env, ri,GTIMER_HYP , value); } +#endif /* !CONFIG_USER_ONLY && CONFIG_TCG */ static void gt_sec_timer_reset (CPUARMState *env,const ARMCPRegInfo *ri) {
Signature · 1 line
2.21.1
Re: [PATCH v3 05/19] target/arm: Restrict Virtualization Host Extensions instructions to TCG
Quoted 6 lines · Philippe Mathieu-Daudé
Under KVM the ARMv8.1-VHE instruction will trap.
Signed-off-by Philippe Mathieu-Daudé <[email protected]>--- target/arm/helper.c | 22 ++++++++++++---------- 1 file changed, 12 insertions(+), 10 deletions(-)
What happened to the uses of these functions?
r~
Quoted 49 lines
target/arm/helper.c +12
-10@@ -2897,16 +2897,6 @@ static void gt_virt_ctl_write(CPUARMState *env, const ARMCPRegInfo *ri,gt_ctl_write (env, ri,GTIMER_VIRT , value); } -static void gt_cntvoff_write (CPUARMState *env,const ARMCPRegInfo *ri, -uint64_t value) -{ -ARMCPU *cpu =env_archcpu (env); - -trace_arm_gt_cntvoff_write (value); -raw_write (env, ri, value); -gt_recalc_timer (cpu,GTIMER_VIRT ); -} -static uint64_t gt_virt_redir_cval_read (CPUARMState *env,const ARMCPRegInfo *ri) {@@ -2949,6 +2939,17 @@ static void gt_virt_redir_ctl_write(CPUARMState *env, const ARMCPRegInfo *ri,gt_ctl_write (env, ri, timeridx, value); } +#if !defined(CONFIG_USER_ONLY ) && defined(CONFIG_TCG ) +static void gt_cntvoff_write (CPUARMState *env,const ARMCPRegInfo *ri, +uint64_t value) +{ +ARMCPU *cpu =env_archcpu (env); + +trace_arm_gt_cntvoff_write (value); +raw_write (env, ri, value); +gt_recalc_timer (cpu,GTIMER_VIRT ); +} +static void gt_hyp_timer_reset (CPUARMState *env,const ARMCPRegInfo *ri) {gt_timer_reset (env, ri,GTIMER_HYP );@@ -2976,6 +2977,7 @@ static void gt_hyp_ctl_write(CPUARMState *env, const ARMCPRegInfo *ri, {gt_ctl_write (env, ri,GTIMER_HYP , value); } +#endif /* !CONFIG_USER_ONLY && CONFIG_TCG */ static void gt_sec_timer_reset (CPUARMState *env,const ARMCPRegInfo *ri) {
Re: [PATCH v3 05/19] target/arm: Restrict Virtualization Host Extensions instructions to TCG
Quoted 9 lines · Richard Henderson
Quoted 6 lines · Philippe Mathieu-Daudé
Under KVM the ARMv8.1-VHE instruction will trap.
Signed-off-by Philippe Mathieu-Daudé <[email protected]>--- target/arm/helper.c | 22 ++++++++++++---------- 1 file changed, 12 insertions(+), 10 deletions(-)What happened to the uses of these functions?
Sincerely I don't remember... I got this branch working again without this patch, so I'll just drop it.
Quoted 53 lines
r~
Quoted 49 lines
target/arm/helper.c +12
-10@@ -2897,16 +2897,6 @@ static void gt_virt_ctl_write(CPUARMState *env, const ARMCPRegInfo *ri,gt_ctl_write (env, ri,GTIMER_VIRT , value); } -static void gt_cntvoff_write (CPUARMState *env,const ARMCPRegInfo *ri, -uint64_t value) -{ -ARMCPU *cpu =env_archcpu (env); - -trace_arm_gt_cntvoff_write (value); -raw_write (env, ri, value); -gt_recalc_timer (cpu,GTIMER_VIRT ); -} -static uint64_t gt_virt_redir_cval_read (CPUARMState *env,const ARMCPRegInfo *ri) {@@ -2949,6 +2939,17 @@ static void gt_virt_redir_ctl_write(CPUARMState *env, const ARMCPRegInfo *ri,gt_ctl_write (env, ri, timeridx, value); } +#if !defined(CONFIG_USER_ONLY ) && defined(CONFIG_TCG ) +static void gt_cntvoff_write (CPUARMState *env,const ARMCPRegInfo *ri, +uint64_t value) +{ +ARMCPU *cpu =env_archcpu (env); + +trace_arm_gt_cntvoff_write (value); +raw_write (env, ri, value); +gt_recalc_timer (cpu,GTIMER_VIRT ); +} +static void gt_hyp_timer_reset (CPUARMState *env,const ARMCPRegInfo *ri) {gt_timer_reset (env, ri,GTIMER_HYP );@@ -2976,6 +2977,7 @@ static void gt_hyp_ctl_write(CPUARMState *env, const ARMCPRegInfo *ri, {gt_ctl_write (env, ri,GTIMER_HYP , value); } +#endif /* !CONFIG_USER_ONLY && CONFIG_TCG */ static void gt_sec_timer_reset (CPUARMState *env,const ARMCPRegInfo *ri) {
PATCH v3 6/19 target/arm: Move Makefile variable restricted to CONFIG_TCG
In reply to Philippe Mathieu-DaudéSimple code movement which simplifies next commits.
--- target/arm/Makefile.objs | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-)
target/arm/Makefile.objs +6 -1
@@ -1,4 +1,3 @@ -obj-$(CONFIG_TCG) += arm-semi.o obj-y += helper.o vfp_helper.o obj-y += cpu.o gdbstub.o obj-$(TARGET_AARCH64) += cpu64.o gdbstub64.o
@@ -56,6 +55,12 @@ target/arm/translate.o: target/arm/decode-a32-uncond.inc.c target/arm/translate.o: target/arm/decode-t32.inc.c target/arm/translate.o: target/arm/decode-t16.inc.c +ifeq ($(CONFIG_TCG),y) + +obj-y += arm-semi.o + +endif # CONFIG_TCG + obj-y += tlb_helper.o debug_helper.o obj-y += translate.o op_helper.o obj-y += crypto_helper.o
Signature · 1 line
2.21.1
PATCH v3 7/19 target/arm: Make cpu_register() available for other files
In reply to Philippe Mathieu-DaudéFrom: Thomas Huth <[email protected]>
Make cpu_register() (renamed to arm_cpu_register()) available from internals.h so we can register CPUs also from other files in the future.
Message-ID: <[email protected]>
--- target/arm/cpu-qom.h | 9 ++++++++- target/arm/cpu.c | 10 ++-------- target/arm/cpu64.c | 8 +------- 3 files changed, 11 insertions(+), 16 deletions(-)
target/arm/cpu-qom.h +8 -1
@@ -35,7 +35,14 @@ struct arm_boot_info;#define TYPE_ARM_MAX_CPU "max-" TYPE_ARM_CPU -typedef struct ARMCPUInfo ARMCPUInfo ; +typedef struct ARMCPUInfo { +const char *name; +void (*initfn)(Object *obj); +void (*class_init)(ObjectClass *oc,void *data); +}ARMCPUInfo ; + +void arm_cpu_register (const ARMCPUInfo *info); +void aarch64_cpu_register (const ARMCPUInfo *info);/** * ARMCPUClass:
target/arm/cpu.c +2 -8
@@ -2698,12 +2698,6 @@ static void arm_max_initfn(Object *obj)#endif /* !defined(CONFIG_USER_ONLY) || !defined(TARGET_AARCH64) */ -struct ARMCPUInfo { -const char *name; -void (*initfn)(Object *obj); -void (*class_init)(ObjectClass *oc,void *data); -}; -static const ARMCPUInfo arm_cpus[] = { #if !defined(CONFIG_USER_ONLY) || !defined(TARGET_AARCH64) { .name = "arm926", .initfn = arm926_initfn },
@@ -2869,7 +2863,7 @@ static void cpu_register_class_init(ObjectClass *oc, void *data) acc->info = data; } -static void cpu_register (const ARMCPUInfo *info) +void arm_cpu_register (const ARMCPUInfo *info) {TypeInfo type_info = { .parent =TYPE_ARM_CPU ,
@@ -2910,7 +2904,7 @@ static void arm_cpu_register_types(void)type_register_static (&idau_interface_type_info);while (info->name) { -cpu_register (info); +arm_cpu_register (info); info++; }
target/arm/cpu64.c +1 -7
@@ -728,12 +728,6 @@ static void aarch64_max_initfn(Object *obj) cpu_max_set_sve_max_vq, NULL, NULL, &error_fatal); } -struct ARMCPUInfo { -const char *name; -void (*initfn)(Object *obj); -void (*class_init)(ObjectClass *oc,void *data); -}; -static const ARMCPUInfo aarch64_cpus[] = { { .name ="cortex-a57" , .initfn = aarch64_a57_initfn }, { .name ="cortex-a53" , .initfn = aarch64_a53_initfn },
@@ -816,7 +810,7 @@ static void cpu_register_class_init(ObjectClass *oc, void *data) acc->info = data; } -static void aarch64_cpu_register (const ARMCPUInfo *info) +void aarch64_cpu_register (const ARMCPUInfo *info) {TypeInfo type_info = { .parent =TYPE_AARCH64_CPU ,
Signature · 1 line
2.21.1
Re: [PATCH v3 07/19] target/arm: Make cpu_register() available for other files
Quoted 9 lines · Philippe Mathieu-Daudé
From: Thomas Huth <[email protected]>
Make
cpu_register()(renamed toarm_cpu_register()) available frominternals.hso we can register CPUs also from other files in the future.Signed-off-by Thomas Huth <[email protected]>Reviewed-by Richard Henderson <[email protected]>Reviewed-by Eric Auger <[email protected]>
Quoted 8 lines
Message-ID: <[email protected]>
[PMD: Split Thomas's patch in two: set_feature (earlier), cpu_register]Signed-off-by Philippe Mathieu-Daudé <[email protected]>--- target/arm/cpu-qom.h | 9 ++++++++- target/arm/cpu.c | 10 ++-------- target/arm/cpu64.c | 8 +------- 3 files changed, 11 insertions(+), 16 deletions(-)
r~
PATCH v3 8/19 target/arm: Add semihosting stub to allow building without TCG
In reply to Philippe Mathieu-DaudéSemihosting requires TCG. When configured with --disable-tcg, the build fails because the 'do_arm_semihosting' is missing. Instead of adding more few more #ifdeffery to the helper code, add a stub.
--- target/arm/arm-semi-stub.c | 13 +++++++++++++ target/arm/Makefile.objs | 3 ++- 2 files changed, 15 insertions(+), 1 deletion(-) create mode 100644 target/arm/arm-semi-stub.c
target/arm/arm-semi-stub.c new file +13 -0
@@ -0,0 +1,13 @@ +/* +* Arm "Angel" semihosting syscalls stubs +* +* SPDX-License-Identifier: GPL-2.0-or-later +*/ +#include "qemu/osdep.h" +#include "cpu.h" +#include "hw/semihosting/semihost.h" + +target_ulong do_arm_semihosting (CPUARMState *env) +{ +abort (); +}
target/arm/Makefile.objs +2 -1
@@ -57,7 +57,8 @@ target/arm/translate.o: target/arm/decode-t16.inc.c ifeq ($(CONFIG_TCG),y) -obj-y += arm-semi.o +obj-$(CONFIG_SEMIHOSTING) += arm-semi.o +obj-$(call lnot,$(CONFIG_SEMIHOSTING)) += arm-semi-stub.o endif # CONFIG_TCG
Signature · 1 line
2.21.1
Re: [PATCH v3 08/19] target/arm: Add semihosting stub to allow building without TCG
Quoted 3 lines · Philippe Mathieu-Daudé
Semihosting requires TCG. When configured with --disable-tcg, the build fails because the '
do_arm_semihosting' is missing. Instead of adding more few more #ifdeffery to the helper code, add a stub.
...
target/arm/Makefile.objs target/arm/translate.o: target/arm/decode-t16.inc.c · line 63
Quoted 7 lines
ifeq ($(CONFIG_TCG),y)
target/arm/Makefile.objs +2
-1-obj-y += arm-semi.o +obj-$(CONFIG_SEMIHOSTING) += arm-semi.o +obj-$(call lnot,$(CONFIG_SEMIHOSTING)) += arm-semi-stub.o endif # CONFIG_TCG
This code doesn't match the comment.
Why isn't this
obj-$(call land,$(CONFIG_TCG),$(CONFIG_SEMIHOSTING)) += arm-semi.o obj-$(call lnot,$(call land ...)) += arm-semi-stub.o
r~
PATCH v3 9/19 target/arm: Move ARM_V7M Kconfig from hw/ to target/
In reply to Philippe Mathieu-DaudéARM_V7M is a concept tied to the architecture. Move it to the target/arm/ directory to keep the hardware/architecture separation clearer.
--- hw/arm/Kconfig | 3 --- target/Kconfig | 2 +- target/arm/Kconfig | 2 ++ 3 files changed, 3 insertions(+), 4 deletions(-) create mode 100644 target/arm/Kconfig
hw/arm/Kconfig +0 -3
@@ -285,9 +285,6 @@ config ZYNQ select XILINX_SPIPS select ZYNQ_DEVCFG -config ARM_V7M - bool - config ALLWINNER_A10 bool select AHCI
target/Kconfig +1 -1
@@ -1 +1 @@ - +source arm/Kconfig
target/arm/Kconfig new file +2 -0
@@ -0,0 +1,2 @@ +config ARM_V7M + bool
Signature · 1 line
2.21.1
Re: [PATCH v3 09/19] target/arm: Move ARM_V7M Kconfig from hw/ to target/
Quoted 11 lines · Philippe Mathieu-Daudé
ARM_V7Mis a concept tied to the architecture. Move it to the target/arm/ directory to keep the hardware/architecture separation clearer.Signed-off-by Philippe Mathieu-Daudé <[email protected]>--- hw/arm/Kconfig | 3 --- target/Kconfig | 2 +- target/arm/Kconfig | 2 ++ 3 files changed, 3 insertions(+), 4 deletions(-) create mode 100644 target/arm/Kconfig
r~
PATCH v3 10/19 target/arm: Restrict ARMv4 cpus to TCG accel
In reply to Philippe Mathieu-DaudéKVM requires a cpu based on (at least) the ARMv7 architecture.
Only enable the following ARMv4 CPUs when TCG is available:
- StrongARM (SA1100/1110)
- OMAP1510 (TI925T)
--- default-configs/arm-softmmu.mak | 2 - target/arm/cpu.c | 33 ----------------- target/arm/cpu_v4.c | 65 +++++++++++++++++++++++++++++++++ hw/arm/Kconfig | 2 + target/arm/Kconfig | 4 ++ target/arm/Makefile.objs | 2 + 6 files changed, 73 insertions(+), 35 deletions(-) create mode 100644 target/arm/cpu_v4.c
default-configs/arm-softmmu.mak +0 -2
@@ -17,8 +17,6 @@ CONFIG_INTEGRATOR=y CONFIG_FSL_IMX31=y CONFIG_MUSICPAL=y CONFIG_MUSCA=y -CONFIG_CHEETAH=y -CONFIG_SX1=y CONFIG_NSERIES=y CONFIG_STELLARIS=y CONFIG_REALVIEW=y
target/arm/cpu.c +0 -33
@@ -2459,36 +2459,6 @@ static void cortex_a15_initfn(Object *obj)define_arm_cp_regs (cpu, cortexa15_cp_reginfo); } -static void ti925t_initfn (Object *obj) -{ -ARMCPU *cpu =ARM_CPU (obj); -set_feature (&cpu->env,ARM_FEATURE_V4T ); -set_feature (&cpu->env,ARM_FEATURE_OMAPCP ); - cpu->midr =ARM_CPUID_TI925T ; - cpu->ctr =0x5109149 ; - cpu->reset_sctlr =0x00000070 ; -} - -static void sa1100_initfn (Object *obj) -{ -ARMCPU *cpu =ARM_CPU (obj); - - cpu->dtb_compatible ="intel,sa1100" ; -set_feature (&cpu->env,ARM_FEATURE_STRONGARM ); -set_feature (&cpu->env,ARM_FEATURE_DUMMY_C15_REGS ); - cpu->midr =0x4401A11B ; - cpu->reset_sctlr =0x00000070 ; -} - -static void sa1110_initfn (Object *obj) -{ -ARMCPU *cpu =ARM_CPU (obj); -set_feature (&cpu->env,ARM_FEATURE_STRONGARM ); -set_feature (&cpu->env,ARM_FEATURE_DUMMY_C15_REGS ); - cpu->midr =0x6901B119 ; - cpu->reset_sctlr =0x00000070 ; -} -static void pxa250_initfn (Object *obj) {ARMCPU *cpu =ARM_CPU (obj);
@@ -2727,9 +2697,6 @@ static const ARMCPUInfo arm_cpus[] = { { .name = "cortex-a8", .initfn = cortex_a8_initfn }, { .name = "cortex-a9", .initfn = cortex_a9_initfn }, { .name = "cortex-a15", .initfn = cortex_a15_initfn }, - { .name = "ti925t", .initfn = ti925t_initfn }, - { .name = "sa1100", .initfn = sa1100_initfn }, - { .name = "sa1110", .initfn = sa1110_initfn }, { .name = "pxa250", .initfn = pxa250_initfn }, { .name = "pxa255", .initfn = pxa255_initfn }, { .name = "pxa260", .initfn = pxa260_initfn },
target/arm/cpu_v4.c new file +65 -0
65 lines not on this page · raw message
hw/arm/Kconfig +2 -0
@@ -28,6 +28,7 @@ config ARM_VIRT config CHEETAH bool + select ARM_V4 select OMAP select TSC210X
@@ -242,6 +243,7 @@ config COLLIE config SX1 bool + select ARM_V4 select OMAP config VERSATILE
target/arm/Kconfig +4 -0
@@ -1,2 +1,6 @@ +config ARM_V4 + depends on TCG + bool + config ARM_V7M bool
target/arm/Makefile.objs +2 -0
@@ -68,6 +68,8 @@ obj-y += crypto_helper.o obj-y += iwmmxt_helper.o vec_helper.o neon_helper.o obj-y += m_helper.o +obj-$(CONFIG_ARM_V4) += cpu_v4.o + obj-$(CONFIG_SOFTMMU) += psci.o obj-$(TARGET_AARCH64) += translate-a64.o helper-a64.o
Signature · 1 line
2.21.1
Re: [PATCH v3 10/19] target/arm: Restrict ARMv4 cpus to TCG accel
Quoted 6 lines · Philippe Mathieu-Daudé
target/arm/cpu_v4.c new file +6
-0+static const ARMCPUInfo arm_v4_cpus[] = { + { .name ="ti925t" , .initfn = ti925t_initfn }, + { .name ="sa1100" , .initfn = sa1100_initfn }, + { .name ="sa1110" , .initfn = sa1110_initfn }, + { .name =NULL } +};
target/arm/cpu_v4.c line 61
Quoted 10 lines
target/arm/cpu_v4.c new file +10
-0+ +static void arm_v4_cpu_register_types (void ) +{ +const ARMCPUInfo *info = arm_v4_cpus; + +while (info->name) { +arm_cpu_register (info); + info++; + } +}
I much prefer ARRAY_SIZE() to sentinels.
I know the existing code make much use of them,
but we don't need to replicate that here.
r~
Richard Henderson
Reviewed-byRe: [PATCH v3 10/19] target/arm: Restrict ARMv4 cpus to TCG accel
Quoted 3 lines · Richard Henderson
I much prefer
ARRAY_SIZE()to sentinels.
I know the existing code make much use of them,
but we don't need to replicate that here.
... but otherwise,
r~
Re: [PATCH v3 10/19] target/arm: Restrict ARMv4 cpus to TCG accel
In reply to Philippe Mathieu-DaudéQuoted 7 lines · Philippe Mathieu-Daudé
KVM requires a cpu based on (at least) the ARMv7 architecture.
Only enable the following ARMv4 CPUs when TCG is available:
- StrongARM (SA1100/1110)
- OMAP1510 (TI925T)
I missed to explain, the point of this Kconfig granularity is on a KVM only build, the TCG-only CPUs can't be default-selected, so most of their devices are not pulled in.
Instead at the end the KVM-only binary only contains the devices required to run the Cortex-A machines.
Quoted 13 lines
default-configs/arm-softmmu.mak +0
-2@@ -17,8 +17,6 @@ CONFIG_INTEGRATOR=y CONFIG_FSL_IMX31=y CONFIG_MUSICPAL=y CONFIG_MUSCA=y -CONFIG_CHEETAH=y -CONFIG_SX1=y CONFIG_NSERIES=y CONFIG_STELLARIS=y CONFIG_REALVIEW=y
[...]
Quoted 31 lines
hw/arm/Kconfig +2
-0@@ -28,6 +28,7 @@ config ARM_VIRT config CHEETAH bool + select ARM_V4 select OMAP select TSC210X@@ -242,6 +243,7 @@ config COLLIE config SX1 bool + select ARM_V4 select OMAP config VERSATILEtarget/arm/Kconfig +4
-0@@ -1,2 +1,6 @@ +config ARM_V4 + depends on TCG + bool + config ARM_V7M bool
PATCH v3 11/19 target/arm: Restrict ARMv5 cpus to TCG accel
In reply to Philippe Mathieu-DaudéKVM requires a cpu based on (at least) the ARMv7 architecture.
Only enable the following ARMv5 CPUs when TCG is available:
- ARM926
- ARM946
- ARM1026
- XScale (PXA250/255/260/261/262/270)
--- default-configs/arm-softmmu.mak | 12 -- target/arm/cpu.c | 234 ---------------------------- target/arm/cpu_v5.c | 266 ++++++++++++++++++++++++++++++++ hw/arm/Kconfig | 7 + target/arm/Kconfig | 4 + target/arm/Makefile.objs | 1 + 6 files changed, 278 insertions(+), 246 deletions(-) create mode 100644 target/arm/cpu_v5.c
default-configs/arm-softmmu.mak +0 -12
@@ -13,32 +13,20 @@ CONFIG_ARM_VIRT=y CONFIG_CUBIEBOARD=y CONFIG_EXYNOS4=y CONFIG_HIGHBANK=y -CONFIG_INTEGRATOR=y CONFIG_FSL_IMX31=y -CONFIG_MUSICPAL=y CONFIG_MUSCA=y CONFIG_NSERIES=y CONFIG_STELLARIS=y CONFIG_REALVIEW=y -CONFIG_VERSATILE=y CONFIG_VEXPRESS=y CONFIG_ZYNQ=y -CONFIG_MAINSTONE=y -CONFIG_GUMSTIX=y -CONFIG_SPITZ=y -CONFIG_TOSA=y -CONFIG_Z2=y -CONFIG_COLLIE=y -CONFIG_ASPEED_SOC=y CONFIG_NETDUINO2=y CONFIG_NETDUINOPLUS2=y CONFIG_MPS2=y CONFIG_RASPI=y -CONFIG_DIGIC=y CONFIG_SABRELITE=y CONFIG_EMCRAFT_SF2=y CONFIG_MICROBIT=y -CONFIG_FSL_IMX25=y CONFIG_FSL_IMX7=y CONFIG_FSL_IMX6UL=y CONFIG_ALLWINNER_H3=y
target/arm/cpu.c +0 -234
258 lines not on this page · raw message
target/arm/cpu_v5.c new file +266 -0
266 lines not on this page · raw message
hw/arm/Kconfig +7 -0
@@ -38,6 +38,7 @@ config CUBIEBOARD config DIGIC bool + select ARM_V5 select PTIMER select PFLASH_CFI02
@@ -67,6 +68,7 @@ config HIGHBANK config INTEGRATOR bool + select ARM_V5 select ARM_TIMER select INTEGRATOR_DEBUG select PL011 # UART
@@ -93,6 +95,7 @@ config MUSCA config MUSICPAL bool + select ARM_V5 select BITBANG_I2C select MARVELL_88W8618 select PTIMER
@@ -132,6 +135,7 @@ config OMAP config PXA2XX bool + select ARM_V5 select FRAMEBUFFER select I2C select SERIAL
@@ -248,6 +252,7 @@ config SX1 config VERSATILE bool + select ARM_V5 select ARM_TIMER # sp804 select PFLASH_CFI01 select LSI_SCSI_PCI
@@ -354,6 +359,7 @@ config XLNX_VERSAL config FSL_IMX25 bool + select ARM_V5 select IMX select IMX_FEC select IMX_I2C
@@ -376,6 +382,7 @@ config FSL_IMX6 config ASPEED_SOC bool + select ARM_V5 select DS1338 select FTGMAC100 select I2C
target/arm/Kconfig +4 -0
@@ -2,5 +2,9 @@ config ARM_V4 depends on TCG bool +config ARM_V5 + depends on TCG + bool + config ARM_V7M bool
target/arm/Makefile.objs +1 -0
@@ -69,6 +69,7 @@ obj-y += iwmmxt_helper.o vec_helper.o neon_helper.o obj-y += m_helper.o obj-$(CONFIG_ARM_V4) += cpu_v4.o +obj-$(CONFIG_ARM_V5) += cpu_v5.o obj-$(CONFIG_SOFTMMU) += psci.o
Signature · 1 line
2.21.1
Re: [PATCH v3 11/19] target/arm: Restrict ARMv5 cpus to TCG accel
target/arm/cpu_v5.c line 262
Quoted 9 lines · Philippe Mathieu-Daudé
target/arm/cpu_v5.c new file +9
-0+static void arm_v5_cpu_register_types (void ) +{ +const ARMCPUInfo *info = arm_v5_cpus; + +while (info->name) { +arm_cpu_register (info); + info++; + } +}
Similarly wrt ARRAY_SIZE. Otherwise,
r~
PATCH v3 12/19 target/arm: Restrict ARMv6 cpus to TCG accel
In reply to Philippe Mathieu-DaudéKVM requires a cpu based on (at least) the ARMv7 architecture.
Only enable the following ARMv6 CPUs when TCG is available:
- ARM1136
- ARM1176
- ARM11MPCore
- Cortex-M0
--- default-configs/arm-softmmu.mak | 2 - target/arm/cpu.c | 137 ------------------------- target/arm/cpu_v6.c | 171 ++++++++++++++++++++++++++++++++ hw/arm/Kconfig | 2 + target/arm/Kconfig | 4 + target/arm/Makefile.objs | 1 + 6 files changed, 178 insertions(+), 139 deletions(-) create mode 100644 target/arm/cpu_v6.c
default-configs/arm-softmmu.mak +0 -2
@@ -13,9 +13,7 @@ CONFIG_ARM_VIRT=y CONFIG_CUBIEBOARD=y CONFIG_EXYNOS4=y CONFIG_HIGHBANK=y -CONFIG_FSL_IMX31=y CONFIG_MUSCA=y -CONFIG_NSERIES=y CONFIG_STELLARIS=y CONFIG_REALVIEW=y CONFIG_VEXPRESS=y
target/arm/cpu.c +0 -137
149 lines not on this page · raw message
target/arm/cpu_v6.c new file +171 -0
171 lines not on this page · raw message
hw/arm/Kconfig +2 -0
@@ -113,6 +113,7 @@ config NETDUINOPLUS2 config NSERIES bool + select ARM_V6 select OMAP select TMP105 # tempature sensor select BLIZZARD # LCD/TV controller
@@ -367,6 +368,7 @@ config FSL_IMX25 config FSL_IMX31 bool + select ARM_V6 select SERIAL select IMX select IMX_I2C
target/arm/Kconfig +4 -0
@@ -6,5 +6,9 @@ config ARM_V5 depends on TCG bool +config ARM_V6 + depends on TCG + bool + config ARM_V7M bool
target/arm/Makefile.objs +1 -0
@@ -70,6 +70,7 @@ obj-y += m_helper.o obj-$(CONFIG_ARM_V4) += cpu_v4.o obj-$(CONFIG_ARM_V5) += cpu_v5.o +obj-$(CONFIG_ARM_V6) += cpu_v6.o obj-$(CONFIG_SOFTMMU) += psci.o
Signature · 1 line
2.21.1
Re: [PATCH v3 12/19] target/arm: Restrict ARMv6 cpus to TCG accel
target/arm/cpu_v6.c line 167
Quoted 9 lines · Philippe Mathieu-Daudé
target/arm/cpu_v6.c new file +9
-0+static void arm_v6_cpu_register_types (void ) +{ +const ARMCPUInfo *info = arm_v6_cpus; + +while (info->name) { +arm_cpu_register (info); + info++; + } +}
Likewise wrt ARRAY_SIZE, otherwise,
r~
PATCH v3 13/19 target/arm: Restrict ARMv7 R-profile cpus to TCG accel
In reply to Philippe Mathieu-DaudéA KVM-only build won't be able to run R-profile cpus.
Only enable the following ARMv7 R-Profile CPUs when TCG is available:
- Cortex-R5
- Cortex-R5F
--- default-configs/aarch64-softmmu.mak | 1 - target/arm/cpu.c | 51 ------------------ target/arm/cpu_v7r.c | 83 +++++++++++++++++++++++++++++ hw/arm/Kconfig | 1 + target/arm/Kconfig | 4 ++ target/arm/Makefile.objs | 1 + 6 files changed, 89 insertions(+), 52 deletions(-) create mode 100644 target/arm/cpu_v7r.c
default-configs/aarch64-softmmu.mak +0 -1
@@ -3,6 +3,5 @@ # We support all the 32 bit boards so need all their config include arm-softmmu.mak -CONFIG_XLNX_ZYNQMP_ARM=y CONFIG_XLNX_VERSAL=y CONFIG_SBSA_REF=y
target/arm/cpu.c +0 -51
63 lines not on this page · raw message
target/arm/cpu_v7r.c new file +83 -0
83 lines not on this page · raw message
hw/arm/Kconfig +1 -0
@@ -340,6 +340,7 @@ config XLNX_ZYNQMP_ARM bool select AHCI select ARM_GIC + select ARM_V7R select CADENCE select DDC select DPCD
target/arm/Kconfig +4 -0
@@ -10,5 +10,9 @@ config ARM_V6 depends on TCG bool +config ARM_V7R + depends on TCG + bool + config ARM_V7M bool
target/arm/Makefile.objs +1 -0
@@ -71,6 +71,7 @@ obj-y += m_helper.o obj-$(CONFIG_ARM_V4) += cpu_v4.o obj-$(CONFIG_ARM_V5) += cpu_v5.o obj-$(CONFIG_ARM_V6) += cpu_v6.o +obj-$(CONFIG_ARM_V7R) += cpu_v7r.o obj-$(CONFIG_SOFTMMU) += psci.o
Signature · 1 line
2.21.1
Re: [PATCH v3 13/19] target/arm: Restrict ARMv7 R-profile cpus to TCG accel
target/arm/cpu_v7r.c line 79
Quoted 9 lines · Philippe Mathieu-Daudé
target/arm/cpu_v7r.c new file +9
-0+static void arm_v7r_cpu_register_types (void ) +{ +const ARMCPUInfo *info = arm_v7r_cpus; + +while (info->name) { +arm_cpu_register (info); + info++; + } +}
Likewise wrt ARRAY_SIZE, otherwise,
r~
PATCH v3 14/19 target/arm: Restrict ARMv7 M-profile cpus to TCG accel
In reply to Philippe Mathieu-DaudéA KVM-only build won't be able to run M-profile cpus.
Only enable the following ARMv7 M-Profile CPUs when TCG is available:
- Cortex-M3
- Cortex-M4
- Cortex-M33
--- default-configs/arm-softmmu.mak | 8 -- target/arm/cpu.c | 176 --------------------------- target/arm/cpu_v7m.c | 207 ++++++++++++++++++++++++++++++++ target/arm/Kconfig | 1 + target/arm/Makefile.objs | 1 + 5 files changed, 209 insertions(+), 184 deletions(-) create mode 100644 target/arm/cpu_v7m.c
default-configs/arm-softmmu.mak +0 -8
@@ -12,19 +12,11 @@ CONFIG_ARM_V7M=y CONFIG_ARM_VIRT=y CONFIG_CUBIEBOARD=y CONFIG_EXYNOS4=y -CONFIG_HIGHBANK=y -CONFIG_MUSCA=y -CONFIG_STELLARIS=y CONFIG_REALVIEW=y CONFIG_VEXPRESS=y CONFIG_ZYNQ=y -CONFIG_NETDUINO2=y -CONFIG_NETDUINOPLUS2=y -CONFIG_MPS2=y CONFIG_RASPI=y CONFIG_SABRELITE=y -CONFIG_EMCRAFT_SF2=y -CONFIG_MICROBIT=y CONFIG_FSL_IMX7=y CONFIG_FSL_IMX6UL=y CONFIG_ALLWINNER_H3=y
target/arm/cpu.c +0 -176
194 lines not on this page · raw message
target/arm/cpu_v7m.c new file +207 -0
207 lines not on this page · raw message
target/arm/Kconfig +1 -0
@@ -15,4 +15,5 @@ config ARM_V7R bool config ARM_V7M + depends on TCG bool
target/arm/Makefile.objs +1 -0
@@ -72,6 +72,7 @@ obj-$(CONFIG_ARM_V4) += cpu_v4.o obj-$(CONFIG_ARM_V5) += cpu_v5.o obj-$(CONFIG_ARM_V6) += cpu_v6.o obj-$(CONFIG_ARM_V7R) += cpu_v7r.o +obj-$(CONFIG_ARM_V7M) += cpu_v7m.o obj-$(CONFIG_SOFTMMU) += psci.o
Signature · 1 line
2.21.1
Re: [PATCH v3 14/19] target/arm: Restrict ARMv7 M-profile cpus to TCG accel
target/arm/cpu_v7m.c line 203
Quoted 9 lines · Philippe Mathieu-Daudé
target/arm/cpu_v7m.c new file +9
-0+static void arm_v7m_cpu_register_types (void ) +{ +const ARMCPUInfo *info = arm_v7m_cpus; + +while (info->name) { +arm_cpu_register (info); + info++; + } +}
Likewise wrt ARRAY_SIZE, otherwise,
r~
PATCH v3 15/19 target/arm: Make m_helper.c optional via CONFIG_ARM_V7M
In reply to Philippe Mathieu-DaudéFrom: Thomas Huth <[email protected]>
We've already got the CONFIG_ARM_V7M switch, but it currently can not be disabled yet. The m_helper.c code should not be compiled into the binary if the switch is not enabled. We also have to provide some stubs in a separate file to make sure that we still can link the other code without CONFIG_ARM_V7M.
Message-Id: <[email protected]> [PMD: add write_v7m_exception() stub when not using TCG,
remove CONFIG_ARM_V7M=y in default-configs/arm-softmmu.mak]
--- default-configs/arm-softmmu.mak | 6 ---- target/arm/cpu.h | 7 ++++ target/arm/m_helper-stub.c | 59 +++++++++++++++++++++++++++++++++ target/arm/Makefile.objs | 3 +- 4 files changed, 68 insertions(+), 7 deletions(-) create mode 100644 target/arm/m_helper-stub.c
default-configs/arm-softmmu.mak +0 -6
@@ -1,11 +1,5 @@ # Default configuration for arm-softmmu -# CONFIG_SEMIHOSTING is always required on this architecture -CONFIG_SEMIHOSTING=y - -# TODO: ARM_V7M is currently always required - make this more flexible! -CONFIG_ARM_V7M=y - # CONFIG_PCI_DEVICES=n # CONFIG_TEST_DEVICES=n
target/arm/cpu.h +7 -0
@@ -1278,7 +1278,14 @@ void pmu_init(ARMCPU *cpu);/* Write a new value to v7m.exception, thus transitioning into or out * of Handler mode; this may result in a change of active stack pointer. */ +#if !defined(CONFIG_TCG ) +static inline void write_v7m_exception (CPUARMState *env,uint32_t new_exc) +{ +g_assert_not_reached (); +} +#else void write_v7m_exception (CPUARMState *env,uint32_t new_exc); +#endif /* Map EL and handler into a PSTATE_MODE. */ static inline unsigned int aarch64_pstate_mode (unsigned int el,bool handler)
target/arm/m_helper-stub.c new file +59 -0
59 lines not on this page · raw message
target/arm/Makefile.objs +2 -1
@@ -66,7 +66,8 @@ obj-y += tlb_helper.o debug_helper.o obj-y += translate.o op_helper.o obj-y += crypto_helper.o obj-y += iwmmxt_helper.o vec_helper.o neon_helper.o -obj-y += m_helper.o +obj-$(CONFIG_ARM_V7M) += m_helper.o +obj-$(call lnot,$(CONFIG_ARM_V7M)) += m_helper-stub.o obj-$(CONFIG_ARM_V4) += cpu_v4.o obj-$(CONFIG_ARM_V5) += cpu_v5.o
Signature · 1 line
2.21.1
Re: [PATCH v3 15/19] target/arm: Make m_helper.c optional via CONFIG_ARM_V7M
default-configs/arm-softmmu.mak line 4
Quoted 5 lines · Philippe Mathieu-Daudé
default-configs/arm-softmmu.mak +0
-2@@ -1,11 +1,5 @@ # Default configuration for arm-softmmu -# CONFIG_SEMIHOSTING is always required on this architecture -CONFIG_SEMIHOSTING=y
This doesn't belong to this patch. Otherwise,
r~
PATCH v3 16/19 target/arm: Do not build TCG objects when TCG is off
In reply to Philippe Mathieu-DaudéFrom: Samuel Ortiz <[email protected]>
We can now safely turn all TCG dependent build off when CONFIG_TCG is off. This allows building ARM binaries with --disable-tcg.
--- target/arm/Makefile.objs | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
target/arm/Makefile.objs +2 -2
@@ -60,8 +60,6 @@ ifeq ($(CONFIG_TCG),y) obj-$(CONFIG_SEMIHOSTING) += arm-semi.o obj-$(call lnot,$(CONFIG_SEMIHOSTING)) += arm-semi-stub.o -endif # CONFIG_TCG - obj-y += tlb_helper.o debug_helper.o obj-y += translate.o op_helper.o obj-y += crypto_helper.o
@@ -80,3 +78,5 @@ obj-$(CONFIG_SOFTMMU) += psci.o obj-$(TARGET_AARCH64) += translate-a64.o helper-a64.o obj-$(TARGET_AARCH64) += translate-sve.o sve_helper.o obj-$(TARGET_AARCH64) += pauth_helper.o + +endif # CONFIG_TCG
Signature · 1 line
2.21.1
PATCH v3 17/19 hw/arm: Automatically select the 'virt' machine on KVM
In reply to Philippe Mathieu-DaudéWhen building a KVM-only QEMU, the 'virt' machine is a good default :)
--- hw/arm/Kconfig | 1 + 1 file changed, 1 insertion(+)
hw/arm/Kconfig +1 -0
@@ -1,5 +1,6 @@ config ARM_VIRT bool + default y if KVM imply PCI_DEVICES imply TEST_DEVICES imply VFIO_AMD_XGBE
Signature · 1 line
2.21.1
Re: [PATCH v3 17/19] hw/arm: Automatically select the 'virt' machine on KVM
Quoted 14 lines · Philippe Mathieu-Daudé
When building a KVM-only QEMU, the 'virt' machine is a good default :)
Signed-off-by Philippe Mathieu-Daudé <[email protected]>--- hw/arm/Kconfig | 1 + 1 file changed, 1 insertion(+)hw/arm/Kconfig +0
-0
hw/arm/Kconfig line 6
Quoted 6 lines
hw/arm/Kconfig +1
-0@@ -1,5 +1,6 @@ config ARM_VIRT bool + default y if KVM imply PCI_DEVICES imply TEST_DEVICES imply VFIO_AMD_XGBE
Likewise SBSA_REF? Otherwise, what is this for?
Did you remove ARM_VIRT from default-config/*?
r~
Re: [PATCH v3 17/19] hw/arm: Automatically select the 'virt' machine on KVM
Quoted 9 lines · Richard Henderson
Quoted 8 lines · Philippe Mathieu-Daudé
When building a KVM-only QEMU, the 'virt' machine is a good default :)
Signed-off-by Philippe Mathieu-Daudé <[email protected]>--- hw/arm/Kconfig | 1 + 1 file changed, 1 insertion(+)
Quoted 14 lines
hw/arm/Kconfig line 6
Quoted 12 lines
hw/arm/Kconfig +1
-0@@ -1,5 +1,6 @@ config ARM_VIRT bool + default y if KVM imply PCI_DEVICES imply TEST_DEVICES imply VFIO_AMD_XGBELikewise
SBSA_REF?
OK.
Quoted 2 lines
Otherwise, what is this for?
Did you removeARM_VIRTfrom default-config/*?
This is to use custom config (and easily test by
blowing default-config/).
Quoted 4 lines
r~
Re: [PATCH v3 17/19] hw/arm: Automatically select the 'virt' machine on KVM
In reply to Philippe Mathieu-DaudéQuoted 14 lines · Philippe Mathieu-Daudé
When building a KVM-only QEMU, the 'virt' machine is a good default :)
Signed-off-by Philippe Mathieu-Daudé <[email protected]>--- hw/arm/Kconfig | 1 + 1 file changed, 1 insertion(+)hw/arm/Kconfig +0
-0
hw/arm/Kconfig line 6
Quoted 6 lines
hw/arm/Kconfig +1
-0@@ -1,5 +1,6 @@ config ARM_VIRT bool + default y if KVM imply PCI_DEVICES imply TEST_DEVICES imply VFIO_AMD_XGBE
What does this actually do ? Why should the choice of accelerator affect what boards we pull in by default? I can see why you'd want to disable boards that only work with accelerators we don't enable, ie don't build TCG-only boards unless CONFIG_TCG, but this is the other way around...
thanks
-- PMM
Re: [PATCH v3 17/19] hw/arm: Automatically select the 'virt' machine on KVM
Quoted 11 lines · Peter Maydell
Quoted 9 lines · Philippe Mathieu-Daudé
When building a KVM-only QEMU, the 'virt' machine is a good default :)
Signed-off-by Philippe Mathieu-Daudé <[email protected]>--- hw/arm/Kconfig | 1 + 1 file changed, 1 insertion(+)
Quoted 14 lines
hw/arm/Kconfig line 6
Quoted 11 lines
hw/arm/Kconfig +1
-0@@ -1,5 +1,6 @@ config ARM_VIRT bool + default y if KVM imply PCI_DEVICES imply TEST_DEVICES imply VFIO_AMD_XGBEWhat does this actually do ? Why should the choice of accelerator affect what boards we pull in by default?
Put another way, our current default is "build everything", so "default y if ..." on a board is a no-op...
-- PMM
Re: [PATCH v3 17/19] hw/arm: Automatically select the 'virt' machine on KVM
Quoted 27 lines · Peter Maydell
Quoted 11 lines · Peter Maydell
Quoted 9 lines · Philippe Mathieu-Daudé
When building a KVM-only QEMU, the 'virt' machine is a good default :)
Signed-off-by Philippe Mathieu-Daudé <[email protected]>--- hw/arm/Kconfig | 1 + 1 file changed, 1 insertion(+)Quoted 14 lines
hw/arm/Kconfig line 6
Quoted 11 lines
hw/arm/Kconfig +1
-0@@ -1,5 +1,6 @@ config ARM_VIRT bool + default y if KVM imply PCI_DEVICES imply TEST_DEVICES imply VFIO_AMD_XGBEWhat does this actually do ? Why should the choice of accelerator affect what boards we pull in by default?
Quoted 2 lines
Put another way, our current default is "build everything", so "default y if ..." on a board is a no-op...
Yes, the problem if I don't restrict to KVM, when using the Xen accelerator odd things occur
(using configure --enable-xen --disable-tcg --disable-kvm):
Compiling C object libqemu-i386-softmmu.fa.p/hw_cpu_a15mpcore.c.o hw/cpu/a15mpcore.c:28:10: fatal error: kvm_arm.h: No such file or directory
We can't have the 'virt' machine automatically selected if Xen is the only accelerator...
I'm looking for a simple way to avoid modifying the Xen code.
Quoted 3 lines
-- PMM
Paolo Bonzini
maintainerRe: [PATCH v3 17/19] hw/arm: Automatically select the 'virt' machine on KVM
Quoted 9 lines · Philippe Mathieu-Daudé
Yes, the problem if I don't restrict to KVM, when using the Xen accelerator odd things occur
(using configure --enable-xen --disable-tcg --disable-kvm):Compiling C object
libqemu-i386-softmmu.fa.p/hw_cpu_a15mpcore.c.ohw/cpu/a15mpcore.c:28:10: fatal error:kvm_arm.h: No such file or directory
I don't understand. Is Xen adding CONFIG_ARM_VIRT=y to default-configs/i386-softmmu.mak??
(By the way, there are duplicate Kconfig symbols between target/arm and hw/cpu, they could/should be removed from target/arm).
Paolo
Re: [PATCH v3 17/19] hw/arm: Automatically select the 'virt' machine on KVM
Quoted 5 lines · Paolo Bonzini
Quoted 4 lines · Philippe Mathieu-Daudé
Yes, the problem if I don't restrict to KVM, when using the Xen accelerator odd things occur
(using configure --enable-xen --disable-tcg --disable-kvm):
Quoted 8 lines
Quoted 5 lines
Compiling C object
libqemu-i386-softmmu.fa.p/hw_cpu_a15mpcore.c.ohw/cpu/a15mpcore.c:28:10: fatal error:kvm_arm.h: No such file or directoryI don't understand. Is Xen adding
CONFIG_ARM_VIRT=yto default-configs/i386-softmmu.mak??
No, this is when using:
config ARM_VIRT
bool
+ default y
I had the understanding devices in hw/$BASEARCH would be only included for $ARCH, but I was wrong, any arch kconfig-include the devices of the other archs.
I tried the following diff which doesn't build because various devices in *non*-archdep folders use arch-specific Kconfig values:
-- >8 --
meson.build +1 -0
@@ -575,6 +575,7 @@ foreach target : target_dirs if fs.is_file(target_kconfig) minikconf_input += [target_kconfig] endif + minikconf_input += 'hw' / config_target['TARGET_BASE_ARCH'] / 'Kconfig' config_devices_mak = configure_file( input: minikconf_input, output: config_devices_mak,
hw/Kconfig +0 -23
@@ -41,29 +41,29 @@ source vfio/Kconfig source watchdog/Kconfig # arch Kconfig -source arm/Kconfig -source alpha/Kconfig -source avr/Kconfig -source cris/Kconfig -source hppa/Kconfig -source i386/Kconfig -source lm32/Kconfig -source m68k/Kconfig -source microblaze/Kconfig -source mips/Kconfig -source moxie/Kconfig -source nios2/Kconfig -source openrisc/Kconfig -source ppc/Kconfig -source riscv/Kconfig -source rx/Kconfig -source s390x/Kconfig -source sh4/Kconfig -source sparc/Kconfig -source sparc64/Kconfig -source tricore/Kconfig -source unicore32/Kconfig -source xtensa/Kconfig # Symbols used by multiple targets config TEST_DEVICES
---
Quoted 3 lines
(By the way, there are duplicate
Kconfigsymbols between target/arm and hw/cpu, they could/should be removed from target/arm).
I'd rather define Kconfig entry where the model is, so in this case keep them defined in hw/cpu/Kconfig and remove dup entries from hw/arm/Kconfig (if Peter is OK with that).
Quoted 3 lines
Paolo
Re: [PATCH v3 17/19] hw/arm: Automatically select the 'virt' machine on KVM
Quoted 66 lines · Philippe Mathieu-Daudé
Quoted 5 lines · Paolo Bonzini
Quoted 4 lines · Philippe Mathieu-Daudé
Yes, the problem if I don't restrict to KVM, when using the Xen accelerator odd things occur
(using configure --enable-xen --disable-tcg --disable-kvm):Quoted 8 lines
Quoted 5 lines
Compiling C object
libqemu-i386-softmmu.fa.p/hw_cpu_a15mpcore.c.ohw/cpu/a15mpcore.c:28:10: fatal error:kvm_arm.h: No such file or directoryI don't understand. Is Xen adding
CONFIG_ARM_VIRT=yto default-configs/i386-softmmu.mak??No, this is when using:
config
ARM_VIRT
bool
+ default yI had the understanding devices in hw/$BASEARCH would be only included for $ARCH, but I was wrong, any arch kconfig-include the devices of the other archs.
I tried the following diff which doesn't build because various devices in *non*-archdep folders use arch-specific
Kconfigvalues:-- >8 --
meson.build +1
-0@@ -575,6 +575,7 @@ foreach target : target_dirs if fs.is_file(target_kconfig) minikconf_input += [target_kconfig] endif + minikconf_input += 'hw' / config_target['TARGET_BASE_ARCH'] / 'Kconfig' config_devices_mak = configure_file( input: minikconf_input, output: config_devices_mak,hw/Kconfig +0
-17@@ -41,29 +41,29 @@ source vfio/Kconfig source watchdog/Kconfig # arch Kconfig -source arm/Kconfig -source alpha/Kconfig -source avr/Kconfig -source cris/Kconfig -source hppa/Kconfig -source i386/Kconfig -source lm32/Kconfig -source m68k/Kconfig -source microblaze/Kconfig -source mips/Kconfig -source moxie/Kconfig -source nios2/Kconfig -source openrisc/Kconfig -source ppc/Kconfig -source riscv/Kconfig -source rx/Kconfig -source s390x/Kconfig
hw/Kconfig source vfio/Kconfig
Quoted 10 lines
hw/Kconfig +0
-7-source sh4/Kconfig -source sparc/Kconfig -source sparc64/Kconfig -source tricore/Kconfig -source unicore32/Kconfig -source xtensa/Kconfig # Symbols used by multiple targets config TEST_DEVICES ---
List of arch-indep Kconfig using arch-defined selectors:
hw/acpi/Kconfig:42: depends on PC hw/intc/Kconfig:31: depends on ARM_GIC && KVM hw/intc/Kconfig:36: depends on OPENPIC && KVM hw/intc/Kconfig:40: depends on POWERNV || PSERIES hw/intc/Kconfig:49: depends on XICS && KVM hw/intc/Kconfig:60: depends on S390_FLIC && KVM
hw/mem/Kconfig:11: depends on (PC || PSERIES || ARM_VIRT)
hw/pci-bridge/Kconfig:8: default y if Q35
hw/timer/Kconfig:14: default y if PC
hw/tpm/Kconfig:18: depends on TPM && PC
hw/tpm/Kconfig:24: depends on TPM && PSERIES
hw/vfio/Kconfig:16: depends on LINUX && S390_CCW_VIRTIO
hw/vfio/Kconfig:38: depends on LINUX && S390_CCW_VIRTIO
Paolo Bonzini
maintainerRe: [PATCH v3 17/19] hw/arm: Automatically select the 'virt' machine on KVM
Quoted 8 lines · Philippe Mathieu-Daudé
List of arch-indep
Kconfigusing arch-defined selectors:hw/acpi/Kconfig:42: depends on PC hw/intc/Kconfig:31: depends on ARM_GIC && KVM hw/intc/Kconfig:36: depends on OPENPIC && KVM hw/intc/Kconfig:40: depends on POWERNV || PSERIES hw/intc/Kconfig:49: depends on XICS && KVM hw/intc/Kconfig:60: depends on S390_FLIC && KVM
Quoted 8 lines
hw/mem/Kconfig:11: depends on (PC || PSERIES ||
ARM_VIRT)
hw/pci-bridge/Kconfig:8: default y if Q35
hw/timer/Kconfig:14: default y if PC
hw/tpm/Kconfig:18: depends on TPM && PC
hw/tpm/Kconfig:24: depends on TPM && PSERIES
hw/vfio/Kconfig:16: depends on LINUX &&S390_CCW_VIRTIO
hw/vfio/Kconfig:38: depends on LINUX &&S390_CCW_VIRTIO
I don't think that's a problem, and also I'm not sure this patch is a good idea.
See docs/devel/kconfig.rst: "Boards default to false; they are enabled by the ``default-configs/*.mak`` for the target they apply to".
Paolo
PATCH v3 18/19 hw/arm: Do not build to 'virt' machine on Xen
In reply to Philippe Mathieu-DaudéXen on ARM does not use QEMU machines [*]. Disable the 'virt' machine there to avoid odd errors such:
CC i386-softmmu/hw/cpu/a15mpcore.o
hw/cpu/a15mpcore.c:28:10: fatal error: kvm_arm.h: No such file or directory
---
Cc: Stefano Stabellini <[email protected]>
Cc: Anthony Perard <[email protected]>
Cc: Paul Durrant <[email protected]>
Cc: [email protected]
--- hw/arm/Kconfig | 1 + 1 file changed, 1 insertion(+)
hw/arm/Kconfig +1 -0
@@ -1,5 +1,6 @@ config ARM_VIRT bool + depends on !XEN default y if KVM imply PCI_DEVICES imply TEST_DEVICES
Signature · 1 line
2.21.1
Re: [PATCH v3 18/19] hw/arm: Do not build to 'virt' machine on Xen
Quoted 7 lines · Philippe Mathieu-Daudé
Xen on ARM does not use QEMU machines [*]. Disable the 'virt' machine there to avoid odd errors such:
CC i386-softmmu/hw/cpu/a15mpcore.o
hw/cpu/a15mpcore.c:28:10: fatal error:kvm_arm.h: No such file or directory
I confirm that what's written on that wikipage is correct: Xen on ARM doesn't use QEMU for emulation, only as a PV backends provider. As such, and also because the code is a bit entangled with the x86 platform, even on ARM we are building and running qemu-system-i386 to get the PV disk and PV framebuffer. Of course, no x86 emulation is actually done.
Ideally we would have a non-arch-specific machine type for the PV backends, but that doesn't exist today.
In short, I think this patch is fine, at least until somebody comes around and tries to add emulation to Xen on ARM.
Quoted 24 lines
Signed-off-by Philippe Mathieu-Daudé <[email protected]>---
Cc: Stefano Stabellini <[email protected]>
Cc: Anthony Perard <[email protected]>
Cc: Paul Durrant <[email protected]>
Cc: [email protected]--- hw/arm/Kconfig | 1 + 1 file changed, 1 insertion(+)hw/arm/Kconfig +1
-0@@ -1,5 +1,6 @@ config ARM_VIRT bool + depends on !XEN default y if KVM imply PCI_DEVICES imply TEST_DEVICESSignature · 1 line
2.21.1
Re: [PATCH v3 18/19] hw/arm: Do not build to 'virt' machine on Xen
In reply to Philippe Mathieu-DaudéQuoted 24 lines · Philippe Mathieu-Daudé
Xen on ARM does not use QEMU machines [*]. Disable the 'virt' machine there to avoid odd errors such:
CC i386-softmmu/hw/cpu/a15mpcore.o
hw/cpu/a15mpcore.c:28:10: fatal error:kvm_arm.h: No such file or directorySigned-off-by Philippe Mathieu-Daudé <[email protected]>---
Cc: Stefano Stabellini <[email protected]>
Cc: Anthony Perard <[email protected]>
Cc: Paul Durrant <[email protected]>
Cc: [email protected]--- hw/arm/Kconfig | 1 + 1 file changed, 1 insertion(+)hw/arm/Kconfig +0
-0
hw/arm/Kconfig
Quoted 7 lines
hw/arm/Kconfig +1
-1@@ -1,5 +1,6 @@ config ARM_VIRT bool + depends on !XEN default y if KVM imply PCI_DEVICES imply TEST_DEVICES --
This seems odd to me:
(1) the error message you quote is for a15mpcore.c, not virt.c
(2) shouldn't this be prevented by something saying "don't build guest architecture X boards into Y-softmmu", rather than a specific flag for a specific arm board ?
thanks
-- PMM
Re: [PATCH v3 18/19] hw/arm: Do not build to 'virt' machine on Xen
Quoted 20 lines · Peter Maydell
Quoted 19 lines · Philippe Mathieu-Daudé
Xen on ARM does not use QEMU machines [*]. Disable the 'virt' machine there to avoid odd errors such:
CC i386-softmmu/hw/cpu/a15mpcore.o
hw/cpu/a15mpcore.c:28:10: fatal error:kvm_arm.h: No such file or directorySigned-off-by Philippe Mathieu-Daudé <[email protected]>---
Cc: Stefano Stabellini <[email protected]>
Cc: Anthony Perard <[email protected]>
Cc: Paul Durrant <[email protected]>
Cc: [email protected]--- hw/arm/Kconfig | 1 + 1 file changed, 1 insertion(+)
Quoted 15 lines
hw/arm/Kconfig
Quoted 12 lines
hw/arm/Kconfig +1
-1@@ -1,5 +1,6 @@ config ARM_VIRT bool + depends on !XEN default y if KVM imply PCI_DEVICES imply TEST_DEVICES --This seems odd to me:
(1) the error message you quote is fora15mpcore.c, notvirt.c
This is the first device the virt board selects:
config ARM_VIRT
bool
imply PCI_DEVICES
imply TEST_DEVICES
imply VFIO_AMD_XGBE
imply VFIO_PLATFORM
imply VFIO_XGMAC
imply TPM_TIS_SYSBUS
select A15MPCORE
...Quoted 3 lines
(2) shouldn't this be prevented by something saying "don't build guest architecture X boards into Y-softmmu", rather than a specific flag for a specific arm board ?
Yes, agreed. This surgical change was quicker for my testing, but we don't need this patch right now, so let's drop it.
Quoted 4 lines
thanks
-- PMM
PATCH v3 19/19 .travis.yml: Add a KVM-only Aarch64 job
In reply to Philippe Mathieu-DaudéAdd a job to build QEMU on Aarch64 with TCG disabled, so this configuration won't bitrot over time.
---
Job ran for 13 min 1 sec
https://travis-ci.org/github/philmd/qemu/jobs/663122258
--- .travis.yml | 32 ++++++++++++++++++++++++++++++++ 1 file changed, 32 insertions(+)
.travis.yml +32 -0
@@ -450,6 +450,38 @@ jobs: - TEST_CMD="make check check-tcg V=1" - CONFIG="--disable-containers --target-list=${MAIN_SOFTMMU_TARGETS}" + - name: "[aarch64] GCC check (KVM)" + arch: arm64 + dist: xenial + addons: + apt_packages: + - libaio-dev + - libattr1-dev + - libcap-ng-dev + - libgcrypt20-dev + - libgnutls28-dev + - libiscsi-dev + - liblttng-ust-dev + - libnfs-dev + - libnss3-dev + - libpixman-1-dev + - libpng-dev + - librados-dev + - libseccomp-dev + - liburcu-dev + - libusb-1.0-0-dev + - libvdeplug-dev + - libvte-2.91-dev + # Tests dependencies + - genisoimage + env: + - CONFIG="--disable-containers --disable-tcg --enable-kvm --enable-fdt --disable-tools" + - TEST_CMD="make check-unit" + script: + # Only select the 'virt' machine. + - echo CONFIG_ARM_VIRT=y > ${SRC_DIR}/default-configs/aarch64-softmmu.mak + - make -j3 && travis_retry ${TEST_CMD} + - name: "[ppc64] GCC check-tcg" arch: ppc64le dist: xenial
Signature · 1 line
2.21.1
Patchew URL: https://patchew.org/QEMU/[email protected]/
Patchew URL: https://patchew.org/QEMU/[email protected]/
Hi,
This series failed the docker-quick@centos7 build test. Please find the testing commands and their output below. If you have Docker installed, you can probably reproduce it locally.
=== TEST SCRIPT BEGIN ===
#!/bin/bash
make docker-image-centos7 V=1 NETWORK=1
time make docker-test-quick@centos7 SHOW_ENV=1 J=14 NETWORK=1 === TEST SCRIPT END ===
missing object type 'or-irq'
Broken pipe/tmp/qemu-test/src/tests/qtest/libqtest.c:175: kill_qemu() detected QEMU death from signal 6 (Aborted) (core dumped)
ERROR - too few tests run (expected 6, got 5)
make: *** [check-qtest-aarch64] Error 1
make: *** Waiting for unfinished jobs....
Could not access KVM kernel module: No such file or directory
qemu-system-x86_64: -accel kvm: failed to initialize kvm: No such file or directory
---
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['sudo', '-n', 'docker', 'run', '--label', 'com.qemu.instance.uuid=08bd1beebdb64d78b4b65d35e7611a89', '-u', '1003', '--security-opt', 'seccomp=unconfined', '--rm', '-e', 'TARGET_LIST=', '-e', 'EXTRA_CONFIGURE_OPTS=', '-e', 'V=', '-e', 'J=14', '-e', 'DEBUG=', '-e', 'SHOW_ENV=1', '-e', 'CCACHE_DIR=/var/tmp/ccache', '-v', '/home/patchew2/.cache/qemu-docker-ccache:/var/tmp/ccache:z', '-v', '/var/tmp/patchew-tester-tmp-t2n0p0f3/src/docker-src.2020-03-16-15.51.58.19896:/var/tmp/qemu:z,ro', 'qemu:centos7', '/var/tmp/qemu/run', 'test-quick']' returned non-zero exit status 2. filter=--filter=label=com.qemu.instance.uuid=08bd1beebdb64d78b4b65d35e7611a89
make[1]: *** [docker-run] Error 1
make[1]: Leaving directory `/var/tmp/patchew-tester-tmp-t2n0p0f3/src'
make: *** [docker-run-test-quick@centos7] Error 2
real 11m59.274s
user 0m8.577s
The full log is available at
http://patchew.org/logs/[email protected]/testing.docker-quick@centos7/?type=message.
---
Email generated automatically by Patchew [https://patchew.org/].
Please send your feedback to [email protected]
Patchew URL: https://patchew.org/QEMU/[email protected]/
Patchew URL: https://patchew.org/QEMU/[email protected]/
Hi,
This series failed the docker-quick@centos7 build test. Please find the testing commands and their output below. If you have Docker installed, you can probably reproduce it locally.
=== TEST SCRIPT BEGIN ===
#!/bin/bash
make docker-image-centos7 V=1 NETWORK=1
time make docker-test-quick@centos7 SHOW_ENV=1 J=14 NETWORK=1 === TEST SCRIPT END ===
missing object type 'or-irq'
Broken pipe/tmp/qemu-test/src/tests/qtest/libqtest.c:175: kill_qemu() detected QEMU death from signal 6 (Aborted) (core dumped)
ERROR - too few tests run (expected 6, got 5)
make: *** [check-qtest-aarch64] Error 1
make: *** Waiting for unfinished jobs....
Could not access KVM kernel module: No such file or directory
qemu-system-x86_64: -accel kvm: failed to initialize kvm: No such file or directory
---
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['sudo', '-n', 'docker', 'run', '--label', 'com.qemu.instance.uuid=d51fe73160644e0ba6a0f3cf1c1d6208', '-u', '1003', '--security-opt', 'seccomp=unconfined', '--rm', '-e', 'TARGET_LIST=', '-e', 'EXTRA_CONFIGURE_OPTS=', '-e', 'V=', '-e', 'J=14', '-e', 'DEBUG=', '-e', 'SHOW_ENV=1', '-e', 'CCACHE_DIR=/var/tmp/ccache', '-v', '/home/patchew2/.cache/qemu-docker-ccache:/var/tmp/ccache:z', '-v', '/var/tmp/patchew-tester-tmp-u8ju4ssp/src/docker-src.2020-03-16-18.57.13.21007:/var/tmp/qemu:z,ro', 'qemu:centos7', '/var/tmp/qemu/run', 'test-quick']' returned non-zero exit status 2. filter=--filter=label=com.qemu.instance.uuid=d51fe73160644e0ba6a0f3cf1c1d6208
make[1]: *** [docker-run] Error 1
make[1]: Leaving directory `/var/tmp/patchew-tester-tmp-u8ju4ssp/src'
make: *** [docker-run-test-quick@centos7] Error 2
real 13m16.228s
user 0m8.763s
The full log is available at
http://patchew.org/logs/[email protected]/testing.docker-quick@centos7/?type=message.
---
Email generated automatically by Patchew [https://patchew.org/].
Please send your feedback to [email protected]