From: Linu Cherian
v3 -> v4:
- Add missing commit messages in patches 1 and 3
v2 -> v3:
- Added documentation for KVM_CAP_NR_MEMSLOTS
- Removed KVM_PRIVATE_MEM_SLOTS which is unused
- KVM_USER_MEM_SLOTS changed to 512 from 508
v1 -> v2:
- Enabling KVM_CAP_NR_MEMSLOTS
From: Linu Cherian
arm/arm64 architecture doesnt use private memslots, hence removing
KVM_PRIVATE_MEM_SLOTS macro definition.
Signed-off-by: Linu Cherian
---
arch/arm/include/asm/kvm_host.h | 1 -
arch/arm64/include/asm/kvm_host.h | 1 -
2
From: Linu Cherian
Having only 32 memslots is a real constraint for the maximum
number of PCI devices that can be assigned to a single guest.
Assuming each PCI device/virtual function having two memory BAR
regions, we could assign only 15 devices/virtual functions to a
From: Linu Cherian
Return KVM_USER_MEM_SLOTS for userspace capability query on
NR_MEMSLOTS.
Signed-off-by: Linu Cherian
---
arch/arm/kvm/arm.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/arch/arm/kvm/arm.c b/arch/arm/kvm/arm.c
index
From: Linu Cherian
Add documentation for KVM_CAP_NR_MEMSLOTS capability.
Signed-off-by: Linu Cherian
---
Documentation/virtual/kvm/api.txt | 4
1 file changed, 4 insertions(+)
diff --git a/Documentation/virtual/kvm/api.txt
From: Linu Cherian
Return KVM_USER_MEM_SLOTS for userspace capability query on
NR_MEMSLOTS.
Signed-off-by: Linu Cherian
---
arch/arm/kvm/arm.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/arch/arm/kvm/arm.c b/arch/arm/kvm/arm.c
index
From: Linu Cherian
Signed-off-by: Linu Cherian
---
arch/arm/include/asm/kvm_host.h | 1 -
arch/arm64/include/asm/kvm_host.h | 1 -
2 files changed, 2 deletions(-)
diff --git a/arch/arm/include/asm/kvm_host.h b/arch/arm/include/asm/kvm_host.h
From: Linu Cherian
Signed-off-by: Linu Cherian
---
Documentation/virtual/kvm/api.txt | 4
1 file changed, 4 insertions(+)
diff --git a/Documentation/virtual/kvm/api.txt
b/Documentation/virtual/kvm/api.txt
index 03145b7..7b82f1c 100644
From: Linu Cherian
Having only 32 memslots is a real constraint for the maximum
number of PCI devices that can be assigned to a single guest.
Assuming each PCI device/virtual function having two memory BAR
regions, we could assign only 15 devices/virtual functions to a
From: Linu Cherian
v2 -> v3:
- Added documentation for KVM_CAP_NR_MEMSLOTS
- Removed KVM_PRIVATE_MEM_SLOTS which is unused
- KVM_USER_MEM_SLOTS changed to 512 from 508
v1 -> v2:
- Enabling KVM_CAP_NR_MEMSLOTS for arm/arm64 moved to separate patch.
- Updated commit
From: Linu Cherian
Having only 32 memslots is a real constraint for the maximum
number of PCI devices that can be assigned to a single guest.
Assuming each PCI device/virtual function having two memory BAR
regions, we could assign only 15 devices/virtual functions to a
From: Linu Cherian
Return KVM_USER_MEM_SLOTS for userspace capability query on
NR_MEMSLOTS.
Signed-off-by: Linu Cherian
---
arch/arm/kvm/arm.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/arch/arm/kvm/arm.c b/arch/arm/kvm/arm.c
index
From: Linu Cherian
v1 -> v2:
- Enabling KVM_CAP_NR_MEMSLOTS for arm/arm64 moved to separate patch.
- Updated commit message so that what is reported to userspace is explicit.
Linu Cherian (2):
KVM: arm/arm64: Enable KVM_CAP_NR_MEMSLOTS on arm/arm64
KVM: arm64:
From: Linu Cherian
Having only 32 memslots is a real constraint for the maximum number of
PCI devices that can be assigned to a single guest. Assuming each PCI
device/virtual function having two memory BAR regions, we could assign
only 15 devices/virtual functions to a
14 matches
Mail list logo