From: Xianglai Li <lixianglai@loongson.cn>
To: loongarch@lists.linux.dev, linux-kernel@vger.kernel.org,
kvm@vger.kernel.org, lixianglai@loongson.cn
Cc: Huacai Chen <chenhuacai@kernel.org>,
Tianrui Zhao <zhaotianrui@loongson.cn>,
Bibo Mao <maobibo@loongson.cn>
Subject: [PATCH V4 2/2] LoongArch: KVM: fix "unreliable stack" issue
Date: Tue, 14 Apr 2026 19:31:11 +0800 [thread overview]
Message-ID: <20260414113111.2997864-3-lixianglai@loongson.cn> (raw)
In-Reply-To: <20260414113111.2997864-1-lixianglai@loongson.cn>
Insert the appropriate UNWIND macro definition into the kvm_exc_entry in
the assembly function to guide the generation of correct ORC table entries,
thereby solving the timeout problem of loading the livepatch-sample module
on a physical machine running multiple vcpus virtual machines.
Signed-off-by: Xianglai Li <lixianglai@loongson.cn>
---
Cc: Huacai Chen <chenhuacai@kernel.org>
Cc: Tianrui Zhao <zhaotianrui@loongson.cn>
Cc: Bibo Mao <maobibo@loongson.cn>
arch/loongarch/kvm/switch.S | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/loongarch/kvm/switch.S b/arch/loongarch/kvm/switch.S
index 1a5636790ef9..29cf6704296e 100644
--- a/arch/loongarch/kvm/switch.S
+++ b/arch/loongarch/kvm/switch.S
@@ -114,7 +114,7 @@
.p2align PAGE_SHIFT
.cfi_sections .debug_frame
SYM_CODE_START(kvm_exc_entry)
- UNWIND_HINT_UNDEFINED
+ UNWIND_HINT_END_OF_STACK
csrwr a2, KVM_TEMP_KS
csrrd a2, KVM_VCPU_KS
addi.d a2, a2, KVM_VCPU_ARCH
--
2.39.1
prev parent reply other threads:[~2026-04-14 11:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-14 11:31 [PATCH V4 0/2] LoongArch: KVM: fix "unreliable stack" issue Xianglai Li
2026-04-14 11:31 ` [PATCH V4 1/2] LoongArch: KVM: Compile the switch.S file directly into the kernel Xianglai Li
2026-04-27 7:56 ` Huacai Chen
2026-04-27 8:36 ` lixianglai
2026-04-27 8:48 ` Huacai Chen
2026-04-27 12:06 ` Jinyang He
2026-04-29 9:47 ` Huacai Chen
2026-04-14 11:31 ` Xianglai Li [this message]
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=20260414113111.2997864-3-lixianglai@loongson.cn \
--to=lixianglai@loongson.cn \
--cc=chenhuacai@kernel.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=loongarch@lists.linux.dev \
--cc=maobibo@loongson.cn \
--cc=zhaotianrui@loongson.cn \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).