From: Boris Ostrovsky <boris.ostrovsky@oracle.com>
To: "Pasi Kärkkäinen" <pasik@iki.fi>,
"Roger Pau Monné" <roger.pau@citrix.com>
Cc: George Dunlap <George.Dunlap@citrix.com>,
Jan Beulich <JBeulich@suse.com>, Juergen Gross <jgross@suse.com>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"bhelgaas@google.com" <bhelgaas@google.com>,
xen-devel <xen-devel@lists.xenproject.org>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Subject: Re: [Xen-devel] [PATCH V3 2/2] Xen/PCIback: Implement PCI flr/slot/bus reset with 'reset' SysFS attribute
Date: Mon, 8 Oct 2018 10:32:45 -0400 [thread overview]
Message-ID: <f6b8e055-7afc-b4de-af88-425d799dcd28@oracle.com> (raw)
In-Reply-To: <20181003155104.GH5318@reaktio.net>
On 10/3/18 11:51 AM, Pasi Kärkkäinen wrote:
> On Wed, Sep 19, 2018 at 11:05:26AM +0200, Roger Pau Monné wrote:
>> On Tue, Sep 18, 2018 at 02:09:53PM -0400, Boris Ostrovsky wrote:
>>> On 9/18/18 5:32 AM, George Dunlap wrote:
>>>>> On Sep 18, 2018, at 8:15 AM, Pasi Kärkkäinen <pasik@iki.fi> wrote:
>>>>>
>>>>> Hi,
>>>>>
>>>>> On Mon, Sep 17, 2018 at 02:06:02PM -0400, Boris Ostrovsky wrote:
>>>>>> What about the toolstack changes? Have they been accepted? I vaguely
>>>>>> recall there was a discussion about those changes but don't remember how
>>>>>> it ended.
>>>>>>
>>>>> I don't think toolstack/libxl patch has been applied yet either.
>>>>>
>>>>>
>>>>> "[PATCH V1 0/1] Xen/Tools: PCI reset using 'reset' SysFS attribute":
>>>>> https://lists.xen.org/archives/html/xen-devel/2017-12/msg00664.html
>>>>>
>>>>> "[PATCH V1 1/1] Xen/libxl: Perform PCI reset using 'reset' SysFS attribute":
>>>>> https://lists.xen.org/archives/html/xen-devel/2017-12/msg00663.html
>>>
>>> Will this patch work for *BSD? Roger?
>> At least FreeBSD don't support pci-passthrough, so none of this works
>> ATM. There's no sysfs on BSD, so much of what's in libxl_pci.c will
>> have to be moved to libxl_linux.c when BSD support is added.
>>
> Ok. That sounds like it's OK for the initial pci 'reset' implementation in xl/libxl to be linux-only..
>
Are these two patches still needed? ISTR they were written originally
to deal with guest trying to use device that was previously assigned to
another guest. But pcistub_put_pci_dev() calls
__pci_reset_function_locked() which first tries FLR, and it looks like
it was added relatively recently.
-boris
next prev parent reply other threads:[~2018-10-08 14:33 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-07 22:21 [PATCH V3 0/2] Xen/PCIback: PCI reset using 'reset' SysFS attribute Govinda Tatti
2017-12-07 22:21 ` [PATCH V3 1/2] Drivers/PCI: Export pcie_has_flr() interface Govinda Tatti
2017-12-08 20:24 ` Bjorn Helgaas
2017-12-12 0:29 ` Govinda Tatti
2017-12-12 0:59 ` Bjorn Helgaas
2017-12-13 20:46 ` [Xen-devel] " Govinda Tatti
2017-12-13 21:24 ` Bjorn Helgaas
2017-12-14 12:52 ` Christoph Hellwig
2017-12-15 0:24 ` Bjorn Helgaas
2017-12-15 15:48 ` Govinda Tatti
2017-12-15 18:18 ` Bjorn Helgaas
2017-12-15 20:01 ` Govinda Tatti
2017-12-18 3:09 ` Alexey Kardashevskiy
2017-12-18 12:26 ` Christoph Hellwig
2017-12-18 17:22 ` Govinda Tatti
2018-09-09 18:59 ` Pasi Kärkkäinen
2018-09-10 2:33 ` Sinan Kaya
2018-09-10 9:52 ` Pasi Kärkkäinen
2018-09-10 17:04 ` Sinan Kaya
2017-12-12 15:07 ` Christoph Hellwig
2017-12-07 22:21 ` [PATCH V3 2/2] Xen/PCIback: Implement PCI flr/slot/bus reset with 'reset' SysFS attribute Govinda Tatti
2017-12-08 9:34 ` Jan Beulich
2017-12-12 15:01 ` Govinda Tatti
[not found] ` <8a3bc517-1255-4547-d244-5c400e44cc77@Oracle.COM>
2017-12-12 15:01 ` Jan Beulich
2017-12-12 15:14 ` [Xen-devel] " Govinda Tatti
2017-12-15 19:52 ` Govinda Tatti
2017-12-18 7:36 ` Jan Beulich
2017-12-18 17:32 ` Boris Ostrovsky
2018-09-16 11:43 ` [Xen-devel] " Pasi Kärkkäinen
2018-09-17 18:06 ` Boris Ostrovsky
2018-09-18 7:15 ` Pasi Kärkkäinen
2018-09-18 9:32 ` George Dunlap
2018-09-18 18:09 ` Boris Ostrovsky
2018-09-19 9:05 ` Roger Pau Monné
2018-10-03 15:51 ` Pasi Kärkkäinen
2018-10-08 14:32 ` Boris Ostrovsky [this message]
2019-08-26 21:05 ` Pasi Kärkkäinen
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=f6b8e055-7afc-b4de-af88-425d799dcd28@oracle.com \
--to=boris.ostrovsky@oracle.com \
--cc=George.Dunlap@citrix.com \
--cc=JBeulich@suse.com \
--cc=bhelgaas@google.com \
--cc=jgross@suse.com \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=pasik@iki.fi \
--cc=roger.pau@citrix.com \
--cc=xen-devel@lists.xenproject.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).