linux-kernel - [PATCH v5 0/2] let archs decide for vCPU ids

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 02 May 2016 19:42:05 +0200
From:	Greg Kurz <gkurz@...ux.vnet.ibm.com>
To:	Paolo Bonzini <pbonzini@...hat.com>, james.hogan@...tec.com,
	mingo@...hat.com
Cc:	linux-mips@...ux-mips.org, kvm@...r.kernel.org, rkrcmar@...hat.com,
	linux-kernel@...r.kernel.org,
	David Hildenbrand <dahi@...ux.vnet.ibm.com>,
	qemu-ppc@...gnu.org, Cornelia Huck <cornelia.huck@...ibm.com>,
	Paul Mackerras <paulus@...ba.org>,
	David Gibson <david@...son.dropbear.id.au>
Subject: [PATCH v5 0/2] let archs decide for vCPU ids

Architectures can freely choose vCPU ids as long as they stay below
KVM_MAX_VCPUS, which is the maximum number of vCPUS. This is a problem
for PowerPC where the ids have to be multiples of the number of threads
per core in the host: when the host is POWER8 with 8 threads per core,
we can only have KVM_MAX_VCPUS / 8 in the guest.

This series decouplates the vCPU id limit from the number of vCPUs.

The first patch is a cleanup I kept from v4.

The second patch adds KVM_MAX_VCPU_ID as suggested by Radim.

---

Greg Kurz (2):
      KVM: remove NULL return path for vcpu ids >= KVM_MAX_VCPUS
      kvm: introduce KVM_MAX_VCPU_ID

 Documentation/virtual/kvm/api.txt   |   10 ++++++++--
 arch/powerpc/include/asm/kvm_host.h |    2 ++
 arch/powerpc/kvm/powerpc.c          |    3 +++
 include/linux/kvm_host.h            |   11 ++++++++---
 include/uapi/linux/kvm.h            |    1 +
 virt/kvm/kvm_main.c                 |    2 +-
 6 files changed, 23 insertions(+), 6 deletions(-)

--
Greg