From: Alexander Graf <agraf@suse.de>
To: Marcelo Tosatti <mtosatti@redhat.com>,
Christian Borntraeger <borntraeger@de.ibm.com>
Cc: Gleb Natapov <gleb@kernel.org>,
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 3/3] kvm: s390: Exploiting generic userspace interface for cmma\
Date: Wed, 16 Apr 2014 21:47:52 +0200 [thread overview]
Message-ID: <534EDE68.5060000@suse.de> (raw)
In-Reply-To: <20140416184906.GA8773@amt.cnet>
On 16.04.14 20:49, Marcelo Tosatti wrote:
> On Thu, Apr 10, 2014 at 01:16:44PM +0200, Christian Borntraeger wrote:
>> From: Dominik Dingel <dingel@linux.vnet.ibm.com>
>>
>> To enable CMMA and to reset its state we use the vm kvm_device ioctls,
>> encapsulating attributes within the KVM_S390_VM_MEM_CTRL group.
>>
>> Signed-off-by: Dominik Dingel <dingel@linux.vnet.ibm.com>
>> Signed-off-by: Christian Borntraeger <borntraeger@de.ibm.com>
>> ---
>> Documentation/virtual/kvm/devices/vm.txt | 18 ++++++++++++++
>> arch/s390/include/uapi/asm/kvm.h | 7 ++++++
>> arch/s390/kvm/kvm-s390.c | 42 ++++++++++++++++++++++++++++++++
>> 3 files changed, 67 insertions(+)
> Sounds awkward to use these three ioctls for something not
> returned by KVM_CREATE_DEVICE.
>
> /* ioctls for fds returned by KVM_CREATE_DEVICE */
> #define KVM_SET_DEVICE_ATTR _IOW(KVMIO, 0xe1, struct kvm_device_attr)
> #define KVM_GET_DEVICE_ATTR _IOW(KVMIO, 0xe2, struct kvm_device_attr)
> #define KVM_HAS_DEVICE_ATTR _IOW(KVMIO, 0xe3, struct kvm_device_attr)
>
> Is that much of a problem to introduce
>
> struct kvm_vm_attr and
>
> /* ioctls for fds returned by KVM_CREATE_VM */
> #define KVM_SET_VM_ATTR _IOW(KVMIO, 0xa, struct kvm_vm_attr)
> #define KVM_GET_VM_ATTR _IOW(KVMIO, 0xb, struct kvm_vm_attr)
> #define KVM_HAS_VM_ATTR _IOW(KVMIO, 0xc, struct kvm_vm_attr)
>
> ?
We could just alias them, no?
#define KVM_SET_VM_ATTR KVM_SET_DEVICE_ATTR
But I don't feel strongly either way.
Alex
> Other than that (which would be mostly organizational issue) per-vm
> attributes seem fine to me.
>
next prev parent reply other threads:[~2014-04-16 19:47 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
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 [this message]
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=534EDE68.5060000@suse.de \
--to=agraf@suse.de \
--cc=borntraeger@de.ibm.com \
--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).