From: "Denis V. Lunev" <den-lists@virtuozzo.com>
To: Changlong Xie <xiecl.fnst@cn.fujitsu.com>,
qemu devel <qemu-devel@nongnu.org>,
Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v2] rfifolock: no need to get thread identifier when nesting
Date: Tue, 10 May 2016 13:25:13 +0300 [thread overview]
Message-ID: <5731B709.20102@virtuozzo.com> (raw)
In-Reply-To: <1462874348-32396-1-git-send-email-xiecl.fnst@cn.fujitsu.com>
On 05/10/2016 12:59 PM, Changlong Xie wrote:
> Signed-off-by: Changlong Xie <xiecl.fnst@cn.fujitsu.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);
> }
Reviewed-by: Denis V. Lunev <den@openvz.org>
next prev parent reply other threads:[~2016-05-10 10:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-10 9:59 [Qemu-devel] [PATCH v2] rfifolock: no need to get thread identifier when nesting Changlong Xie
2016-05-10 10:25 ` Denis V. Lunev [this message]
2016-05-12 9:42 ` Stefan Hajnoczi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5731B709.20102@virtuozzo.com \
--to=den-lists@virtuozzo.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--cc=xiecl.fnst@cn.fujitsu.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).