On 11/24/2016 04:55 AM, Nitesh Konkar wrote:
> Currently when the vcpu placement is static
> and cpuset is not specified, CPU Affinity
> under virsh emulatorpin shows 0..CPUMAX. This
> patchset will result in display of only
> online CPU's under CPU Affinity on linux.
>
> Signed-off-by: Nitesh
On 06.12.2016 13:10, Peter Krempa wrote:
> On Tue, Dec 06, 2016 at 13:01:48 +0100, Viktor Mihajlovski wrote:
>> On 06.12.2016 12:33, Peter Krempa wrote:
>>> On Fri, Nov 25, 2016 at 14:53:07 +0530, Nitesh Konkar wrote:
>
> [...]
>
>>> Additionally we historically treat the "all bits set" cpu map
On Tue, Dec 06, 2016 at 13:01:48 +0100, Viktor Mihajlovski wrote:
> On 06.12.2016 12:33, Peter Krempa wrote:
> > On Fri, Nov 25, 2016 at 14:53:07 +0530, Nitesh Konkar wrote:
[...]
> > Additionally we historically treat the "all bits set" cpu map as
> > that there is no pinning configured. This
On 06.12.2016 12:33, Peter Krempa wrote:
> On Fri, Nov 25, 2016 at 14:53:07 +0530, Nitesh Konkar wrote:
>> Currently when the vcpu placement is static and cpuset is not
>> specified, CPU Affinity under virsh emulatorpin shows 0..CPUMAX.
>> This patchset will result in display of only online CPU's
On Fri, Nov 25, 2016 at 14:53:07 +0530, Nitesh Konkar wrote:
> Currently when the vcpu placement is static
> and cpuset is not specified, CPU Affinity
> under virsh emulatorpin shows 0..CPUMAX. This
> patchset will result in display of only
> online CPU's under CPU Affinity on linux.
>
>
Currently when the vcpu placement is static
and cpuset is not specified, CPU Affinity
under virsh emulatorpin shows 0..CPUMAX. This
patchset will result in display of only
online CPU's under CPU Affinity on linux.
Signed-off-by: Nitesh Konkar
---
Currently when the vcpu placement is static
and cpuset is not specified, CPU Affinity
under virsh emulatorpin shows 0..CPUMAX. This
patchset will result in display of only
online CPU's under CPU Affinity on linux.
Signed-off-by: Nitesh Konkar
---