From: "Alex Bennée" <alex.bennee@linaro.org>
To: Gautam Bhat <mindentropy@gmail.com>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: How does "rsi" get set in x86 prologue?
Date: Thu, 02 Jan 2025 10:15:23 +0000 [thread overview]
Message-ID: <87jzbdv7wk.fsf@draig.linaro.org> (raw)
In-Reply-To: <CAM2a4uxJFhw71emxdZrB4SF-JSzJy_-bL=g9ke7OmjUoOXUDYQ@mail.gmail.com> (Gautam Bhat's message of "Thu, 2 Jan 2025 00:56:47 +0530")
Gautam Bhat <mindentropy@gmail.com> writes:
> I am trying to understanding the generated code for the x86 target. On
> EPILOGUE code below:
>
> 0x7fff98000000: 55 pushq %rbp
> 0x7fff98000001: 53 pushq %rbx
> 0x7fff98000002: 41 54 pushq %r12
> 0x7fff98000004: 41 55 pushq %r13
> 0x7fff98000006: 41 56 pushq %r14
> 0x7fff98000008: 41 57 pushq %r15
> 0x7fff9800000a: 48 8b ef movq %rdi, %rbp
> 0x7fff9800000d: 48 81 c4 78 fb ff ff addq $-0x488, %rsp
> 0x7fff98000014: ff e6 jmpq *%rsi
> 0x7fff98000016: 33 c0 xorl %eax, %eax
> 0x7fff98000018: 48 81 c4 88 04 00 00 addq $0x488, %rsp
> 0x7fff9800001f: c5 f8 77 vzeroupper
> 0x7fff98000022: 41 5f popq %r15
> 0x7fff98000024: 41 5e popq %r14
> 0x7fff98000026: 41 5d popq %r13
> 0x7fff98000028: 41 5c popq %r12
> 0x7fff9800002a: 5b popq %rbx
> 0x7fff9800002b: 5d popq %rbp
> 0x7fff9800002c: c3 retq
>
> Can someone help me understand in which file or where in the source
> does the "rsi" get set to jump? (0x7fff98000014: ff e6 jmpq
> *%rsi)
The prologue/epilogue code is generated by:
/* Generate global QEMU prologue and epilogue code */
static void tcg_target_qemu_prologue(TCGContext *s)
{
int i, stack_addend;
/* TB prologue */
/* Reserve some stack space, also for TCG temps. */
stack_addend = FRAME_SIZE - PUSH_SIZE;
tcg_set_frame(s, TCG_REG_CALL_STACK, TCG_STATIC_CALL_ARGS_SIZE,
CPU_TEMP_BUF_NLONGS * sizeof(long));
/* Save all callee saved registers. */
for (i = 0; i < ARRAY_SIZE(tcg_target_callee_save_regs); i++) {
tcg_out_push(s, tcg_target_callee_save_regs[i]);
}
if (!tcg_use_softmmu && guest_base) {
int seg = setup_guest_base_seg();
if (seg != 0) {
x86_guest_base.seg = seg;
} else if (guest_base == (int32_t)guest_base) {
x86_guest_base.ofs = guest_base;
} else {
assert(TCG_TARGET_REG_BITS == 64);
/* Choose R12 because, as a base, it requires a SIB byte. */
x86_guest_base.index = TCG_REG_R12;
tcg_out_movi(s, TCG_TYPE_PTR, x86_guest_base.index, guest_base);
tcg_regset_set_reg(s->reserved_regs, x86_guest_base.index);
}
}
if (TCG_TARGET_REG_BITS == 32) {
tcg_out_ld(s, TCG_TYPE_PTR, TCG_AREG0, TCG_REG_ESP,
(ARRAY_SIZE(tcg_target_callee_save_regs) + 1) * 4);
tcg_out_addi(s, TCG_REG_ESP, -stack_addend);
/* jmp *tb. */
tcg_out_modrm_offset(s, OPC_GRP5, EXT5_JMPN_Ev, TCG_REG_ESP,
(ARRAY_SIZE(tcg_target_callee_save_regs) + 2) * 4
+ stack_addend);
} else {
tcg_out_mov(s, TCG_TYPE_PTR, TCG_AREG0, tcg_target_call_iarg_regs[0]);
tcg_out_addi(s, TCG_REG_ESP, -stack_addend);
/* jmp *tb. */
tcg_out_modrm(s, OPC_GRP5, EXT5_JMPN_Ev, tcg_target_call_iarg_regs[1]);
}
/*
* Return path for goto_ptr. Set return value to 0, a-la exit_tb,
* and fall through to the rest of the epilogue.
*/
tcg_code_gen_epilogue = tcg_splitwx_to_rx(s->code_ptr);
tcg_out_movi(s, TCG_TYPE_REG, TCG_REG_EAX, 0);
/* TB epilogue */
tb_ret_addr = tcg_splitwx_to_rx(s->code_ptr);
tcg_out_addi(s, TCG_REG_CALL_STACK, stack_addend);
if (have_avx2) {
tcg_out_vex_opc(s, OPC_VZEROUPPER, 0, 0, 0, 0);
}
for (i = ARRAY_SIZE(tcg_target_callee_save_regs) - 1; i >= 0; i--) {
tcg_out_pop(s, tcg_target_callee_save_regs[i]);
}
tcg_out_opc(s, OPC_RET, 0, 0, 0);
}
The call into the prologue comes from:
ret = tcg_qemu_tb_exec(cpu_env(cpu), tb_ptr);
in cpu_tb_exec. With env in RDI and tb_ptr (the code address) being in
RSI.
>
> Thanks,
> Gautam.
--
Alex Bennée
Virtualisation Tech Lead @ Linaro
next prev parent reply other threads:[~2025-01-02 10:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-01 19:26 How does "rsi" get set in x86 prologue? Gautam Bhat
2025-01-02 10:15 ` Alex Bennée [this message]
2025-01-30 15:34 ` Gautam Bhat
2025-01-31 12:58 ` Alex Bennée
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=87jzbdv7wk.fsf@draig.linaro.org \
--to=alex.bennee@linaro.org \
--cc=mindentropy@gmail.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is 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).