linux-kernel - Re: [Xen-devel] [PATCH V2] Xen/pciback: Implement PCI slot or bus reset with 'do

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <2783ea8a-3ef3-c4dd-a592-52cf8e188ad4@oracle.com>
Date:   Wed, 29 Nov 2017 11:38:57 -0600
From:   Govinda Tatti <govinda.tatti@...cle.com>
To:     Jan Beulich <JBeulich@...e.com>
Cc:     Juergen Gross <jgross@...e.com>, linux-kernel@...r.kernel.org,
        xen-devel@...ts.xenproject.org, boris.ostrovsky@...cle.com,
        roger.pau@...rix.com
Subject: Re: [Xen-devel] [PATCH V2] Xen/pciback: Implement PCI slot or bus
 reset with 'do_flr' SysFS attribute


>> In the case of bus or slot reset, our goal is to reset connected PCIe
>> fabric/card/endpoint.
>> The connected card/endpoint can be multi-function device. So, same
>> walk-through and checking
>> is needed irrespective of type of reset being used.
> I don't follow: The scope of other devices/functions possibly
> affected by a reset depends on the type of reset, doesn't it?
For PCIe platforms, both slot and bus reset endup resetting all connected
device/functions on thesecondary bus (behind the root-port or 
downstream-port).

Cheers
GOVINDA