Thanks Pasi for your response. Please see below for my comments.
On 11/8/2017 11:38 AM, Pasi Kärkkäinen wrote:
Hi,
On Wed, Nov 08, 2017 at 09:44:48AM -0600, Govinda Tatti wrote:
Thanks Jan for your review comments. Please see below for my comments.
On 11/7/2017 8:40 AM, Jan Beulich wrote
ces that are in
use by other drivers (other than Xen pciback) prior to the reset, we check
that all of the devices under the bridge are owned by Xen pciback. If they
are not, we refrain from executing the bus (or slot) reset.
Signed-off-by: Govinda Tatti
Signed-off-by: Konrad Rzeszutek Wilk
Reviewe
Thanks Jan for your review comments. Please see below for my comments.
On 11/7/2017 8:40 AM, Jan Beulich wrote:
On 06.11.17 at 18:48, wrote:
--- a/Documentation/ABI/testing/sysfs-driver-pciback
+++ b/Documentation/ABI/testing/sysfs-driver-pciback
@@ -11,3 +11,15 @@ Description:
On 11/8/2017 9:09 AM, Juergen Gross wrote:
On 08/11/17 16:00, Govinda Tatti wrote:
Thanks Roger for your review comments. Please see below for my comments.
On 11/7/2017 5:21 AM, Roger Pau Monné wrote:
On Mon, Nov 06, 2017 at 12:48:42PM -0500, Govinda Tatti wrote:
+out:
+ if (!err
Thanks Roger for your review comments. Please see below for my comments.
On 11/7/2017 5:21 AM, Roger Pau Monné wrote:
On Mon, Nov 06, 2017 at 12:48:42PM -0500, Govinda Tatti wrote:
The life-cycle of a PCI device in Xen pciback is complex and is constrained
by the generic PCI locking mechanism
ces that are in
use by other drivers (other than Xen pciback) prior to the reset, we check
that all of the devices under the bridge are owned by Xen pciback. If they
are not, we refrain from executing the bus (or slot) reset.
Signed-off-by: Govinda Tatti
Signed-off-by: Konrad Rzeszutek Wilk
Reviewe
