[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-ppc] [PATCH v2 0/6] Fix migration issues with arbitrary cpu-ho
From: |
Eduardo Habkost |
Subject: |
Re: [Qemu-ppc] [PATCH v2 0/6] Fix migration issues with arbitrary cpu-hot(un)plug |
Date: |
Tue, 26 Jul 2016 15:35:55 -0300 |
User-agent: |
Mutt/1.6.1 (2016-04-27) |
On Mon, Jul 25, 2016 at 11:59:18AM +0200, Igor Mammedov wrote:
[...]
> Igor Mammedov (6):
> exec: reduce CONFIG_USER_ONLY ifdeffenery
> exec: don't use cpu_index to detect if cpu_exec_init()'s been called
> for cpu
> exec: set cpu_index only if it's not been explictly set
> qdev: fix object reference leak in case device.realize() fails
> pc: init CPUState->cpu_index with index in possible_cpus[]
> Revert "pc: Enforce adding CPUs contiguously and removing them in
> opposite order"
Applied to x86-next. Thanks!
Subject line of patch 2/6 was changed to:
"exec: Don't use cpu_index to detect if cpu_exec_init()'s been called"
to make it shorter.
--
Eduardo
- [Qemu-ppc] [PATCH v2 3/6] exec: set cpu_index only if it's not been explictly set, (continued)
- [Qemu-ppc] [PATCH v2 3/6] exec: set cpu_index only if it's not been explictly set, Igor Mammedov, 2016/07/25
- [Qemu-ppc] [PATCH v2 4/6] qdev: fix object reference leak in case device.realize() fails, Igor Mammedov, 2016/07/25
- [Qemu-ppc] [PATCH v2 6/6] Revert "pc: Enforce adding CPUs contiguously and removing them in opposite order", Igor Mammedov, 2016/07/25
- [Qemu-ppc] [PATCH v2 5/6] pc: init CPUState->cpu_index with index in possible_cpus[], Igor Mammedov, 2016/07/25
- Re: [Qemu-ppc] [PATCH v2 0/6] Fix migration issues with arbitrary cpu-hot(un)plug, David Gibson, 2016/07/25
- Re: [Qemu-ppc] [PATCH v2 0/6] Fix migration issues with arbitrary cpu-hot(un)plug, David Gibson, 2016/07/26
- Re: [Qemu-ppc] [PATCH v2 0/6] Fix migration issues with arbitrary cpu-hot(un)plug, Michael S. Tsirkin, 2016/07/26
- Re: [Qemu-ppc] [PATCH v2 0/6] Fix migration issues with arbitrary cpu-hot(un)plug,
Eduardo Habkost <=