All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yosuke Iwamatsu <y-iwamatsu@ab.jp.nec.com>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>,
	xen-devel@lists.xensource.com, "Zhai,
	Edwin" <edwin.zhai@intel.com>
Subject: [PATCH] PV Passthrough PCI Device Hotplug Support (Tools Part)
Date: Mon, 10 Mar 2008 10:19:10 +0900	[thread overview]
Message-ID: <47D48C8E.7060206@ab.jp.nec.com> (raw)
In-Reply-To: <47BEA1AC.40707@ab.jp.nec.com>

[-- Attachment #1: Type: text/plain, Size: 1487 bytes --]

Hi,

This is the updated patch of PV PCI passthrough hotplug (tools portion).

Changes to xm command:
- Let 'xm pci-attach' command use <domain:bus:slot.func> expression
   rather than use separated arguments like <domain> <bus> <slot> <func>.
   This is the same expression of the domain configuration file and I
   believe it is more user-friendly.
- Let 'xm pci-detach' command use the same <domain:bus:slot.func>
   expression. Formerly, <virtual slot> was used as the key to indicate
   which device we were detaching. But for the current implementation of
   PV PCI hotplug, virtual slots don't have much meaning. I think using
   the same physical device name in both attachment and detachment is
   appropriate here.

Changes to xend:
- Both attach and detach commands are received by device_configure()
   and handled by pci_device_configure().
- HVM specific processings are done in hvm_pci_create_device() and
   hvm_destroyPCIDevice().

The major problem I encoutered during this work is that, I don't have
a vt-d enabled machine and could not confirm that HVM PCI hotplug would
still work after modifications :-(
Then I hacked libxc a little to pretend as if there existed a vt-d
hardware, and could see HVM PCI attach/detach working correctly.
So now I'm pretty sure that we can do both PV and HVM hotplugs with
this patch, but I would appreciate it if someone could test this on
a real vt-d machine.

Regards,
-------------------
Yosuke Iwamatsu
         NEC Corporation


[-- Attachment #2: pv_pcihp_tools_merge.patch --]
[-- Type: all/allfiles, Size: 31631 bytes --]

[-- Attachment #3: Type: text/plain, Size: 138 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

  reply	other threads:[~2008-03-10  1:19 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-21 11:01 [PATCH 1/3][RFC] PV Passthrough PCI Device Hotplug Support (Tools Part) Yosuke Iwamatsu
2008-02-22 10:04 ` Keir Fraser
2008-02-22 10:19   ` Yosuke Iwamatsu
2008-03-10  1:19     ` Yosuke Iwamatsu [this message]
2008-03-10  2:04       ` [PATCH] PV Passthrough PCI Device Hotplug Support(Tools Part) Masaki Kanno
2008-03-10  2:26         ` Yosuke Iwamatsu
2008-03-10  7:17       ` [PATCH] PV Passthrough PCI Device Hotplug Support (Tools Part) Zhai, Edwin
2008-03-10 11:22         ` Yosuke Iwamatsu

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=47D48C8E.7060206@ab.jp.nec.com \
    --to=y-iwamatsu@ab.jp.nec.com \
    --cc=Keir.Fraser@cl.cam.ac.uk \
    --cc=edwin.zhai@intel.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 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.