From: Jean Guyader <jean.guyader@gmail.com>
To: "Kay, Allen M" <allen.m.kay@intel.com>
Cc: xen-devel <xen-devel@lists.xensource.com>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
Wilk <konrad.wilk@oracle.com>,
Jean Guyader <jean.guyader@eu.citrix.com>,
Ian Campbell <Ian.Campbell@eu.citrix.com>,
Thomas Horsten <thomas.horsten@citrix.com>,
Ross Philipson <Ross.Philipson@citrix.com>
Subject: Re: FLR support in xl tool stack
Date: Fri, 28 Jan 2011 09:50:24 +0530 [thread overview]
Message-ID: <AANLkTikW-Rub9WtYCW7k2P1mDFZ=L3tUoFHPL9-JukQQ@mail.gmail.com> (raw)
In-Reply-To: <987664A83D2D224EAE907B061CE93D53019438F9F8@orsmsx505.amr.corp.intel.com>
On 28 January 2011 08:38, Kay, Allen M <allen.m.kay@intel.com> wrote:
> In xm tool stack, there is a function called do_FLR() located in python/xen/util/pci.py that takes care of issuing FLR to passthrough PCI devices. This function is responsible for looking at the device and figure out the most appropriate way to reset the device (PCI/PCIe FLR, secondary bus reset, etc...).
>
> In xl tool stack, I see there is a libxl_device_pci_reset() in libxl/libxl_pci.c that suppose to do the similar thing. It references /sys/bus/pci/drivers/pciback/do_flr and tries to write something to it. However, pciback driver in 2.6.32.27 pvops kernel does not seem to have this do_flr functionality.
>
> Is this something being worked on but not checked in to pvops dom0 kernel yet?
>
> If not, I would prefer implementing all of the do_FLR() functionaility in libxl and not to depend on pciback driver given it is not part of the upstream kernel. This will make using newer kernels such as 2.6.38 much easier.
>
> Comments?
>
On the newest kernels (I don't know from which version), the reset
function has been moved under the pci device tree directly. So
/sys/bus/pci/device/<BDF>/reset.
Jean
next prev parent reply other threads:[~2011-01-28 4:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-28 3:08 FLR support in xl tool stack Kay, Allen M
2011-01-28 4:20 ` Jean Guyader [this message]
2011-01-28 7:34 ` Ian Campbell
2011-01-28 16:10 ` Ross Philipson
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='AANLkTikW-Rub9WtYCW7k2P1mDFZ=L3tUoFHPL9-JukQQ@mail.gmail.com' \
--to=jean.guyader@gmail.com \
--cc=Ian.Campbell@eu.citrix.com \
--cc=Ross.Philipson@citrix.com \
--cc=allen.m.kay@intel.com \
--cc=jean.guyader@eu.citrix.com \
--cc=konrad.wilk@oracle.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=thomas.horsten@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.