linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: cdall@linaro.org (Christoffer Dall)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V2 1/2] KVM: arm/arm64: Enable KVM_CAP_NR_MEMSLOTS on arm/arm64
Date: Thu, 23 Feb 2017 11:10:27 +0100	[thread overview]
Message-ID: <20170223101027.GA1409@cbox> (raw)
In-Reply-To: <1486538141-30627-2-git-send-email-linucherian@gmail.com>

On Wed, Feb 08, 2017 at 12:45:40PM +0530, linucherian at gmail.com wrote:
> From: Linu Cherian <linu.cherian@cavium.com>
> 
> Return KVM_USER_MEM_SLOTS for userspace capability query on
> NR_MEMSLOTS.

This feature seems to be undocumented (I cannot find it in
Documentation/virtual/kvm/api.txt).

Can we add documentation for it?

What does user space do currently without this capability?  Does it just
rely on some default?

Thanks,
-Christoffer

> 
> Signed-off-by: Linu Cherian <linu.cherian@cavium.com>
> ---
>  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 9d74464..b64b47f 100644
> --- a/arch/arm/kvm/arm.c
> +++ b/arch/arm/kvm/arm.c
> @@ -221,6 +221,9 @@ int kvm_vm_ioctl_check_extension(struct kvm *kvm, long ext)
>  	case KVM_CAP_MAX_VCPUS:
>  		r = KVM_MAX_VCPUS;
>  		break;
> +	case KVM_CAP_NR_MEMSLOTS:
> +		r = KVM_USER_MEM_SLOTS;
> +		break;
>  	case KVM_CAP_MSI_DEVID:
>  		if (!kvm)
>  			r = -EINVAL;
> -- 
> 1.9.1
> 

  reply	other threads:[~2017-02-23 10:10 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-08  7:15 [PATCH V2 0/2] KVM: arm64: Increase number of user memslots linucherian at gmail.com
2017-02-08  7:15 ` [PATCH V2 1/2] KVM: arm/arm64: Enable KVM_CAP_NR_MEMSLOTS on arm/arm64 linucherian at gmail.com
2017-02-23 10:10   ` Christoffer Dall [this message]
2017-02-26  4:30     ` Linu Cherian
2017-02-08  7:15 ` [PATCH V2 2/2] KVM: arm64: Increase number of user memslots to 508 linucherian at gmail.com
2017-02-23 10:14   ` Christoffer Dall
2017-02-26  7:06     ` Linu Cherian
2017-03-02 12:29       ` Christoffer Dall

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=20170223101027.GA1409@cbox \
    --to=cdall@linaro.org \
    --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).