mirror of
https://github.com/Motorhead1991/qemu.git
synced 2025-08-04 16:23:55 -06:00
arm: Clarify the logic of set_pc()
Until now, the set_pc logic was unclear, which raised questions about whether it should be used directly, applying a value to PC or adding additional checks, for example, set the Thumb bit in Arm cpu. Let's set the set_pc logic for “Configure the PC, as was done in the ELF file” and implement synchronize_with_tb hook for preserving PC to cpu_tb_exec. Signed-off-by: Julia Suvorova <jusual@mail.ru> Acked-by: Stefan Hajnoczi <stefanha@redhat.com> Message-id: 20190129121817.7109-1-jusual@mail.ru Reviewed-by: Peter Maydell <peter.maydell@linaro.org> Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
This commit is contained in:
parent
ef682cdb4a
commit
42f6ed9193
5 changed files with 39 additions and 25 deletions
|
@ -480,20 +480,6 @@ static void aarch64_cpu_finalizefn(Object *obj)
|
|||
{
|
||||
}
|
||||
|
||||
static void aarch64_cpu_set_pc(CPUState *cs, vaddr value)
|
||||
{
|
||||
ARMCPU *cpu = ARM_CPU(cs);
|
||||
/* It's OK to look at env for the current mode here, because it's
|
||||
* never possible for an AArch64 TB to chain to an AArch32 TB.
|
||||
* (Otherwise we would need to use synchronize_from_tb instead.)
|
||||
*/
|
||||
if (is_a64(&cpu->env)) {
|
||||
cpu->env.pc = value;
|
||||
} else {
|
||||
cpu->env.regs[15] = value;
|
||||
}
|
||||
}
|
||||
|
||||
static gchar *aarch64_gdb_arch_name(CPUState *cs)
|
||||
{
|
||||
return g_strdup("aarch64");
|
||||
|
@ -504,7 +490,6 @@ static void aarch64_cpu_class_init(ObjectClass *oc, void *data)
|
|||
CPUClass *cc = CPU_CLASS(oc);
|
||||
|
||||
cc->cpu_exec_interrupt = arm_cpu_exec_interrupt;
|
||||
cc->set_pc = aarch64_cpu_set_pc;
|
||||
cc->gdb_read_register = aarch64_cpu_gdb_read_register;
|
||||
cc->gdb_write_register = aarch64_cpu_gdb_write_register;
|
||||
cc->gdb_num_core_regs = 34;
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue