From: "Roger Pau Monné" <roger.pau@citrix.com>
To: Vincenzo Maffione <v.maffione@gmail.com>, xen-devel@lists.xenproject.org
Subject: Re: [new PV device]
Date: Tue, 15 Apr 2014 12:25:56 +0200 [thread overview]
Message-ID: <534D0934.5050603@citrix.com> (raw)
In-Reply-To: <CA+_eA9jmJrgr+g=gqBssDnYWygWtnE3i-H8i-hZ0KQqqxv3C0Q@mail.gmail.com>
On 14/04/14 17:45, Vincenzo Maffione wrote:
> Hi,
> I would like to design a new paravirtual device for Xen PV guests
> (under Linux),
> for research purposes.
> This device should be a "simplification" of netfront/netback in that
> the interface
> with the domU/dom0 O.S. is not the normal TCP/IP stack, but something way
> simpler (however, this is not so important w.r.t. my question).
>
> Looking at the netback code
> linux:drivers/net/xen-netback/xenbus.c
> I've run into some "hotplug scripts" support code.
> The netfront code, on the other hand, has no hotplug-related code.
>
> I don't really understand what is the purpose of this hotplug support
> (Is it something
> related to the vif-* scripts?), but I'm wondering whether I can get
> rid of this code for my
> "simplified" device.
This hooks were used by xend, which relies on udev for launching hotplug
scripts. libxl launches scripts directly, so if you are adding a new
device, and don't need xend compatibility, you can get rid of them AFAIK.
Roger.
prev parent reply other threads:[~2014-04-15 10:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-14 15:45 [new PV device] Vincenzo Maffione
2014-04-14 21:46 ` Wei Liu
2014-04-15 10:13 ` Vincenzo Maffione
2014-04-15 10:20 ` Wei Liu
2014-04-15 10:39 ` Konrad Rzeszutek Wilk
2014-04-15 10:25 ` Roger Pau Monné [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=534D0934.5050603@citrix.com \
--to=roger.pau@citrix.com \
--cc=v.maffione@gmail.com \
--cc=xen-devel@lists.xenproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.