[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] [PATCH v4 05/16] pc: enforce adding CPUs contiguously a
|
From: |
Eduardo Habkost |
|
Subject: |
Re: [Qemu-devel] [PATCH v4 05/16] pc: enforce adding CPUs contiguously and removing them in opposit order |
|
Date: |
Tue, 19 Jul 2016 09:30:30 -0300 |
|
User-agent: |
Mutt/1.6.1 (2016-04-27) |
On Tue, Jul 19, 2016 at 02:25:19PM +0200, Igor Mammedov wrote:
> On Mon, 18 Jul 2016 15:05:37 -0600
> Eric Blake <address@hidden> wrote:
>
> > On 07/14/2016 10:54 AM, Igor Mammedov wrote:
> >
> > s/opposit/opposite/ in the subject line, but it's already long. I wonder
> > if you can go shorter, with:
> >
> > pc: enforce CPU add/remove in contiguous order
> >
> > > it will still allow us to use cpu_index as migration instance_id
> > > since when CPUs are added contiguously (from the first to the last)
> > > and removed in opposite order, cpu_index stays stable and it's
> > > reproducable on destination side.
> >
> > s/reproducable/reproducible/
> Eduardo could you fix it up when applying or should I respin it?
I can fix it.
--
Eduardo
- Re: [Qemu-devel] [PATCH v4 04/16] pc: forbid BSP removal, (continued)
[Qemu-devel] [PATCH v4 06/16] pc: cpu: allow device_add to be used with x86 cpu, Igor Mammedov, 2016/07/14
[Qemu-devel] [PATCH v4 07/16] pc: implement query-hotpluggable-cpus callback, Igor Mammedov, 2016/07/14
[Qemu-devel] [PATCH v4 09/16] apic: drop APICCommonState.idx and use APIC ID as index in local_apics[], Igor Mammedov, 2016/07/14
[Qemu-devel] [PATCH v4 08/16] apic: move MAX_APICS check to 'apic' class, Igor Mammedov, 2016/07/14
[Qemu-devel] [PATCH v4 11/16] (kvm)apic: add unrealize callbacks, Igor Mammedov, 2016/07/14
[Qemu-devel] [PATCH v4 10/16] apic: kvm-apic: fix crash due to access to freed memory region, Igor Mammedov, 2016/07/14
[Qemu-devel] [PATCH v4 13/16] target-i386: cpu: do not ignore error and fix apic parent, Igor Mammedov, 2016/07/14