All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yosuke Iwamatsu <y-iwamatsu@ab.jp.nec.com>
To: "Cui, Dexuan" <dexuan.cui@intel.com>
Cc: xen-devel@lists.xensource.com, Keir Fraser <keir.fraser@eu.citrix.com>
Subject: Re: [PATCH] Improve the current FLR logic
Date: Tue, 15 Jul 2008 13:05:54 +0900	[thread overview]
Message-ID: <487C2222.5030703@ab.jp.nec.com> (raw)
In-Reply-To: <FE7BBCFBB500984A9A7922EBC95F516E0169A036@pdsmsx414.ccr.corp.intel.com>

Hi,

Cui, Dexuan wrote:
> [PATCH3] do_FLR_in_control_panel.patch:  the improved FLR logic in
> Control Panel: 1) If the device is PCIe endpoint and supports PCIe FLR,
> we use that; 2) Else, if the device is PCIe endpoint, and all functions
> on the device are assigned to the same guest, we use the immediate
> parent bus's Secondary Bus Reset to reset all functions of the device
> (here, actually we require all the functions of the device be assigned
> to the same guest); 3) Else, if the device is PCI endpoint and is on a
> host bus (e.g. integrated devices) and if the device supports PCI
> Advanced Capabilities, we use that for FLR; 4) Else, we use the
> Secondary Bus Reset (if the PCI device is behind a PCI/PCI-X bridge,
> then all devices behind the uppermost such PCI/PCI-X bridge above this
> device must be co-assigned)

In case 2) or 4), I think multfunction devices or sibling devices need
not be actually assigned to the same guest, if they are just owned by
pciback and not used by other guests.

> [PATCH4] list_assignable_devices.patch: a command "xm
> pci-list-assignable-devices" which can list all the assignable devices
> in the system. It is useful for end users.

It looks like xm_pci_list_assignable_devices() directly accesses to
sysfs and invokes hypercall without going through xend. Since xm
commands can be executed by a remote server through xmlrpc, most of
this function should be implemented in xend.
Also please note that test_assign_device() excludes the case of
non-iommu device assignment for pv.

Thanks,
-- Yosuke Iwamatsu

  parent reply	other threads:[~2008-07-15  4:05 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-12 12:37 [PATCH] Improve the current FLR logic Cui, Dexuan
2008-07-14 17:52 ` Espen Skoglund
2008-07-17 10:21   ` Cui, Dexuan
2008-07-17 12:50     ` Espen Skoglund
2008-07-18  5:31       ` Jiang, Yunhong
2008-07-15  4:05 ` Yosuke Iwamatsu [this message]
2008-07-17 10:21   ` Cui, Dexuan
2008-07-17 11:06     ` Yosuke Iwamatsu
2008-07-18  2:13       ` Cui, Dexuan
2008-07-17  9:33 ` Yuji Shimada
2008-07-17 10:22   ` Cui, Dexuan
2008-07-18  6:37   ` Cui, Dexuan
2008-07-18  9:34     ` Yuji Shimada
2008-07-18 10:43       ` Cui, Dexuan
2008-07-22 10:16         ` Yuji Shimada
2008-07-22 10:48           ` Keir Fraser
2008-07-23  3:16           ` Cui, Dexuan
2008-07-24  7:53             ` Yuji Shimada
     [not found]               ` <FE7BBCFBB500984A9A7922EBC95F516E0178C213@pdsmsx414.ccr.corp.intel.com>
2008-07-24  8:38                 ` Yuji Shimada
2008-07-24 10:19                   ` Cui, Dexuan
2008-07-25  3:02                     ` Yuji Shimada
2008-07-25  3:21                       ` Cui, Dexuan
2008-09-19  6:45                     ` Neo Jia
2008-09-19  6:58                       ` Cui, Dexuan
2008-10-01  6:55                       ` Neo Jia
2008-10-01  6:53   ` Neo Jia
2008-10-01  8:21     ` Yuji Shimada

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=487C2222.5030703@ab.jp.nec.com \
    --to=y-iwamatsu@ab.jp.nec.com \
    --cc=dexuan.cui@intel.com \
    --cc=keir.fraser@eu.citrix.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.