qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Chen Fan <chen.fan.fnst@cn.fujitsu.com>
To: "Andreas Färber" <afaerber@suse.de>,
	"Gu Zheng" <guz.fnst@cn.fujitsu.com>
Cc: Zhu Guihua <zhugh.fnst@cn.fujitsu.com>,
	Bharata B Rao <bharata@linux.vnet.ibm.com>,
	qemu-devel@nongnu.org, tangchen@cn.fujitsu.com,
	isimatu.yasuaki@jp.fujitsu.com, anshul.makkar@profitbricks.com,
	imammedo@redhat.com
Subject: Re: [Qemu-devel] [PATCH v4 00/10] cpu: add device_add foo-x86_64-cpu support
Date: Thu, 26 Feb 2015 18:02:36 +0800	[thread overview]
Message-ID: <54EEEF3C.1020903@cn.fujitsu.com> (raw)
In-Reply-To: <54EEE8E0.40301@suse.de>


On 02/26/2015 05:35 PM, Andreas Färber wrote:
> Hi,
>
> Am 25.02.2015 um 10:58 schrieb Chen Fan:
>> On 02/25/2015 12:56 AM, Andreas Färber wrote:
>>> Am 24.02.2015 um 02:25 schrieb Gu Zheng:
>>>> The issues you commented in the previous version have been fixed in
>>>> this one.
>>> What I have repeatedly rejected is "device_add foo-x86_64-cpu". This is
>>> still in 00/10 and 09/10. Most of the actual changes however do look to
>>> be going in the right direction of making 'realize' work as expected for
>>> foo-x86_64-cpu.
>>>
>>> As for the socket-based device_add I mentioned, I had pushed a work
>>> branch qom-cpu-x86 and had some off-list discussions for some of the
>>> other architectures but did not submit it as an RFC yet. What I am still
>>> working on is dynamic properties to allocate cores (threads TBD) for
>>> "device_add x86_64-cpu-socket,cores=n".
>> Can you explain all your thoughts about cpu hotplug feature with
>> socket-based,
>> or how goals do you want to see?
> Basically I am implementing Anthony's suggestion from a year or two
> back, that is moving towards using real building blocks such as
> Xeon-E5-4242 as shortcut for a 6-core, 2-HT device, ultimately replacing
> -cpu. Think of what can be plugged in real servers - a socket is atomic
> in reality, you can't add cores or hyperthreads dynamically. And the QOM
> realize model then forces me to use child<> properties inside the socket
> object for consistent recursive processing.
yes, I agree with you.

but the existed command 'cpu-add' is adding one logic processor each time.
it will cause compatibility with the socket-based cpu device. and what
do you think to solve this problem ?

Thanks,
Chen

>
> Regards,
> Andreas
>
>> and what is the status of "device_add x86_64-cpu-socket" ?
>>
>> after that, I think we can do somethings to help you to achieve your ideas.
>>
>> Thanks,
>> Chen
>>
>>>> Could you please help to review it?
>>> Will get to it Friday earliest.
>>>
>>> Regards,
>>> Andreas
>>>
>

  reply	other threads:[~2015-02-26 10:09 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-13 10:25 [Qemu-devel] [PATCH v4 00/10] cpu: add device_add foo-x86_64-cpu support Zhu Guihua
2015-02-13 10:25 ` [Qemu-devel] [PATCH v4 01/10] cpu/apic: drop icc bus/bridge/ Zhu Guihua
2015-03-05 18:17   ` Eduardo Habkost
2015-03-06  3:10     ` Chen Fan
2015-03-06  9:35   ` Igor Mammedov
2015-02-13 10:25 ` [Qemu-devel] [PATCH v4 02/10] icc_bus: remove icc related files Zhu Guihua
2015-02-13 10:25 ` [Qemu-devel] [PATCH v4 03/10] cpu: introduce CpuTopoInfo structure for argument simplification Zhu Guihua
2015-02-13 10:25 ` [Qemu-devel] [PATCH v4 04/10] cpu: introduce get_compat_arch_id() method and override it for X86CPU Zhu Guihua
2015-02-13 10:25 ` [Qemu-devel] [PATCH v4 05/10] qom/cpu: move register_vmstate to common CPUClass.realizefn Zhu Guihua
2015-03-05 18:32   ` Eduardo Habkost
2015-03-06  8:53   ` Igor Mammedov
2015-03-06  9:31     ` Chen Fan
2015-02-13 10:25 ` [Qemu-devel] [PATCH v4 06/10] qom/cpu: move apic vmstate register into x86_cpu_apic_realize Zhu Guihua
2015-02-13 10:25 ` [Qemu-devel] [PATCH v4 07/10] monitor: use cc->get_arch_id as the cpu index Zhu Guihua
2015-02-13 10:25 ` [Qemu-devel] [PATCH v4 08/10] acpi: introduce acpi_send_gpe_event() Zhu Guihua
2015-02-13 10:25 ` [Qemu-devel] [PATCH v4 09/10] cpu: add device_add foo-x86_64-cpu support Zhu Guihua
2015-03-05 18:43   ` Eduardo Habkost
2015-02-13 10:25 ` [Qemu-devel] [PATCH v4 10/10] i386/cpu: add instance finalize callback Zhu Guihua
2015-02-24  1:25 ` [Qemu-devel] [PATCH v4 00/10] cpu: add device_add foo-x86_64-cpu support Gu Zheng
2015-02-24 16:56   ` Andreas Färber
2015-02-25  9:58     ` Chen Fan
2015-02-26  9:35       ` Andreas Färber
2015-02-26 10:02         ` Chen Fan [this message]
2015-02-26  4:42     ` Bharata B Rao
2015-02-26  9:08       ` Andreas Färber
2015-03-13  6:17 ` Zhu Guihua

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=54EEEF3C.1020903@cn.fujitsu.com \
    --to=chen.fan.fnst@cn.fujitsu.com \
    --cc=afaerber@suse.de \
    --cc=anshul.makkar@profitbricks.com \
    --cc=bharata@linux.vnet.ibm.com \
    --cc=guz.fnst@cn.fujitsu.com \
    --cc=imammedo@redhat.com \
    --cc=isimatu.yasuaki@jp.fujitsu.com \
    --cc=qemu-devel@nongnu.org \
    --cc=tangchen@cn.fujitsu.com \
    --cc=zhugh.fnst@cn.fujitsu.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).