From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Rafal Wojtczuk <rafal@invisiblethingslab.com>
Cc: xen-devel@lists.xensource.com, qubes-devel@googlegroups.com
Subject: Re: Using xen-netfront in dom0
Date: Mon, 19 Apr 2010 10:15:21 -0700 [thread overview]
Message-ID: <4BCC8FA9.80309@goop.org> (raw)
In-Reply-To: <20100419082624.GC18572@emperor2.itldev.org>
On 04/19/2010 01:26 AM, Rafal Wojtczuk wrote:
> Is there any reason for this check, besides obviously false assumption
> "nobody needs it in dom0" ? On a related note, there seems to be no such
> check in xen-blkfront.c.
>
> If there are no disadvantages, I would vote for removal of the
> xen_initial_domain() check; otherwise, can we have a module parameter
> "allow_dom0" ?
>
No, I think its probably fine to remove the check. Presumably if the
driver is modular it would never get loaded in a normal dom0 case
anyway? And in the non-modular case, an initialized but unused driver
shouldn't take much memory (and if it does, that should be fixed).
J
prev parent reply other threads:[~2010-04-19 17:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-19 8:26 Using xen-netfront in dom0 Rafal Wojtczuk
2010-04-19 17:15 ` Jeremy Fitzhardinge [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=4BCC8FA9.80309@goop.org \
--to=jeremy@goop.org \
--cc=qubes-devel@googlegroups.com \
--cc=rafal@invisiblethingslab.com \
--cc=xen-devel@lists.xensource.com \
/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).