lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <674347a4-68f3-b1fc-1cf2-d910e84f3026@oracle.com>
Date:   Thu, 30 Nov 2017 07:55:27 -0600
From:   Govinda Tatti <govinda.tatti@...cle.com>
To:     Jan Beulich <JBeulich@...e.com>
Cc:     xen-devel@...ts.xenproject.org,
        Boris Ostrovsky <boris.ostrovsky@...cle.com>,
        Konrad Rzeszutek Wilk <konrad.wilk@...cle.com>,
        Juergen Gross <jgross@...e.com>, linux-kernel@...r.kernel.org
Subject: Re: [Xen-devel] [PATCH] Xen/pciback: Implement PCI slot or bus reset
 with 'do_flr' SysFS attribute



On 11/30/2017 2:29 AM, Jan Beulich wrote:
>>>> On 29.11.17 at 20:44, <govinda.tatti@...cle.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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ