From: Govinda Tatti <govinda.tatti@oracle.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: xen-devel@lists.xenproject.org,
Boris Ostrovsky <boris.ostrovsky@oracle.com>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
Juergen Gross <jgross@suse.com>,
linux-kernel@vger.kernel.org
Subject: Re: [Xen-devel] [PATCH] Xen/pciback: Implement PCI slot or bus reset with 'do_flr' SysFS attribute
Date: Thu, 30 Nov 2017 07:55:27 -0600 [thread overview]
Message-ID: <674347a4-68f3-b1fc-1cf2-d910e84f3026@oracle.com> (raw)
In-Reply-To: <5A1FCF95020000780019364A@prv-mh.provo.novell.com>
On 11/30/2017 2:29 AM, Jan Beulich wrote:
>>>> On 29.11.17 at 20:44, <govinda.tatti@oracle.com> wrote:
>> So, we will use the following sequence to reset the requested
>> device/function.
>>
>> - FLR (as first option)
>> - BUS/SLOT reset (as fall-back option) if FLR is not supported or any
>> issue with FLR
> It looks to me as if the slot reset could also fail despite the probe
> having succeeded. In such a case it might be better to try a bus
> reset, i.e. the sequence would become
> - FLR
> - slot reset if FLR failed
> - bus reset if slot reset failed
Fine with me.
Cheers
GOVINDA
next prev parent reply other threads:[~2017-11-30 13:55 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-06 17:48 [PATCH] Xen/pciback: Implement PCI slot or bus reset with 'do_flr' SysFS attribute Govinda Tatti
2017-11-07 11:21 ` [Xen-devel] " Roger Pau Monné
2017-11-08 15:00 ` Govinda Tatti
2017-11-08 15:09 ` Juergen Gross
2017-11-08 15:34 ` Govinda Tatti
2017-11-07 14:40 ` Jan Beulich
2017-11-08 15:44 ` Govinda Tatti
2017-11-08 17:38 ` Pasi Kärkkäinen
2017-11-08 23:26 ` Govinda Tatti
2017-11-09 8:28 ` Jan Beulich
2017-11-29 15:08 ` Govinda Tatti
2017-11-29 15:35 ` Jan Beulich
2017-11-29 16:29 ` Konrad Rzeszutek Wilk
2017-11-29 16:40 ` Jan Beulich
2017-11-29 19:26 ` Konrad Rzeszutek Wilk
2017-11-29 19:44 ` Govinda Tatti
2017-11-30 8:29 ` Jan Beulich
2017-11-30 13:55 ` Govinda Tatti [this message]
2017-11-29 17:25 ` Govinda Tatti
2017-11-29 18:05 ` Pasi Kärkkäinen
2017-11-29 19:51 ` Govinda Tatti
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=674347a4-68f3-b1fc-1cf2-d910e84f3026@oracle.com \
--to=govinda.tatti@oracle.com \
--cc=JBeulich@suse.com \
--cc=boris.ostrovsky@oracle.com \
--cc=jgross@suse.com \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--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).