From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-1.0 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id DBB38C072B5 for ; Fri, 24 May 2019 09:55:33 +0000 (UTC) Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id B08F621773 for ; Fri, 24 May 2019 09:55:33 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org B08F621773 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=sipsolutions.net Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=qemu-devel-bounces+qemu-devel=archiver.kernel.org@nongnu.org Received: from localhost ([127.0.0.1]:51850 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1hU6vF-0007T7-02 for qemu-devel@archiver.kernel.org; Fri, 24 May 2019 05:55:33 -0400 Received: from eggs.gnu.org ([209.51.188.92]:53733) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1hU6uT-00079x-I5 for qemu-devel@nongnu.org; Fri, 24 May 2019 05:54:46 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hU6uR-0001Ov-F2 for qemu-devel@nongnu.org; Fri, 24 May 2019 05:54:45 -0400 Received: from s3.sipsolutions.net ([2a01:4f8:191:4433::2]:54254 helo=sipsolutions.net) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1hU6uQ-0001Np-5W for qemu-devel@nongnu.org; Fri, 24 May 2019 05:54:43 -0400 Received: by sipsolutions.net with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1hU6uB-0001Nq-RL; Fri, 24 May 2019 11:54:27 +0200 Message-ID: From: Johannes Berg To: Stefan Hajnoczi Date: Fri, 24 May 2019 11:54:26 +0200 In-Reply-To: (sfid-20190523_164131_760945_C45BA0A2) References: <0952696452f5ff4e38d2417029243fc60efa33d6.camel@sipsolutions.net> <20190523115950.GH26632@stefanha-x1.localdomain> <41d64b8971a097d1568f947517b45d09c156ccc8.camel@sipsolutions.net> (sfid-20190523_164131_760945_C45BA0A2) Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.28.5 (3.28.5-2.fc28) Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 2a01:4f8:191:4433::2 Subject: Re: [Qemu-devel] custom virt-io support (in user-mode-linux) X-BeenThere: qemu-devel@nongnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: ido@wizery.com, linux-um@lists.infradead.org, qemu-devel , Linux Virtualization Errors-To: qemu-devel-bounces+qemu-devel=archiver.kernel.org@nongnu.org Sender: "Qemu-devel" On Thu, 2019-05-23 at 15:41 +0100, Stefan Hajnoczi wrote: > > Also, not sure I understand how the client is started? > > The vhost-user device backend can be launched before QEMU. QEMU is > started with the UNIX domain socket path so it can connect. Hmm. I guess I'm confusing the terminology then - I thought qemu was the server and the backend was the client that connects to it. If it's the other way around, yeah, that makes things easier and certainly makes sense (you could have a daemon that implements something). > QEMU itself doesn't fork+exec the vhost-user device backend. It's > expected that the user or the management stack has already launched > the vhost-user device backend. Right. > > Do you know if there's a sample client/server somewhere? > > See contrib/libvhost-user in the QEMU source tree as well as the > vhost-user-blk and vhost-user-scsi examples in the contrib/ directory. Awesome, thanks! johannes From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from s3.sipsolutions.net ([2a01:4f8:191:4433::2] helo=sipsolutions.net) by bombadil.infradead.org with esmtps (Exim 4.90_1 #2 (Red Hat Linux)) id 1hU6uN-0002Rn-S6 for linux-um@lists.infradead.org; Fri, 24 May 2019 09:54:42 +0000 Message-ID: Subject: Re: [Qemu-devel] custom virt-io support (in user-mode-linux) From: Johannes Berg Date: Fri, 24 May 2019 11:54:26 +0200 In-Reply-To: (sfid-20190523_164131_760945_C45BA0A2) References: <0952696452f5ff4e38d2417029243fc60efa33d6.camel@sipsolutions.net> <20190523115950.GH26632@stefanha-x1.localdomain> <41d64b8971a097d1568f947517b45d09c156ccc8.camel@sipsolutions.net> (sfid-20190523_164131_760945_C45BA0A2) Mime-Version: 1.0 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-um" Errors-To: linux-um-bounces+geert=linux-m68k.org@lists.infradead.org To: Stefan Hajnoczi Cc: ido@wizery.com, linux-um@lists.infradead.org, qemu-devel , Linux Virtualization On Thu, 2019-05-23 at 15:41 +0100, Stefan Hajnoczi wrote: > > Also, not sure I understand how the client is started? > > The vhost-user device backend can be launched before QEMU. QEMU is > started with the UNIX domain socket path so it can connect. Hmm. I guess I'm confusing the terminology then - I thought qemu was the server and the backend was the client that connects to it. If it's the other way around, yeah, that makes things easier and certainly makes sense (you could have a daemon that implements something). > QEMU itself doesn't fork+exec the vhost-user device backend. It's > expected that the user or the management stack has already launched > the vhost-user device backend. Right. > > Do you know if there's a sample client/server somewhere? > > See contrib/libvhost-user in the QEMU source tree as well as the > vhost-user-blk and vhost-user-scsi examples in the contrib/ directory. Awesome, thanks! johannes _______________________________________________ linux-um mailing list linux-um@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-um