On Thu, Apr 27, 2017 at 11:59:26AM -0300, jos...@linux.vnet.ibm.com wrote:
> On Thu, Apr 27, 2017 at 10:55:04AM +0200, Paolo Bonzini wrote:
> >
> >
> > On 24/04/2017 19:19, Jose Ricardo Ziviani wrote:
> > > These trace events were very useful to help me to understand and find a
> > > reordering i
- Original Message -
> From: jos...@linux.vnet.ibm.com
> To: "Paolo Bonzini"
> Cc: f...@redhat.com, qemu-devel@nongnu.org, stefa...@redhat.com
> Sent: Thursday, April 27, 2017 4:59:26 PM
> Subject: Re: [Qemu-devel] [PATCH v2] trace: add qemu mutex lock and unloc
On Thu, Apr 27, 2017 at 10:55:04AM +0200, Paolo Bonzini wrote:
>
>
> On 24/04/2017 19:19, Jose Ricardo Ziviani wrote:
> > These trace events were very useful to help me to understand and find a
> > reordering issue in vfio, for example:
> >
> > qemu_mutex_lock locked mutex 0x10905ad8
> > vfio_
On 24/04/2017 19:19, Jose Ricardo Ziviani wrote:
> These trace events were very useful to help me to understand and find a
> reordering issue in vfio, for example:
>
> qemu_mutex_lock locked mutex 0x10905ad8
> vfio_region_write (0001:03:00.0:region1+0xc0, 0x2020c, 4)
> qemu_mutex_unlock unloc
On Mon, 04/24 14:19, Jose Ricardo Ziviani wrote:
> These trace events were very useful to help me to understand and find a
> reordering issue in vfio, for example:
>
> qemu_mutex_lock locked mutex 0x10905ad8
> vfio_region_write (0001:03:00.0:region1+0xc0, 0x2020c, 4)
> qemu_mutex_unlock unlocke
