From: Ian Campbell <Ian.Campbell@XenSource.com>
To: "Kay, Allen M" <allen.m.kay@intel.com>
Cc: "You, Yongkang" <yongkang.you@intel.com>,
xen-devel@lists.xensource.com, "Han,
Weidong" <weidong.han@intel.com>
Subject: RE: Hiding pci devices from dom0 drivers
Date: Fri, 05 Oct 2007 09:31:38 +0100 [thread overview]
Message-ID: <1191573098.5994.89.camel@localhost.localdomain> (raw)
In-Reply-To: <13A2F7DE1BAEA345A61DD40F303ED7A695F5E3@scsmsx412.amr.corp.intel.com>
On Thu, 2007-10-04 at 11:53 -0700, Kay, Allen M wrote:
> What are your experiences with the reliability of the following
> "pciback" script to dynamically "hide" pci devices after boot?
>
> I found it cause system hangs about 50% of the time.
I've never had a problem with it. It can hang on unbind if the device in
question is in use but as soon as you free up the device (i.e. close the
application which accesses it) the script will continue.
> I'm also having some issues with xen0 kernel. It has e1000 driver as
> builtin. This causes problems since I need to use the latest e1000
> driver from sourceforge so I need to modify xen0 linux config to mark
> e1000 as "m".
The -xen0 is intended to be a mostly statically compiled kernel with
drivers for the most common hardware. If you want a modular kernel you
should be using the -xen kernel.
> In any case, the path of least resistence for me right now is to come up
> with a set of instructions to ask people to download linux-2.6.18-xen.hg
> manually, move it to xen-unstable.hg, turn on PCIDEV_BACKEND='y' in
> config file, and then do "make install" in xen-unstable.hg.
The xen-unstable build system will do the download phase for you. You
can also use the "make CONFIGMODE=menuconfig linux-2.6-xen0-config"
style targets.
Ian.
next prev parent reply other threads:[~2007-10-05 8:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-24 7:10 Hiding pci devices from dom0 drivers Kay, Allen M
2007-09-24 7:27 ` Keir Fraser
2007-09-24 8:13 ` Ian Campbell
2007-10-04 18:53 ` Kay, Allen M
2007-10-05 8:31 ` Ian Campbell [this message]
2007-10-08 6:05 ` You, Yongkang
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=1191573098.5994.89.camel@localhost.localdomain \
--to=ian.campbell@xensource.com \
--cc=allen.m.kay@intel.com \
--cc=weidong.han@intel.com \
--cc=xen-devel@lists.xensource.com \
--cc=yongkang.you@intel.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 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.