From: Olaf Hering <olaf@aepfle.de>
To: Jan Beulich <JBeulich@suse.com>
Cc: xen-devel <xen-devel@lists.xensource.com>,
Ian Jackson <Ian.Jackson@eu.citrix.com>,
Ian Campbell <Ian.Campbell@citrix.com>,
"fantonifabio@tiscali.it" <fantonifabio@tiscali.it>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Subject: Re: [PATCH] tools/hotplug/Linux/init.d/: added other xen kernel modules on xencommons start
Date: Fri, 10 Aug 2012 18:05:00 +0200 [thread overview]
Message-ID: <20120810160500.GA21459@aepfle.de> (raw)
In-Reply-To: <502541A60200007800094396@nat28.tlf.novell.com>
On Fri, Aug 10, Jan Beulich wrote:
> >>> On 10.08.12 at 17:10, Olaf Hering <olaf@aepfle.de> wrote:
> > On Fri, Aug 10, Jan Beulich wrote:
> >
> >> That's the case for our kernels, but doesn't have to be for any
> >> derived ones (and there are still a few people cloning our patches).
> >
> > Do they build things into the kernel?
> > Should some other module than evtchn be used to decide which branch to
> > take?
>
> There are people who build in everything. So you would only
> ever be able to derive results from being able to load some
> specific module; not being able to load a certain module doesn't
> allow drawing any conclusion.
If attempting to load pvops modules in a xenlinux based kernel is an
issue then there needs to be another way to tell them appart. A lame
test would be test -f /proc/xen/balloon which doesnt seem to exist in
pvops dom0.
If attempting to load non-existant modules is not an issue then I will
prepare a patch which adds "netbk blkbk xen-scsibk usbbk pciback"
to the list.
Olaf
next prev parent reply other threads:[~2012-08-10 16:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-31 12:41 [PATCH] tools/hotplug/Linux/init.d/: added other xen kernel modules on xencommons start Fabio Fantoni
2012-06-08 14:07 ` Ian Jackson
2012-08-01 12:23 ` Fabio Fantoni
2012-08-01 12:28 ` Ian Campbell
2012-08-03 11:08 ` Ian Jackson
2012-08-07 13:43 ` Jan Beulich
2012-08-07 17:22 ` Ian Jackson
2012-08-08 7:07 ` Jan Beulich
2012-08-10 15:04 ` Olaf Hering
2012-08-10 15:08 ` Jan Beulich
2012-08-10 15:10 ` Olaf Hering
2012-08-10 15:15 ` Jan Beulich
2012-08-10 16:05 ` Olaf Hering [this message]
2012-08-10 17:15 ` Ian Jackson
2012-08-10 15:12 ` Ian Jackson
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=20120810160500.GA21459@aepfle.de \
--to=olaf@aepfle.de \
--cc=Ian.Campbell@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=JBeulich@suse.com \
--cc=fantonifabio@tiscali.it \
--cc=konrad.wilk@oracle.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).