From: "Michael S. Tsirkin" <mst@redhat.com>
To: Salil Mehta <salil.mehta@huawei.com>
Cc: lixianglai <lixianglai@loongson.cn>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"Salil Mehta" <salil.mehta@opnsrc.net>,
"Bernhard Beschow" <shentey@gmail.com>,
"Xiaojuan Yang" <yangxiaojuan@loongson.cn>,
"Song Gao" <gaosong@loongson.cn>,
"Igor Mammedov" <imammedo@redhat.com>,
"Ani Sinha" <anisinha@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Richard Henderson" <richard.henderson@linaro.org>,
"Eduardo Habkost" <eduardo@habkost.net>,
"Marcel Apfelbaum" <marcel.apfelbaum@gmail.com>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
"wangyanan (Y)" <wangyanan55@huawei.com>,
"Daniel P. Berrangé" <berrange@redhat.com>,
"Peter Xu" <peterx@redhat.com>,
"David Hildenbrand" <david@redhat.com>,
"Bibo Mao" <maobibo@loongson.cn>
Subject: Re: [PATCH v3 1/7] Update ACPI GED framework to support vcpu hot-(un)plug
Date: Wed, 27 Sep 2023 11:18:18 -0400 [thread overview]
Message-ID: <20230927111809-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <e8fbec0306d24cdab3398772a8301fc7@huawei.com>
On Tue, Sep 26, 2023 at 12:38:44PM +0000, Salil Mehta wrote:
> Hi Michael,
>
> > From: Michael S. Tsirkin <mst@redhat.com>
> > Sent: Tuesday, September 26, 2023 1:08 PM
> >
> > On Tue, Sep 26, 2023 at 07:26:40PM +0800, lixianglai wrote:
> > >
> > > Hi, Michael S. Tsirkin :
> > > > On Tue, Sep 26, 2023 at 05:54:26PM +0800, xianglai li wrote:
> > > > > ACPI GED shall be used to convey to the guest kernel about any cpu
> > hot-(un)plug
> > > > > events. Therefore, existing ACPI GED framework inside QEMU needs to
> > be enhanced
> > > > > to support CPU hot-(un)plug state and events.
> > > > >
> > > > > Co-authored-by: "Salil Mehta" <salil.mehta@opnsrc.net>
> > > > > Co-authored-by: "Salil Mehta" <salil.mehta@huawei.com>
> > > > This is not the way to handle multiple emails.
> > >
> > > Oh, sorry, I'll delete the first one.
> > >
> > > Thanks,
> > >
> > > Xianglai.
> >
> > Can you guys figure out together with Salil Mehta what's the
> > correct order to merge this? I can't figure out with dueling patches.
>
> We already have an agreed approach and Loongson folks will
> rebase from the common patch-set. There is no contention.
>
> Thanks
> Salil.
>
>
Great, thanks a lot!
--
MST
next prev parent reply other threads:[~2023-09-27 15:18 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-26 9:54 [PATCH v3 0/7] *** Adds CPU hot-plug support to Loongarch *** xianglai li
2023-09-26 9:54 ` [PATCH v3 1/7] Update ACPI GED framework to support vcpu hot-(un)plug xianglai li
2023-09-26 10:50 ` Salil Mehta via
2023-09-26 12:16 ` lixianglai
2023-09-26 11:02 ` Michael S. Tsirkin
2023-09-26 11:26 ` lixianglai
2023-09-26 12:08 ` Michael S. Tsirkin
2023-09-26 12:38 ` Salil Mehta via
2023-09-27 15:18 ` Michael S. Tsirkin [this message]
2023-09-26 12:03 ` Michael S. Tsirkin
2023-09-26 9:54 ` [PATCH v3 2/7] Update CPUs AML with cpu-(ctrl)dev change xianglai li
2023-09-26 10:49 ` Salil Mehta via
2023-09-26 11:12 ` Michael S. Tsirkin
2023-09-26 11:45 ` Salil Mehta via
2023-09-26 11:54 ` Michael S. Tsirkin
2023-09-26 12:03 ` Salil Mehta via
2023-09-26 12:07 ` Michael S. Tsirkin
2023-09-26 15:52 ` Salil Mehta via
2023-09-26 17:38 ` Michael S. Tsirkin
2023-09-26 12:49 ` lixianglai
2023-09-27 15:17 ` Michael S. Tsirkin
2023-09-28 1:36 ` lixianglai
2023-09-26 12:30 ` Daniel P. Berrangé
2023-09-27 15:16 ` Michael S. Tsirkin
2023-09-26 12:17 ` lixianglai
2023-09-26 9:54 ` [PATCH v3 3/7] Added CPU topology support for Loongarch xianglai li
2023-09-26 9:54 ` [PATCH v3 4/7] Optimize loongarch_irq_init function implementation xianglai li
2023-09-26 9:54 ` [PATCH v3 5/7] Add basic CPU hot-(un)plug support for Loongarch xianglai li
2023-09-26 9:54 ` [PATCH v3 6/7] Add support of *unrealize* for Loongarch cpu xianglai li
2023-09-26 9:54 ` [PATCH v3 7/7] Update the ACPI table for the Loongarch CPU xianglai li
2023-09-26 10:58 ` Salil Mehta via
2023-09-27 2:26 ` lixianglai
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=20230927111809-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=anisinha@redhat.com \
--cc=berrange@redhat.com \
--cc=david@redhat.com \
--cc=eduardo@habkost.net \
--cc=gaosong@loongson.cn \
--cc=imammedo@redhat.com \
--cc=lixianglai@loongson.cn \
--cc=maobibo@loongson.cn \
--cc=marcel.apfelbaum@gmail.com \
--cc=pbonzini@redhat.com \
--cc=peterx@redhat.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=salil.mehta@huawei.com \
--cc=salil.mehta@opnsrc.net \
--cc=shentey@gmail.com \
--cc=wangyanan55@huawei.com \
--cc=yangxiaojuan@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 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.