kvm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christian Borntraeger <borntraeger@de.ibm.com>
To: Alexander Graf <agraf@suse.de>,
	Marcelo Tosatti <mtosatti@redhat.com>,
	Gleb Natapov <gleb@kernel.org>
Cc: Paolo Bonzini <pbonzini@redhat.com>, KVM <kvm@vger.kernel.org>,
	linux-s390 <linux-s390@vger.kernel.org>,
	Cornelia Huck <cornelia.huck@de.ibm.com>,
	Dominik Dingel <dingel@linux.vnet.ibm.com>
Subject: Re: [PATCH 1/3] kvm: s390: Per-vm kvm device controls
Date: Thu, 10 Apr 2014 13:33:55 +0200	[thread overview]
Message-ID: <534681A3.2080408@de.ibm.com> (raw)
In-Reply-To: <534680A7.7090404@suse.de>

On 10/04/14 13:29, Alexander Graf wrote:
> 
> On 10.04.14 13:16, Christian Borntraeger wrote:
>> From: Dominik Dingel <dingel@linux.vnet.ibm.com>
>>
>> We sometimes need to get/set attributes specific to a virtual machine
>> and so need something else than ONE_REG.
>>
>> Let's copy the KVM_DEVICE approach, and define the respective ioctls
>> for the vm file descriptor.
>>
>> Signed-off-by: Dominik Dingel <dingel@linux.vnet.ibm.com>
>> Signed-off-by: Christian Borntraeger <borntraeger@de.ibm.com>
>> ---
>>   Documentation/virtual/kvm/api.txt        |  8 ++---
>>   Documentation/virtual/kvm/devices/vm.txt |  6 ++++
>>   arch/s390/kvm/kvm-s390.c                 | 54 ++++++++++++++++++++++++++++++++
>>   include/uapi/linux/kvm.h                 |  1 +
>>   4 files changed, 65 insertions(+), 4 deletions(-)
>>   create mode 100644 Documentation/virtual/kvm/devices/vm.txt
>>
>> diff --git a/Documentation/virtual/kvm/api.txt b/Documentation/virtual/kvm/api.txt
>> index c24211d..f69731a 100644
>> --- a/Documentation/virtual/kvm/api.txt
>> +++ b/Documentation/virtual/kvm/api.txt
>> @@ -2314,8 +2314,8 @@ struct kvm_create_device {
>>     4.80 KVM_SET_DEVICE_ATTR/KVM_GET_DEVICE_ATTR
>>   -Capability: KVM_CAP_DEVICE_CTRL
>> -Type: device ioctl
>> +Capability: KVM_CAP_DEVICE_CTRL, KVM_CAP_VM_ATTRIBUTES for vm device
>> +Type: device ioctl, vm ioctl
>>   Parameters: struct kvm_device_attr
>>   Returns: 0 on success, -1 on error
>>   Errors:
>> @@ -2340,8 +2340,8 @@ struct kvm_device_attr {
>>     4.81 KVM_HAS_DEVICE_ATTR
>>   -Capability: KVM_CAP_DEVICE_CTRL
>> -Type: device ioctl
>> +Capability: KVM_CAP_DEVICE_CTRL, KVM_CAP_VM_ATTRIBUTES for vm device
>> +Type: device ioctl, vm ioctl
>>   Parameters: struct kvm_device_attr
>>   Returns: 0 on success, -1 on error
>>   Errors:
>> diff --git a/Documentation/virtual/kvm/devices/vm.txt b/Documentation/virtual/kvm/devices/vm.txt
>> new file mode 100644
>> index 0000000..4fe1532
>> --- /dev/null
>> +++ b/Documentation/virtual/kvm/devices/vm.txt
>> @@ -0,0 +1,6 @@
>> +Generic vm interface
>> +====================================
>> +
>> +The interface handles per-vm attributes, such as CMMA status on s390 and is
>> +similar in way to ONE_REG, but targeting the whole vm instead of one vcpu
>> +alone. It is available with KVM_CAP_VM_ATTRIBUTES.
> 
> This document doesn't sound impressively useful :).

Will be filled with patch3. I asked Dominik to split this out into this patch,
since we introduce the capability here.


  reply	other threads:[~2014-04-10 11:34 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-10 11:16 [PATCH 0/3] Introduce per-vm kvm device attributes Christian Borntraeger
2014-04-10 11:16 ` [PATCH 1/3] kvm: s390: Per-vm kvm device controls Christian Borntraeger
2014-04-10 11:29   ` Alexander Graf
2014-04-10 11:33     ` Christian Borntraeger [this message]
2014-04-10 11:35       ` Alexander Graf
2014-04-10 11:16 ` [PATCH 2/3] kvm: s390: make cmma usage conditionally Christian Borntraeger
2014-04-10 11:16 ` [PATCH 3/3] kvm: s390: Exploiting generic userspace interface for cmma Christian Borntraeger
2014-04-16 18:49   ` [PATCH 3/3] kvm: s390: Exploiting generic userspace interface for cmma\ Marcelo Tosatti
2014-04-16 19:47     ` Alexander Graf
2014-04-21 20:48       ` Marcelo Tosatti
2014-04-10 11:37 ` [PATCH 0/3] Introduce per-vm kvm device attributes Alexander Graf

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=534681A3.2080408@de.ibm.com \
    --to=borntraeger@de.ibm.com \
    --cc=agraf@suse.de \
    --cc=cornelia.huck@de.ibm.com \
    --cc=dingel@linux.vnet.ibm.com \
    --cc=gleb@kernel.org \
    --cc=kvm@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=mtosatti@redhat.com \
    --cc=pbonzini@redhat.com \
    /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).