From: Sergey Fedorov <serge.fdrv@gmail.com>
To: "Alex Bennée" <alex.bennee@linaro.org>,
"Paolo Bonzini" <pbonzini@redhat.com>
Cc: mttcg@greensocs.com, qemu-devel@nongnu.org,
fred konrad <fred.konrad@greensocs.com>,
a rigo <a.rigo@virtualopensystems.com>,
cota@braap.org, bobby prani <bobby.prani@gmail.com>,
mark burton <mark.burton@greensocs.com>,
jan kiszka <jan.kiszka@siemens.com>,
rth@twiddle.net, peter maydell <peter.maydell@linaro.org>,
claudio fontana <claudio.fontana@huawei.com>
Subject: Re: [Qemu-devel] [RFC 0/7] Safe watch and breakpoint manipulation
Date: Mon, 20 Jun 2016 21:16:20 +0300 [thread overview]
Message-ID: <576832F4.5080202@gmail.com> (raw)
In-Reply-To: <8737o7su4z.fsf@linaro.org>
On 20/06/16 19:27, Alex Bennée wrote:
> The watchpoint contention is the biggest one. FWIW I like the RCU
> approach because it is low impact when running (and I'm hoping faster as
> well by not being a linked list).
When can we expect any contention? I generally find the idea of RCU
really great, but in this particular case, I'm afraid, it could give us
less profit (performance) than pain (complexity).
> It's not a major problem in system mode because generally the system is
> halted when changes are made to the list. However I'd like to solve it
> properly for both system and user-mode so I can then forgot about
> another special case.
Could you please explain a bit more about problems in user-mode?
Thanks,
Sergey
next prev parent reply other threads:[~2016-06-20 18:16 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-17 16:33 [Qemu-devel] [RFC 0/7] Safe watch and breakpoint manipulation Alex Bennée
2016-06-17 16:33 ` [RFC 1/7] cpu: move break/watchpoints into arrays Alex Bennée
2016-06-17 16:33 ` [Qemu-devel] " Alex Bennée
2016-06-17 17:03 ` Paolo Bonzini
2016-06-17 17:03 ` [Qemu-devel] " Paolo Bonzini
2016-06-17 16:33 ` [RFC 2/7] exec: keep CPUWatchpoint references internal Alex Bennée
2016-06-17 16:33 ` [Qemu-devel] " Alex Bennée
2016-06-17 17:17 ` Paolo Bonzini
2016-06-17 17:17 ` [Qemu-devel] " Paolo Bonzini
2016-06-17 16:33 ` [RFC 3/7] exec: keep CPUBreakpoint " Alex Bennée
2016-06-17 16:33 ` [Qemu-devel] " Alex Bennée
2016-06-17 16:33 ` [RFC 4/7] break/watchpoints: store inside array Alex Bennée
2016-06-17 16:33 ` [Qemu-devel] " Alex Bennée
2016-06-17 17:15 ` Paolo Bonzini
2016-06-17 17:15 ` [Qemu-devel] " Paolo Bonzini
2016-06-17 16:33 ` [Qemu-devel] [RFC 5/7] breakpoints: put breakpoints under RCU control Alex Bennée
2016-06-17 16:59 ` Paolo Bonzini
2016-06-17 16:33 ` [Qemu-devel] [RFC 6/7] linux-user: don't clone watchpoints Alex Bennée
2016-06-17 17:18 ` Paolo Bonzini
2016-06-17 16:33 ` [Qemu-devel] [RFC 7/7] watchpoints: put watchpoints under RCU control Alex Bennée
2016-06-17 17:10 ` Paolo Bonzini
2016-06-17 17:01 ` [Qemu-devel] [RFC 0/7] Safe watch and breakpoint manipulation Paolo Bonzini
2016-06-20 13:55 ` Sergey Fedorov
2016-06-20 14:25 ` Paolo Bonzini
2016-06-20 15:23 ` Sergey Fedorov
2016-06-20 15:49 ` Sergey Fedorov
2016-06-20 16:08 ` Paolo Bonzini
2016-06-20 16:27 ` Alex Bennée
2016-06-20 18:16 ` Sergey Fedorov [this message]
2016-06-20 18:19 ` Sergey Fedorov
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=576832F4.5080202@gmail.com \
--to=serge.fdrv@gmail.com \
--cc=a.rigo@virtualopensystems.com \
--cc=alex.bennee@linaro.org \
--cc=bobby.prani@gmail.com \
--cc=claudio.fontana@huawei.com \
--cc=cota@braap.org \
--cc=fred.konrad@greensocs.com \
--cc=jan.kiszka@siemens.com \
--cc=mark.burton@greensocs.com \
--cc=mttcg@greensocs.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.