All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Williamson <mark.williamson@cl.cam.ac.uk>
To: xen-devel@lists.xensource.com
Cc: hap9@epoch.ncsc.mil
Subject: Re: [RFC] Auto rebind PCI devices
Date: Wed, 5 Apr 2006 16:18:16 +0100	[thread overview]
Message-ID: <200604051618.16626.mark.williamson@cl.cam.ac.uk> (raw)
In-Reply-To: <20060404190935.GB1221@granada.merseine.nu>

> > * 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.
>
> That sounds awkward. What's the use case you see in mind from stealing
> devices from a domain while it's running?

To clarify my thinking on this a little more: I think it would be good to be 
able to move PCI devices between domains in a reasonably straightforward way.  
This would be something like the PCI hotplug for IBM's dynamic LPAR, which is 
already supported by Linux.

The eventual goal being that you can reassign PCI devices "hotplug-style" (it 
would look like a hotplug to the pcifront kernel) at runtime, with the user 
interface providing appropriate safety checks / "do you really want this?" 
dialogs, according to the level of confidence of the user.

Cheers,
Mark

-- 
Dave: Just a question. What use is a unicyle with no seat?  And no pedals!
Mark: To answer a question with a question: What use is a skateboard?
Dave: Skateboards have wheels.
Mark: My wheel has a wheel!

  parent reply	other threads:[~2006-04-05 15:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-04 16:43 [RFC] Auto rebind PCI devices Mark Williamson
2006-04-04 19:09 ` Muli Ben-Yehuda
2006-04-05 10:04   ` M.A. Williamson
2006-04-05 15:18   ` Mark Williamson [this message]
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=200604051618.16626.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.