All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Campbell <Ian.Campbell@eu.citrix.com>
To: Jean Guyader <jean.guyader@gmail.com>
Cc: xen-devel <xen-devel@lists.xensource.com>,
	Stefano Stabellini <Stefano.Stabellini@eu.citrix.com>,
	Wilk <konrad.wilk@oracle.com>,
	"Kay, Allen M" <allen.m.kay@intel.com>,
	Jean Guyader <Jean.Guyader@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 07:34:06 +0000	[thread overview]
Message-ID: <1296200046.20804.74.camel@localhost.localdomain> (raw)
In-Reply-To: <AANLkTikW-Rub9WtYCW7k2P1mDFZ=L3tUoFHPL9-JukQQ@mail.gmail.com>

On Fri, 2011-01-28 at 04:20 +0000, Jean Guyader wrote: 
> 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.
Only...             ^s

... otherwise that's correct and libxl will try this path if the pciback
one does not exist.

If any additional FLR functionality is required it should be done in the
kernel as part of this generic FLR mechanism so that everyone benefits.

drivers/pci/pci-sysfs.c provides the sysfs node based on the result of
pci_probe_reset_function(dev) which tries a bunch of generic ways of
resetting a device. In addition drivers/pci/quirks.c provides some
device specific quirks.

Perhaps all that is needed is to nominate some patches for backporting
to the xen/stable-2.6.32 branch? 
$ git log --no-merges --pretty=oneline v2.6.32.27..origin/master drivers/pci/quirks.c
seems to provide an initial set of potentially interesting candidates.

Ian.

  reply	other threads:[~2011-01-28  7:34 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
2011-01-28  7:34   ` Ian Campbell [this message]
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=1296200046.20804.74.camel@localhost.localdomain \
    --to=ian.campbell@eu.citrix.com \
    --cc=Jean.Guyader@citrix.com \
    --cc=Ross.Philipson@citrix.com \
    --cc=Stefano.Stabellini@eu.citrix.com \
    --cc=allen.m.kay@intel.com \
    --cc=jean.guyader@gmail.com \
    --cc=konrad.wilk@oracle.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.