kvm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alexander Graf <agraf@suse.de>
To: Christian Borntraeger <borntraeger@de.ibm.com>,
	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 0/3]  Introduce per-vm kvm device attributes
Date: Thu, 10 Apr 2014 13:37:54 +0200	[thread overview]
Message-ID: <53468292.5080200@suse.de> (raw)
In-Reply-To: <1397128604-50161-1-git-send-email-borntraeger@de.ibm.com>


On 10.04.14 13:16, Christian Borntraeger wrote:
> Marcelo, Gleb, Alex,
>
> this is a followup to the recent discussion (re config device)
>
> To avoid a bunch of new ioctl, lets reuse the device attributes on
> the "VM device". All of these attributes are architecture specific.
> Patch1 introduces the interface,
> Patch2 makes CMMA configurable
> Patch3 uses the interface introduced in patch1
>
> Marcelo, Gleb, Alex, are you ok with the approach of patch 1? Then we
> will continue using that for VM specific controls instead of adding
> new ioctls. (Otherwise we will continue with new ioctl).

Looks reasonable to me, though I wouldn't be opposed to ENABLE_CAP + 
specific ioctl for reset in this case either. Whatever works better for 
you guys.

Acked-by: Alexander Graf <agraf@suse.de>


Alex


      parent reply	other threads:[~2014-04-10 11:37 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
2014-04-21 20:48       ` Marcelo Tosatti
2014-04-10 11:37 ` Alexander Graf [this message]

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=53468292.5080200@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).