From mboxrd@z Thu Jan 1 00:00:00 1970 From: Alexander Graf Date: Mon, 19 May 2014 12:59:47 +0000 Subject: Re: [PATCH 7/8] powerpc/powernv: Implement ppc_call_opal() Message-Id: <537A0043.4050906@suse.de> List-Id: References: <1400040722-29608-1-git-send-email-gwshan@linux.vnet.ibm.com> <1400040722-29608-8-git-send-email-gwshan@linux.vnet.ibm.com> In-Reply-To: <1400040722-29608-8-git-send-email-gwshan@linux.vnet.ibm.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: Gavin Shan , kvm-ppc@vger.kernel.org Cc: aik@ozlabs.ru, alex.williamson@redhat.com, qiudayu@linux.vnet.ibm.com, linuxppc-dev@lists.ozlabs.org On 14.05.14 06:12, Gavin Shan wrote: > If we're running PowerNV platform, ppc_firmware() will be directed > to ppc_call_opal() where we can call to OPAL API accordingly. In > ppc_call_opal(), the input argument are parsed out and call to > appropriate OPAL API to handle that. Each request passed to the > function is identified with token. As we get to the function either > from host owned application (e.g. errinjct) or VM, we always have > the first parameter (so-called "virtual") to differentiate the > cases. This sounds like nonsense. A virtual parameter? What is that supposed to be? I don't think you can use this interface for VM device management, as the syscall interface is (hopefully!) limited to CAP_ADMIN which you (hopefully!) don't have as VFIO user. Alex