From: Igor Mammedov <imammedo@redhat.com>
To: Bibo Mao <maobibo@loongson.cn>
Cc: Song Gao <gaosong@loongson.cn>,
Markus Armbruster <armbru@redhat.com>,
Jiaxun Yang <jiaxun.yang@flygoat.com>,
qemu-devel@nongnu.org, Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [PATCH v6 3/6] hw/loongarch/virt: Fix error handling in cpu unplug
Date: Fri, 4 Apr 2025 14:08:28 +0200 [thread overview]
Message-ID: <20250404140828.6041ef56@imammedo.users.ipa.redhat.com> (raw)
In-Reply-To: <20250321031259.2419842-4-maobibo@loongson.cn>
On Fri, 21 Mar 2025 11:12:56 +0800
Bibo Mao <maobibo@loongson.cn> wrote:
> In function virt_cpu_unplug(), it will send cpu unplug message to
> interrupt controller extioi and ipi irqchip. If there is problem in
> this function, system should continue to run and keep state the same
> before cpu is removed.
see my comment to 2/6, the same applies here.
(unless there is a good reason why it can fail)
>
> If error happends in cpu unplug stage, send cpu plug message to extioi
> and ipi irqchip to restore to previous stage, and then return immediately.
>
> Fixes: 2cd6857f6f5b (hw/loongarch/virt: Implement cpu unplug interface)
> Signed-off-by: Bibo Mao <maobibo@loongson.cn>
> ---
> hw/loongarch/virt.c | 6 ++++++
> 1 file changed, 6 insertions(+)
>
> diff --git a/hw/loongarch/virt.c b/hw/loongarch/virt.c
> index 8563967c8b..503362a69e 100644
> --- a/hw/loongarch/virt.c
> +++ b/hw/loongarch/virt.c
> @@ -958,6 +958,8 @@ static void virt_cpu_unplug(HotplugHandler *hotplug_dev,
> hotplug_handler_unplug(HOTPLUG_HANDLER(lvms->extioi), dev, &err);
> if (err) {
> error_propagate(errp, err);
> + hotplug_handler_plug(HOTPLUG_HANDLER(lvms->ipi), dev,
> + &error_abort);
> return;
> }
>
> @@ -965,6 +967,10 @@ static void virt_cpu_unplug(HotplugHandler *hotplug_dev,
> hotplug_handler_unplug(HOTPLUG_HANDLER(lvms->acpi_ged), dev, &err);
> if (err) {
> error_propagate(errp, err);
> + hotplug_handler_plug(HOTPLUG_HANDLER(lvms->ipi), dev,
> + &error_abort);
> + hotplug_handler_plug(HOTPLUG_HANDLER(lvms->extioi), dev,
> + &error_abort);
> return;
> }
>
next prev parent reply other threads:[~2025-04-04 12:09 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-21 3:12 [PATCH v6 0/6] target/loongarch: Fix some issues reported from coccinelle Bibo Mao
2025-03-21 3:12 ` [PATCH v6 1/6] target/loongarch: Fix error handling of KVM feature checks Bibo Mao
2025-03-21 3:12 ` [PATCH v6 2/6] hw/loongarch/virt: Fix error handling in cpu plug Bibo Mao
2025-04-04 12:06 ` Igor Mammedov
2025-03-21 3:12 ` [PATCH v6 3/6] hw/loongarch/virt: Fix error handling in cpu unplug Bibo Mao
2025-03-21 6:47 ` Markus Armbruster
2025-03-21 7:00 ` bibo mao
2025-03-21 7:21 ` Markus Armbruster
2025-03-21 7:35 ` bibo mao
2025-03-21 8:08 ` Markus Armbruster
2025-03-21 8:21 ` bibo mao
2025-04-04 11:59 ` Igor Mammedov
2025-04-08 2:07 ` bibo mao
2025-03-21 7:09 ` bibo mao
2025-04-04 12:08 ` Igor Mammedov [this message]
2025-03-21 3:12 ` [PATCH v6 4/6] hw/loongarch/virt: Eliminate error_propagate() Bibo Mao
2025-03-21 3:12 ` [PATCH v6 5/6] target/loongarch: Remove unnecessary temporary variable assignment Bibo Mao
2025-03-21 3:12 ` [PATCH v6 6/6] target/loongarch: Clean up virt_cpu_irq_init() error handling 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=20250404140828.6041ef56@imammedo.users.ipa.redhat.com \
--to=imammedo@redhat.com \
--cc=armbru@redhat.com \
--cc=gaosong@loongson.cn \
--cc=jiaxun.yang@flygoat.com \
--cc=maobibo@loongson.cn \
--cc=pbonzini@redhat.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 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.