From mboxrd@z Thu Jan  1 00:00:00 1970
From: Paul Mackerras <paulus@samba.org>
Subject: Re: [PATCH 1/3] KVM: PPC: Book3S: Controls for in-kernel PAPR
 hypercall handling
Date: Thu, 29 May 2014 15:27:34 +1000
Message-ID: <20140529052734.GA17928@drongo>
References: <1401106626-13130-1-git-send-email-paulus@samba.org>
 <1401106626-13130-2-git-send-email-paulus@samba.org>
 <5385E444.2080509@suse.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: kvm-ppc@vger.kernel.org, kvm@vger.kernel.org
To: Alexander Graf <agraf@suse.de>
Return-path: <kvm-ppc-owner@vger.kernel.org>
Content-Disposition: inline
In-Reply-To: <5385E444.2080509@suse.de>
Sender: kvm-ppc-owner@vger.kernel.org
List-Id: kvm.vger.kernel.org

On Wed, May 28, 2014 at 03:27:32PM +0200, Alexander Graf wrote:
> 
> On 26.05.14 14:17, Paul Mackerras wrote:
> >+6.8 KVM_CAP_PPC_ENABLE_HCALL
> >+
> >+Architectures: ppc
> >+Parameters: args[0] is the PAPR hcall number
> >+	    args[1] is 0 to disable, 1 to enable in-kernel handling
> >+
> >+This capability controls whether individual PAPR hypercalls (hcalls)
> >+get handled by the kernel or not.  Enabling or disabling in-kernel
> >+handling of an hcall is effective across the VM.  On creation, an
> 
> Hrm. Could we move the CAP to vm level then?

You mean, define a VM ioctl instead of using a capability?  Or are you
suggesting something else?

Paul.