[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] [PATCH v1 0/4] prebuild cpu QOM tree /machine/node/sock
From: |
Eric Blake |
Subject: |
Re: [Qemu-devel] [PATCH v1 0/4] prebuild cpu QOM tree /machine/node/socket/core ->link-cpu |
Date: |
Wed, 19 Mar 2014 06:00:03 -0600 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0 |
On 03/19/2014 02:53 AM, Chen Fan wrote:
> at present, after hotplug a discontinuous cpu id on source, then done
> migration,
> on target, it will fail to add the unoccupied cpu id which was skipped at
> source,
> this cause is on target Qemu prebuild CPU with continuous cpu_index. so after
> migration, the cpu infrastructure bewteen source and target are different.
>
> I suppose we could use apic_id as instance_id which was used at registering
> vmstate
> when create cpu. on target, we prebuild the specified cpu topology using
> comand line:
> -device /machine/node[]/socket[]/core[]/cpu[], then migration, we could
> keep the same
> cpu infrastructure on both side.
>
> RFC:
> V4: rename CpuTopoInfo to X86CPUTopoInfo. and move cpu_exsit() to
> pc_new_cpu().
>
> V3: get rid of thread object and tie link<cpu> to <core> directly. and
> prebuild full
> core[] and thread[] as init socket[] according to smp_cores and smp_threads.
>
> TODO:
> 1. add cpu "path" property which used for specifying the QOM path.
> 2. add -device cpu-foo.path supported.
> 3. then we could introduce hot-remove cpu probably.
>
> I don't know wether this way is right or not. pls tell me. :)
When sending a cover letter for a new revision of a patch series, we
generally do NOT use In-Reply-To headers, but instead send it as a new
thread. Patches are harder to see when they are buried as a reply to
another thread.
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
signature.asc
Description: OpenPGP digital signature
- Re: [Qemu-devel] [RFC v3 2/3] i386: use CpuTopoInfo instead apic_id as argument for pc_new_cpu(), (continued)
- Re: [Qemu-devel] [RFC v3 2/3] i386: use CpuTopoInfo instead apic_id as argument for pc_new_cpu(), Chen Fan, 2014/03/12
- [Qemu-devel] [RFC v4 0/3] prebuild cpu QOM tree /machine/node/socket/core ->link-cpu, Chen Fan, 2014/03/12
- [Qemu-devel] [RFC v4 1/3] cpu: introduce CpuTopoInfo structure for argument simplification, Chen Fan, 2014/03/12
- Re: [Qemu-devel] [RFC v4 1/3] cpu: introduce CpuTopoInfo structure for argument simplification, Eduardo Habkost, 2014/03/12
- [Qemu-devel] [PATCH v1 0/4] prebuild cpu QOM tree /machine/node/socket/core ->link-cpu, Chen Fan, 2014/03/19
- [Qemu-devel] [PATCH v1 2/4] i386: use CpuTopoInfo instead apic_id as argument for pc_new_cpu(), Chen Fan, 2014/03/19
- Re: [Qemu-devel] [PATCH v1 2/4] i386: use CpuTopoInfo instead apic_id as argument for pc_new_cpu(), Eduardo Habkost, 2014/03/19
- [Qemu-devel] [PATCH v1 3/4] topo unit-test: update Unit tests to test-x86-cpuid.c, Chen Fan, 2014/03/19
- [Qemu-devel] [PATCH v1 1/4] cpu: introduce CpuTopoInfo structure for argument simplification, Chen Fan, 2014/03/19
- [Qemu-devel] [PATCH v1 4/4] i386: introduce cpu QOM hierarchy tree, Chen Fan, 2014/03/19
- Re: [Qemu-devel] [PATCH v1 0/4] prebuild cpu QOM tree /machine/node/socket/core ->link-cpu,
Eric Blake <=
- Re: [Qemu-devel] [PATCH v1 0/4] prebuild cpu QOM tree /machine/node/socket/core ->link-cpu, Chen Fan, 2014/03/19
- [Qemu-devel] [RFC v4 3/3] i386: introduce cpu QOM hierarchy tree, Chen Fan, 2014/03/12
- [Qemu-devel] [RFC v4 2/3] i386: use CpuTopoInfo instead apic_id as argument for pc_new_cpu(), Chen Fan, 2014/03/12
- Re: [Qemu-devel] [RFC v4 2/3] i386: use CpuTopoInfo instead apic_id as argument for pc_new_cpu(), Eduardo Habkost, 2014/03/12
- [Qemu-devel] [RFC v3 3/3] i386: introduce cpu QOM hierarchy tree, chen.fan.fnst, 2014/03/11
[Qemu-devel] [RFC v2 2/2] i386: introduce cpu QOM hierarchy tree, Chen Fan, 2014/03/04