From: Vasile Catalin-B50542 <catalin.vasile@freescale.com>
To: Vasile Catalin-B50542 <catalin.vasile@freescale.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [vhost] link new devices
Date: Wed, 4 Mar 2015 09:46:51 +0200 [thread overview]
Message-ID: <54F6B86B.60309@freescale.com> (raw)
In-Reply-To: <54DE1945.30600@freescale.com>
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
prev parent reply other threads:[~2015-03-04 7:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-13 15:33 [Qemu-devel] [vhost] link new devices Vasile Catalin-B50542
2015-03-03 15:40 ` Stefan Hajnoczi
2015-03-04 7:46 ` Vasile Catalin-B50542 [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=54F6B86B.60309@freescale.com \
--to=catalin.vasile@freescale.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).