From: linucherian@gmail.com (linucherian at gmail.com)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V3 0/4] KVM: arm64: Increase number of user memslots
Date: Tue, 7 Mar 2017 11:22:40 +0530 [thread overview]
Message-ID: <1488865964-17346-1-git-send-email-linucherian@gmail.com> (raw)
From: Linu Cherian <linu.cherian@cavium.com>
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 message so that what is reported to userspace is explicit.
Linu Cherian (4):
KVM: Add documentation for KVM_CAP_NR_MEMSLOTS
KVM: arm/arm64: Enable KVM_CAP_NR_MEMSLOTS on arm/arm64
KVM: arm/arm64: Remove KVM_PRIVATE_MEM_SLOTS definition that are
unused
KVM: arm64: Increase number of user memslots to 512
Documentation/virtual/kvm/api.txt | 4 ++++
arch/arm/include/asm/kvm_host.h | 1 -
arch/arm/kvm/arm.c | 3 +++
arch/arm64/include/asm/kvm_host.h | 3 +--
4 files changed, 8 insertions(+), 3 deletions(-)
--
1.9.1
next reply other threads:[~2017-03-07 5:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-07 5:52 linucherian at gmail.com [this message]
2017-03-07 5:52 ` [PATCH V3 1/4] KVM: Add documentation for KVM_CAP_NR_MEMSLOTS linucherian at gmail.com
2017-03-07 14:58 ` Christoffer Dall
2017-03-07 5:52 ` [PATCH V3 2/4] KVM: arm/arm64: Enable KVM_CAP_NR_MEMSLOTS on arm/arm64 linucherian at gmail.com
2017-03-07 5:52 ` [PATCH V3 3/4] KVM: arm/arm64: Remove KVM_PRIVATE_MEM_SLOTS definition that are unused linucherian at gmail.com
2017-03-07 14:58 ` Marc Zyngier
2017-03-07 5:52 ` [PATCH V3 4/4] KVM: arm64: Increase number of user memslots to 512 linucherian at gmail.com
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1488865964-17346-1-git-send-email-linucherian@gmail.com \
--to=linucherian@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).