From: Paolo Bonzini <pbonzini@redhat.com>
To: Sergey Fedorov <serge.fdrv@gmail.com>, qemu-devel@nongnu.org
Cc: alex.bennee@linaro.org, sergey.fedorov@linaro.org
Subject: Re: [Qemu-devel] [PATCH] atomics: add volatile_read/volatile_set
Date: Mon, 18 Jul 2016 22:54:55 +0200 [thread overview]
Message-ID: <13032d05-0ddc-42ae-6e25-2b13ef535f4f@redhat.com> (raw)
In-Reply-To: <578D2821.6010408@gmail.com>
On 18/07/2016 21:04, Sergey Fedorov wrote:
> How much performance do we really need and how much performance can we
> loose introducing such a flag? We should yet gain something reducing
> tb_lock contention. Maybe it is worthwhile to use a dedicated flag to
> keep code more clear? There's always a question of balance between code
> structure and maintainability (future of the TCG) on one hand and
> performance (present of the TCG) on the other hand.
Fair enough, can you send a patch that does this? If we can do the
check only just before tb_add_jump, indeed there's no reason to do all
the mess with invalid state.
Paolo
prev parent reply other threads:[~2016-07-18 20:55 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-18 14:17 [Qemu-devel] [PATCH] atomics: add volatile_read/volatile_set Paolo Bonzini
2016-07-18 16:52 ` Sergey Fedorov
2016-07-18 16:53 ` Paolo Bonzini
2016-07-18 16:57 ` Sergey Fedorov
2016-07-18 17:00 ` Paolo Bonzini
2016-07-18 17:07 ` Sergey Fedorov
2016-07-18 17:11 ` Paolo Bonzini
2016-07-18 17:17 ` Sergey Fedorov
2016-07-18 17:22 ` Paolo Bonzini
2016-07-18 17:25 ` Sergey Fedorov
2016-07-18 17:28 ` Paolo Bonzini
2016-07-18 17:31 ` Sergey Fedorov
2016-07-18 17:58 ` Paolo Bonzini
2016-07-18 19:04 ` Sergey Fedorov
2016-07-18 20:54 ` Paolo Bonzini [this message]
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=13032d05-0ddc-42ae-6e25-2b13ef535f4f@redhat.com \
--to=pbonzini@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=serge.fdrv@gmail.com \
--cc=sergey.fedorov@linaro.org \
/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).