[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] [PATCH v3 6/7] xen/pciback: Print out the domain owning the device.

To: <konrad@xxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxxx>, <boris.ostrovsky@xxxxxxxxxx>, <linux-kernel@xxxxxxxxxxxxxxx>
From: David Vrabel <david.vrabel@xxxxxxxxxx>
Date: Wed, 9 Jul 2014 14:04:57 +0100
Delivery-date: Wed, 09 Jul 2014 13:05:50 +0000
List-id: Xen developer discussion <xen-devel.lists.xen.org>

On 08/07/14 19:58, konrad@xxxxxxxxxx wrote:
> From: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
> 
> We had been printing it only if the device was built with
> debug enabled. But this information is usuable in the field
> to troubleshoot.

"useful"

Reviewed-by: David Vrabel <david.vrabel@xxxxxxxxxx>

David

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel

References:
- [Xen-devel] [PATCH] Xen PCIbackend support for slot and bus reset (v3).
  - From: konrad
- [Xen-devel] [PATCH v3 6/7] xen/pciback: Print out the domain owning the device.
  - From: konrad

Prev by Date: [Xen-devel] intercept syscall of VM by setting MSR_SYSENTER_CS as 0x0
Next by Date: Re: [Xen-devel] [PATCH RFC V2 6/6] xen: introduce xenpv-softmmu.mak
Previous by thread: [Xen-devel] [PATCH v3 6/7] xen/pciback: Print out the domain owning the device.
Next by thread: [Xen-devel] [PATCH v3 5/7] xen/pciback: Include the domain id if removing the device whilst still in use
Index(es):
- Date
- Thread

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.