Hi,
Am 03.05.2013 15:50, schrieb Jason J. Herne:
> I've done some investigating into using the device_add hmp/qmp command
> to support hot-plugging cpus on S390. The alternative suggestion was to
> simply use a new cpu_add hmp/qmp command.
A cpu-add QMP command has been merged by now. Using it w
On Fri, 03 May 2013 09:50:50 -0400
"Jason J. Herne" wrote:
> I've done some investigating into using the device_add hmp/qmp command
> to support hot-plugging cpus on S390. The alternative suggestion was to
> simply use a new cpu_add hmp/qmp command.
>
> device_add accepts all of the same opti
I've done some investigating into using the device_add hmp/qmp command
to support hot-plugging cpus on S390. The alternative suggestion was to
simply use a new cpu_add hmp/qmp command.
device_add accepts all of the same options as the -device command line
parameter takes. This would imply th
On Fri, Apr 19, 2013 at 09:13:32PM +0200, Christian Borntraeger wrote:
> On 19/04/13 15:16, Andreas Färber wrote:
> [...]
> >>> Background is that for x86 we currently have a flat CPU core/thread
> >>> namespace but would need to deal with sockets, cores and threads to get
> >>> topologies right. I
On 19/04/13 15:16, Andreas Färber wrote:
[...]
>>> Background is that for x86 we currently have a flat CPU core/thread
>>> namespace but would need to deal with sockets, cores and threads to get
>>> topologies right. I assume there are no such issues on s390x, so that
>>> the vCPU to CPUState mappi
On Fri, 19 Apr 2013 15:16:36 +0200
Andreas Färber wrote:
> Am 19.04.2013 09:51, schrieb Jens Freimann:
> > On Wed, Apr 17, 2013 at 08:06:37PM +0200, Andreas Färber wrote:
> >> Hi Jens,
> >>
> >> Am 03.04.2013 08:42, schrieb Jens Freimann:
> >>> this is what our approach to CPU hotplug looks like.
Am 19.04.2013 09:51, schrieb Jens Freimann:
> On Wed, Apr 17, 2013 at 08:06:37PM +0200, Andreas Färber wrote:
>> Hi Jens,
>>
>> Am 03.04.2013 08:42, schrieb Jens Freimann:
>>> this is what our approach to CPU hotplug looks like.
>>> With respect to Igor's CPU hotplug series, how should we proceed?
On Wed, Apr 17, 2013 at 08:06:37PM +0200, Andreas Färber wrote:
> Hi Jens,
>
> Am 03.04.2013 08:42, schrieb Jens Freimann:
> > this is what our approach to CPU hotplug looks like.
> > With respect to Igor's CPU hotplug series, how should we proceed?
> > Should we change the interface to
> > qemu
On Wed, Apr 17, 2013 at 08:06:37PM +0200, Andreas Färber wrote:
> Hi Jens,
>
> Am 03.04.2013 08:42, schrieb Jens Freimann:
> > this is what our approach to CPU hotplug looks like.
> > With respect to Igor's CPU hotplug series, how should we proceed?
> > Should we change the interface to
> > qemu
Hi Jens,
Am 03.04.2013 08:42, schrieb Jens Freimann:
> this is what our approach to CPU hotplug looks like.
> With respect to Igor's CPU hotplug series, how should we proceed?
> Should we change the interface to
> qemu_system_cpu_add_notifier/qemu_system_cpu_hotplug_request/cpu-add etc?
I am wo
Hi all,
this is what our approach to CPU hotplug looks like.
With respect to Igor's CPU hotplug series, how should we proceed?
Should we change the interface to
qemu_system_cpu_add_notifier/qemu_system_cpu_hotplug_request/cpu-add etc?
Feedback regarding the non-API part is also highly welcome!
11 matches
Mail list logo
