From: Bibo Mao <maobibo@loongson.cn>
To: Huacai Chen <chenhuacai@kernel.org>
Cc: kernel@xen0n.name, kvm@vger.kernel.org,
loongarch@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] LoongArch: KVM: Small enhancement about timer
Date: Thu, 30 Apr 2026 09:17:56 +0800 [thread overview]
Message-ID: <b876bfe6-4a47-559a-1f33-00e363cb62de@loongson.cn> (raw)
In-Reply-To: <CAAhV-H5+mR5gnd6x6yUEFK7ZnWyYQVTiE6C=enk7bHxe2Mo2Sg@mail.gmail.com>
On 2026/4/29 下午6:13, Huacai Chen wrote:
> The first patch cannot be applied cleanly, I adjusted it and applied,
> hope it is correct.
> https://git.kernel.org/pub/scm/linux/kernel/git/chenhuacai/linux-loongson.git/log/?h=loongarch-next
yes, that is correct.
And thanks for your modification.
Regards
Bibo Mao
>
>
> Huacai
>
> On Tue, Apr 14, 2026 at 3:23 PM Bibo Mao <maobibo@loongson.cn> wrote:
>>
>> By running LTP stress test cases on VM, there is an RCU timeout issue on
>> some vCPUs recently. The problem is that there is HW timer interrupt lost
>> issue when injecting SIP0/IPI interrupt from KVM hypervisor, this problem
>> is hidden because the KVM hypervisor will inject spurious timer interrupt
>> if emulated timer is expired. In late the spurious timer interrupt is
>> clear if old TI bit of ESTAT register is not set, so there will be RCU
>> timeout issue with LTP stress test.
>>
>> This patch set fixes the HW timer interrupt lost issue, also this patch
>> moves unconditional delay in timer interrupt clear scenery, which happens
>> seldomly; mostly the timer interrupt bit is set when it expires.
>>
>> Bibo Mao (3):
>> LoongArch: KVM: Move AVEC interrupt injection in switch loop
>> LoongArch: KVM: Fix HW timer interrupt lost when inject interrupt from
>> software
>> LoongArch: KVM: Move unconditional delay in timer clear scenery
>>
>> arch/loongarch/kvm/interrupt.c | 37 +++++++++++++++++++++++++---------
>> arch/loongarch/kvm/timer.c | 16 +++++++++++++--
>> 2 files changed, 41 insertions(+), 12 deletions(-)
>>
>>
>> base-commit: d568788baab24875604c231f723dbb72387fb081
>> --
>> 2.39.3
>>
>>
prev parent reply other threads:[~2026-04-30 1:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-14 7:23 [PATCH 0/3] LoongArch: KVM: Small enhancement about timer Bibo Mao
2026-04-14 7:23 ` [PATCH 1/3] LoongArch: KVM: Move AVEC interrupt injection in switch loop Bibo Mao
2026-04-14 7:23 ` [PATCH 2/3] LoongArch: KVM: Fix HW timer interrupt lost when inject interrupt from software Bibo Mao
2026-04-14 7:23 ` [PATCH 3/3] LoongArch: KVM: Move unconditional delay in timer clear scenery Bibo Mao
2026-04-29 10:13 ` [PATCH 0/3] LoongArch: KVM: Small enhancement about timer Huacai Chen
2026-04-30 1:17 ` Bibo Mao [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=b876bfe6-4a47-559a-1f33-00e363cb62de@loongson.cn \
--to=maobibo@loongson.cn \
--cc=chenhuacai@kernel.org \
--cc=kernel@xen0n.name \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=loongarch@lists.linux.dev \
/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).