On Sat, Mar 21, 2015 at 8:28 PM, Alexander Graf ag...@suse.de wrote:
On 20.03.15 16:51, Bharata B Rao wrote:
On Fri, Mar 20, 2015 at 12:34:18PM +0100, Alexander Graf wrote:
On 20.03.15 12:26, Paul Mackerras wrote:
On Fri, Mar 20, 2015 at 12:01:32PM +0100, Alexander Graf wrote:
On
On 23.03.15 08:50, Bharata B Rao wrote:
On Sat, Mar 21, 2015 at 8:28 PM, Alexander Graf ag...@suse.de wrote:
On 20.03.15 16:51, Bharata B Rao wrote:
On Fri, Mar 20, 2015 at 12:34:18PM +0100, Alexander Graf wrote:
On 20.03.15 12:26, Paul Mackerras wrote:
On Fri, Mar 20, 2015 at
From: Bharata B Rao bhar...@linux.vnet.ibm.com
Since KVM isn't equipped to handle closure of vcpu fd from userspace(QEMU)
correctly, certain work arounds have to be employed to allow reuse of
vcpu array slot in KVM during cpu hot plug/unplug from guest. One such
proposed workaround is to park the
On 20.03.15 10:39, Paul Mackerras wrote:
From: Bharata B Rao bhar...@linux.vnet.ibm.com
Since KVM isn't equipped to handle closure of vcpu fd from userspace(QEMU)
correctly, certain work arounds have to be employed to allow reuse of
vcpu array slot in KVM during cpu hot plug/unplug from
On 20.03.15 12:26, Paul Mackerras wrote:
On Fri, Mar 20, 2015 at 12:01:32PM +0100, Alexander Graf wrote:
On 20.03.15 10:39, Paul Mackerras wrote:
From: Bharata B Rao bhar...@linux.vnet.ibm.com
Since KVM isn't equipped to handle closure of vcpu fd from userspace(QEMU)
correctly, certain
On Fri, Mar 20, 2015 at 12:34:18PM +0100, Alexander Graf wrote:
On 20.03.15 12:26, Paul Mackerras wrote:
On Fri, Mar 20, 2015 at 12:01:32PM +0100, Alexander Graf wrote:
On 20.03.15 10:39, Paul Mackerras wrote:
From: Bharata B Rao bhar...@linux.vnet.ibm.com
Since KVM isn't
