From: Frederic Konrad <fred.konrad@greensocs.com>
To: qemu-devel <qemu-devel@nongnu.org>, mttcg@listserver.greensocs.com
Cc: Peter Maydell <peter.maydell@linaro.org>
Subject: [Qemu-devel] goal of tb_lock in cpu-exec?
Date: Thu, 08 Jan 2015 17:25:58 +0100 [thread overview]
Message-ID: <54AEAF96.3050700@greensocs.com> (raw)
Hi everybody and happy new year,
I wondered what is the goal of tb_lock in cpu-exec.c.
According to the exec-all.h it's to protect tbs and page table but why do we
have to cover the whole cpu_exec function?
I'm asking this because we planned to reuse tb_lock to protect every
access to
tb_ctx by replacing spinlock by QemuMutex.
Anybody has a clue?
Thanks,
Fred
reply other threads:[~2015-01-08 16:26 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=54AEAF96.3050700@greensocs.com \
--to=fred.konrad@greensocs.com \
--cc=mttcg@listserver.greensocs.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.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).