From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:49160) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bA0F8-00088K-Bl for qemu-devel@nongnu.org; Mon, 06 Jun 2016 15:31:23 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bA0F3-0005q0-CL for qemu-devel@nongnu.org; Mon, 06 Jun 2016 15:31:21 -0400 Received: from mx1.redhat.com ([209.132.183.28]:43812) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bA0F3-0005pw-6f for qemu-devel@nongnu.org; Mon, 06 Jun 2016 15:31:17 -0400 Date: Mon, 6 Jun 2016 13:31:15 -0600 From: Alex Williamson Message-ID: <20160606133115.15f6e2a8@ul30vt.home> In-Reply-To: <20160606174425.GA8903@nvidia.com> References: <1464119897-10844-1-git-send-email-kwankhede@nvidia.com> <1464119897-10844-2-git-send-email-kwankhede@nvidia.com> <20160603165746.3df39542@oc7835276234> <799479b0-44d5-061f-185a-43df0dba2fb3@nvidia.com> <20160606140148.31ec05f9@oc7835276234> <20160606062742.GA31747@nvidia.com> <20160606162911.7021a02c@oc7835276234> <20160606174425.GA8903@nvidia.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [RFC PATCH v4 1/3] Mediated device Core driver List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Neo Jia Cc: Dong Jia , Kirti Wankhede , pbonzini@redhat.com, kraxel@redhat.com, qemu-devel@nongnu.org, kvm@vger.kernel.org, kevin.tian@intel.com, shuai.ruan@intel.com, jike.song@intel.com, zhiyuan.lv@intel.com On Mon, 6 Jun 2016 10:44:25 -0700 Neo Jia wrote: > On Mon, Jun 06, 2016 at 04:29:11PM +0800, Dong Jia wrote: > > On Sun, 5 Jun 2016 23:27:42 -0700 > > Neo Jia wrote: > > > > 2. VFIO_DEVICE_CCW_CMD_REQUEST > > This intends to handle an intercepted channel I/O instruction. It > > basically need to do the following thing: > > May I ask how and when QEMU knows that he needs to issue such VFIO ioctl at > first place? Yep, this is my question as well. It sounds a bit like there's an emulated device in QEMU that's trying to tell the mediated device when to start an operation when we probably should be passing through whatever i/o operations indicate that status directly to the mediated device. Thanks, Alex