From: "Jürgen Groß" <jgross@suse.com>
To: Bibo Mao <maobibo@loongson.cn>,
Paolo Bonzini <pbonzini@redhat.com>,
Huacai Chen <chenhuacai@kernel.org>,
WANG Xuerui <kernel@xen0n.name>,
Ajay Kaher <ajay.kaher@broadcom.com>,
Alexey Makhalov <alexey.makhalov@broadcom.com>,
Broadcom internal kernel review list
<bcm-kernel-feedback-list@broadcom.com>
Cc: kvm@vger.kernel.org, loongarch@lists.linux.dev,
linux-kernel@vger.kernel.org, virtualization@lists.linux.dev,
x86@kernel.org
Subject: Re: [PATCH v3 2/2] LoongArch: Add paravirt support with vcpu_is_preempted() in guest side
Date: Wed, 3 Dec 2025 16:56:01 +0100 [thread overview]
Message-ID: <032a028f-9fe5-4839-a596-f4e6317d7946@suse.com> (raw)
In-Reply-To: <20251202024833.1714363-3-maobibo@loongson.cn>
[-- Attachment #1.1.1: Type: text/plain, Size: 325 bytes --]
On 02.12.25 03:48, Bibo Mao wrote:
> Function vcpu_is_preempted() is used to check whether vCPU is preempted
> or not. Here add implementation with vcpu_is_preempted() when option
> CONFIG_PARAVIRT is enabled.
>
> Signed-off-by: Bibo Mao <maobibo@loongson.cn>
Acked-by: Juergen Gross <jgross@suse.com>
Juergen
[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 3743 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 495 bytes --]
next prev parent reply other threads:[~2025-12-03 15:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-02 2:48 [PATCH v3 0/2] LoongArch: KVM: Add paravirt preempt support Bibo Mao
2025-12-02 2:48 ` [PATCH v3 1/2] LoongArch: KVM: Add paravirt preempt feature in hypervisor side Bibo Mao
2025-12-02 2:48 ` [PATCH v3 2/2] LoongArch: Add paravirt support with vcpu_is_preempted() in guest side Bibo Mao
2025-12-03 15:56 ` Jürgen Groß [this message]
2025-12-06 13:04 ` Huacai Chen
2025-12-18 12:10 ` Bibo Mao
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=032a028f-9fe5-4839-a596-f4e6317d7946@suse.com \
--to=jgross@suse.com \
--cc=ajay.kaher@broadcom.com \
--cc=alexey.makhalov@broadcom.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=chenhuacai@kernel.org \
--cc=kernel@xen0n.name \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=loongarch@lists.linux.dev \
--cc=maobibo@loongson.cn \
--cc=pbonzini@redhat.com \
--cc=virtualization@lists.linux.dev \
--cc=x86@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®