From: Giacomo Mazzola <gmazz@amazon.de>
To: <kvm@vger.kernel.org>
Cc: Giacomo Mazzola <gmazz@amazon.de>
Subject: [kvm-unit-tests PATCH 4/8] x86: fix ISR thunk to use absolute indirect jump
Date: Tue, 9 Jun 2026 14:08:56 +0000 [thread overview]
Message-ID: <20260609140901.95727-5-gmazz@amazon.de> (raw)
In-Reply-To: <20260609140901.95727-1-gmazz@amazon.de>
Replace the relative jmp (e9 rel32) with an absolute indirect
jmp *0(%rip) (ff 25 00000000 + addr64). The rel32 displacement
is sign-extended to 64 bits, so when the displacement between
the thunk and isr_entry_point exceeds 2 GiB the sign extension
corrupts the target address.
Signed-off-by: Giacomo Mazzola <gmazz@amazon.de>
---
lib/x86/isr.c | 8 +++++---
1 file changed, 5 insertions(+), 3 deletions(-)
diff --git a/lib/x86/isr.c b/lib/x86/isr.c
index 53c0c2b3..4f474931 100644
--- a/lib/x86/isr.c
+++ b/lib/x86/isr.c
@@ -79,9 +79,11 @@ void handle_irq(unsigned vec, void (*func)(isr_regs_t *regs))
/* mov $func_high, %(rsp+4) */
*thunk++ = 0xc7; *thunk++ = 0x44; *thunk++ = 0x24; *thunk++ = 0x04;
*(u32 *)thunk = (ulong)func >> 32; thunk += 4;
- /* jmp isr_entry_point */
- *thunk ++ = 0xe9;
- *(u32 *)thunk = (ulong)isr_entry_point - (ulong)(thunk + 4);
+ /* jmp *0(%rip): absolute indirect jump to isr_entry_point */
+ *thunk++ = 0xff; *thunk++ = 0x25;
+ /* disp32 = 0: address follows */
+ *(u32 *)thunk = 0; thunk += 4;
+ *(u64 *)thunk = (ulong)isr_entry_point;
#else
/* push $func */
*thunk++ = 0x68;
--
2.47.3
Amazon Web Services Development Center Germany GmbH
Tamara-Danz-Str. 13
10243 Berlin
Geschaeftsfuehrung: Christof Hellmis, Andreas Stieger
Eingetragen am Amtsgericht Charlottenburg unter HRB 257764 B
Sitz: Berlin
Ust-ID: DE 365 538 597
next prev parent reply other threads:[~2026-06-09 14:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-09 14:08 [kvm-unit-tests PATCH 0/8] x86: fixes for running KUT as EFI on non-QEMU KVM hosts Giacomo Mazzola
2026-06-09 14:08 ` [kvm-unit-tests PATCH 1/8] x86: efi: use PER_CPU_SIZE for per-CPU stack allocation Giacomo Mazzola
2026-06-09 14:08 ` [kvm-unit-tests PATCH 2/8] x86: fix EFI memory allocator to clamp regions to 4 GiB Giacomo Mazzola
2026-06-09 14:08 ` [kvm-unit-tests PATCH 3/8] x86: skip PMU init when no PMU is advertised Giacomo Mazzola
2026-06-09 14:08 ` Giacomo Mazzola [this message]
2026-06-09 14:08 ` [kvm-unit-tests PATCH 5/8] x86: replace per-AP bringup prints with a single summary line Giacomo Mazzola
2026-06-09 14:08 ` [kvm-unit-tests PATCH 6/8] x86: add timeout-based SMP bringup when fw_cfg is unavailable Giacomo Mazzola
2026-06-09 14:08 ` [kvm-unit-tests PATCH 7/8] efi: fix load_options_size conversion to character count Giacomo Mazzola
2026-06-10 16:09 ` Andrew Jones
2026-06-09 14:09 ` [kvm-unit-tests PATCH 8/8] efi: parse KUT_ENV= from load options into environ Giacomo Mazzola
2026-06-10 18:18 ` Andrew Jones
2026-06-25 14:04 ` [kvm-unit-tests PATCH v2 8/8] lib: parse KUT_ENV= from command line " Giacomo Mazzola
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=20260609140901.95727-5-gmazz@amazon.de \
--to=gmazz@amazon.de \
--cc=kvm@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.