* [Qemu-devel] [PULL 0/1] Block patches
@ 2016-05-17 0:19 Stefan Hajnoczi
2016-05-17 0:19 ` [Qemu-devel] [PULL 1/1] rfifolock: no need to get thread identifier when nesting Stefan Hajnoczi
2016-05-17 15:48 ` [Qemu-devel] [PULL 0/1] Block patches Peter Maydell
0 siblings, 2 replies; 3+ messages in thread
From: Stefan Hajnoczi @ 2016-05-17 0:19 UTC (permalink / raw)
To: qemu-devel; +Cc: Peter Maydell, Stefan Hajnoczi
The following changes since commit 70f87e0f0aa04f764dabaeb3ed71ff195748076a:
Merge remote-tracking branch 'remotes/kraxel/tags/pull-ui-20160513-1' into staging (2016-05-13 13:39:38 +0100)
are available in the git repository at:
git://github.com/stefanha/qemu.git tags/block-pull-request
for you to fetch changes up to de3e15a705cbb4b54b2a749f8d5131c9f1666fb3:
rfifolock: no need to get thread identifier when nesting (2016-05-16 15:29:44 -0700)
----------------------------------------------------------------
----------------------------------------------------------------
Changlong Xie (1):
rfifolock: no need to get thread identifier when nesting
util/rfifolock.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--
2.5.5
^ permalink raw reply [flat|nested] 3+ messages in thread
* [Qemu-devel] [PULL 1/1] rfifolock: no need to get thread identifier when nesting
2016-05-17 0:19 [Qemu-devel] [PULL 0/1] Block patches Stefan Hajnoczi
@ 2016-05-17 0:19 ` Stefan Hajnoczi
2016-05-17 15:48 ` [Qemu-devel] [PULL 0/1] Block patches Peter Maydell
1 sibling, 0 replies; 3+ messages in thread
From: Stefan Hajnoczi @ 2016-05-17 0:19 UTC (permalink / raw)
To: qemu-devel; +Cc: Peter Maydell, Changlong Xie, Stefan Hajnoczi
From: Changlong Xie <xiecl.fnst@cn.fujitsu.com>
Signed-off-by: Changlong Xie <xiecl.fnst@cn.fujitsu.com>
Reviewed-by: Denis V. Lunev <den@openvz.org>
Message-id: 1462874348-32396-1-git-send-email-xiecl.fnst@cn.fujitsu.com
Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
---
util/rfifolock.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/util/rfifolock.c b/util/rfifolock.c
index c22f5fe..084c2f0 100644
--- a/util/rfifolock.c
+++ b/util/rfifolock.c
@@ -58,9 +58,9 @@ void rfifolock_lock(RFifoLock *r)
}
qemu_cond_wait(&r->cond, &r->lock);
}
+ qemu_thread_get_self(&r->owner_thread);
}
- qemu_thread_get_self(&r->owner_thread);
r->nesting++;
qemu_mutex_unlock(&r->lock);
}
--
2.5.5
^ permalink raw reply related [flat|nested] 3+ messages in thread* Re: [Qemu-devel] [PULL 0/1] Block patches
2016-05-17 0:19 [Qemu-devel] [PULL 0/1] Block patches Stefan Hajnoczi
2016-05-17 0:19 ` [Qemu-devel] [PULL 1/1] rfifolock: no need to get thread identifier when nesting Stefan Hajnoczi
@ 2016-05-17 15:48 ` Peter Maydell
1 sibling, 0 replies; 3+ messages in thread
From: Peter Maydell @ 2016-05-17 15:48 UTC (permalink / raw)
To: Stefan Hajnoczi; +Cc: QEMU Developers
On 17 May 2016 at 01:19, Stefan Hajnoczi <stefanha@redhat.com> wrote:
> The following changes since commit 70f87e0f0aa04f764dabaeb3ed71ff195748076a:
>
> Merge remote-tracking branch 'remotes/kraxel/tags/pull-ui-20160513-1' into staging (2016-05-13 13:39:38 +0100)
>
> are available in the git repository at:
>
> git://github.com/stefanha/qemu.git tags/block-pull-request
>
> for you to fetch changes up to de3e15a705cbb4b54b2a749f8d5131c9f1666fb3:
>
> rfifolock: no need to get thread identifier when nesting (2016-05-16 15:29:44 -0700)
>
> ----------------------------------------------------------------
>
> ----------------------------------------------------------------
>
> Changlong Xie (1):
> rfifolock: no need to get thread identifier when nesting
Applied, thanks.
-- PMM
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2016-05-17 15:49 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2016-05-17 0:19 [Qemu-devel] [PULL 0/1] Block patches Stefan Hajnoczi
2016-05-17 0:19 ` [Qemu-devel] [PULL 1/1] rfifolock: no need to get thread identifier when nesting Stefan Hajnoczi
2016-05-17 15:48 ` [Qemu-devel] [PULL 0/1] Block patches Peter Maydell
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).