From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:37812)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <fred.konrad@greensocs.com>) id 1Y9FuP-0003Ps-FF
	for qemu-devel@nongnu.org; Thu, 08 Jan 2015 11:26:07 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <fred.konrad@greensocs.com>) id 1Y9FuM-0003yv-AN
	for qemu-devel@nongnu.org; Thu, 08 Jan 2015 11:26:05 -0500
Received: from [2001:41d0:8:2b42::1] (port=35501 helo=greensocs.com)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <fred.konrad@greensocs.com>) id 1Y9FuM-0003ya-1S
	for qemu-devel@nongnu.org; Thu, 08 Jan 2015 11:26:02 -0500
Message-ID: <54AEAF96.3050700@greensocs.com>
Date: Thu, 08 Jan 2015 17:25:58 +0100
From: Frederic Konrad <fred.konrad@greensocs.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [Qemu-devel] goal of tb_lock in cpu-exec?
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: qemu-devel <qemu-devel@nongnu.org>, mttcg@listserver.greensocs.com
Cc: Peter Maydell <peter.maydell@linaro.org>

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