From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:47203) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YT41O-0007mq-8j for qemu-devel@nongnu.org; Wed, 04 Mar 2015 02:47:11 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YT41K-0005fd-8g for qemu-devel@nongnu.org; Wed, 04 Mar 2015 02:47:10 -0500 Received: from mail-bn1bon0135.outbound.protection.outlook.com ([157.56.111.135]:45442 helo=na01-bn1-obe.outbound.protection.outlook.com) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YT41K-0005fW-4S for qemu-devel@nongnu.org; Wed, 04 Mar 2015 02:47:06 -0500 Message-ID: <54F6B86B.60309@freescale.com> Date: Wed, 4 Mar 2015 09:46:51 +0200 From: Vasile Catalin-B50542 MIME-Version: 1.0 References: <54DE1945.30600@freescale.com> In-Reply-To: <54DE1945.30600@freescale.com> Content-Type: text/plain; charset="windows-1252"; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [vhost] link new devices List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Vasile Catalin-B50542 Cc: qemu-devel@nongnu.org I'm not yet very accustomed to qemu sources and I usually associate source code modules integration with type_init(). Related to vhost-net, I later found out that it is an API like source code, it is used/called by virtio-net. On Fri, Feb 13, 2015 at 05:33:25PM +0200, Vasile Catalin-B50542 wrote: > How does the vhost API links with vhost devices? > I don't see any "*-net" or "*_net" or even "*net" references in vhost API > files, > nor do I see any registering macros inside vhost-net device code. What do you mean by "link"? The vhost kernel modules have an ioctl(2) interface. See hw/virtio/vhost-backend.c:vhost_kernel_call() callers. Stefan