From: Chen Fan <chen.fan.fnst@cn.fujitsu.com>
To: Vasilis Liaskovitis <vasilis.liaskovitis@profitbricks.com>
Cc: "Igor Mammedov" <imammedo@redhat.com>,
qemu-devel@nongnu.org, "Andreas Färber" <afaerber@suse.de>
Subject: Re: [Qemu-devel] [RFC qom-cpu v4 09/10] piix4: implement function cpu_status_write() for vcpu ejection
Date: Wed, 27 Nov 2013 20:11:33 +0800 [thread overview]
Message-ID: <1385554293.27561.67.camel@G08FNSTD131468> (raw)
In-Reply-To: <20131125183806.GA16693@dhcp-192-168-178-175.profitbricks.localdomain>
On Mon, 2013-11-25 at 19:38 +0100, Vasilis Liaskovitis wrote:
> On Fri, Nov 22, 2013 at 09:02:27AM +0100, Vasilis Liaskovitis wrote:
> > Hi,
> >
> > On Wed, Oct 09, 2013 at 05:43:17PM +0800, Chen Fan wrote:
> > > When OS eject a vcpu (like: echo 1 > /sys/bus/acpi/devices/LNXCPUXX/eject),
> > > it will call acpi EJ0 method, the firmware will write the new cpumap, QEMU
> > > will know which vcpu need to be ejected.
> >
> > I think that the _EJ0 callback (CPEJ method in hw/i386/acpi-dsdt-cpu-hotplug.dsl)
> > currently does not write the new cpumap, it only sleeps. So cpu_state_write is
> > never called on ejection, and the cpu objects remain allocated in qemu. Is there
> > an updated version of the patchseries with a CPEJ that writes the new cpumap?
>
> oops, never mind. I missed your seabios patch mentioned in the head message,
> got it now.
>
Ok, thanks for your attention.
> thanks,
>
> - Vasilis
next prev parent reply other threads:[~2013-11-27 12:13 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-09 9:43 [Qemu-devel] [RFC qom-cpu v4 00/10] i386: add cpu hot remove support Chen Fan
2013-10-09 9:43 ` [Qemu-devel] [RFC qom-cpu v4 01/10] x86: move apic_state field from CPUX86State to X86CPU Chen Fan
2013-10-09 9:43 ` [Qemu-devel] [RFC qom-cpu v4 02/10] apic: remove redundant variable 'apic_no' from apic_init_common() Chen Fan
2013-10-09 9:43 ` [Qemu-devel] [RFC qom-cpu v4 03/10] apic: remove local_apics array and using CPU_FOREACH instead Chen Fan
2013-10-09 9:43 ` [Qemu-devel] [RFC qom-cpu v4 04/10] x86: add x86_cpu_unrealizefn() for cpu apic remove Chen Fan
2013-10-09 9:43 ` [Qemu-devel] [RFC qom-cpu v4 05/10] qmp: add 'cpu-del' command support Chen Fan
2013-11-27 14:00 ` Eric Blake
2013-11-28 1:14 ` Chen Fan
2013-10-09 9:43 ` [Qemu-devel] [RFC qom-cpu v4 06/10] qom cpu: rename variable 'cpu_added_notifier' to 'cpu_hotplug_notifier' Chen Fan
2013-10-09 9:43 ` [Qemu-devel] [RFC qom-cpu v4 07/10] qom cpu: add UNPLUG cpu notifier support Chen Fan
2013-10-09 9:43 ` [Qemu-devel] [RFC qom-cpu v4 08/10] i386: implement pc interface pc_hot_del_cpu() Chen Fan
2013-10-09 9:43 ` [Qemu-devel] [RFC qom-cpu v4 09/10] piix4: implement function cpu_status_write() for vcpu ejection Chen Fan
2013-11-22 8:02 ` Vasilis Liaskovitis
2013-11-25 18:38 ` Vasilis Liaskovitis
2013-11-27 12:11 ` Chen Fan [this message]
2013-10-09 9:43 ` [Qemu-devel] [RFC qom-cpu v4 10/10] cpus: reclaim allocated vCPU objects Chen Fan
2013-11-28 14:48 ` Igor Mammedov
2013-12-04 2:28 ` Chen Fan
2013-11-28 14:41 ` [Qemu-devel] [RFC qom-cpu v4 00/10] i386: add cpu hot remove support Igor Mammedov
2013-12-04 2:15 ` Chen Fan
2013-12-04 15:42 ` Igor Mammedov
2013-12-05 1:08 ` Chen Fan
2013-12-19 8:10 ` Chen Fan
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=1385554293.27561.67.camel@G08FNSTD131468 \
--to=chen.fan.fnst@cn.fujitsu.com \
--cc=afaerber@suse.de \
--cc=imammedo@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=vasilis.liaskovitis@profitbricks.com \
/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 NNTP newsgroup(s).