All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Williamson <mark.williamson@cl.cam.ac.uk>
To: hap9@epoch.ncsc.mil
Cc: xen-devel@lists.xensource.com
Subject: [RFC] Auto rebind PCI devices
Date: Tue, 4 Apr 2006 17:43:32 +0100	[thread overview]
Message-ID: <200604041743.32542.mark.williamson@cl.cam.ac.uk> (raw)

Hi Ryan,

I remember you showing some interest when I suggested rebinding PCI devices 
automatically.  I've hacked together a quick prototype of "what I meant".

I put a bundle at: 
http://www.cambridge.intel-research.net/~mwilli2/pci_auto_rebind.hg

You can fetch my changes into a repository using:
hg unbundle <url>

The behaviour is:
* If the device specified in a domain config file is already bound to another 
driver in dom0, fail creation with an error - as before.
* If the device specified in the config is not currently bound to a driver, 
add it to the pciback driver and create the domain.
* If the device specificed in the config is bound *and* pci-force-rebind is 
set, then unbind it from the existing driver and rebind it to pciback, then 
start the domain.

pci-force-rebind allows users who want total automation in the rebinding 
process to have it, whilst by default preventing the automatic rebinding from 
stealing devices dom0 is relying on.

I'd be interested to see what you think about it - in particular, whether 
there are potential failures in the rebinding code that I ought to be 
catching (e.g. if drivers won't unbind from a device - can that happen?).  
Any objections to the general functionality?

Cheers,
Mark

             reply	other threads:[~2006-04-04 16:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-04 16:43 Mark Williamson [this message]
2006-04-04 19:09 ` [RFC] Auto rebind PCI devices Muli Ben-Yehuda
2006-04-05 10:04   ` M.A. Williamson
2006-04-05 15:18   ` Mark Williamson
2006-04-05 17:07     ` Muli Ben-Yehuda
2006-04-10 20:28 ` Ryan

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=200604041743.32542.mark.williamson@cl.cam.ac.uk \
    --to=mark.williamson@cl.cam.ac.uk \
    --cc=hap9@epoch.ncsc.mil \
    --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 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.