From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:47832) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bNgSV-0004wc-0B for qemu-devel@nongnu.org; Thu, 14 Jul 2016 09:13:43 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bNgSQ-0002pb-Ul for qemu-devel@nongnu.org; Thu, 14 Jul 2016 09:13:42 -0400 Received: from mail-wm0-x236.google.com ([2a00:1450:400c:c09::236]:37423) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bNgSQ-0002pX-Nf for qemu-devel@nongnu.org; Thu, 14 Jul 2016 09:13:38 -0400 Received: by mail-wm0-x236.google.com with SMTP id i5so112721633wmg.0 for ; Thu, 14 Jul 2016 06:13:38 -0700 (PDT) References: <1468354426-837-1-git-send-email-sergey.fedorov@linaro.org> <148a0c48-f58c-6d95-8b97-6449670019ac@redhat.com> <87wpko4edi.fsf@linaro.org> <54367505-7189-9f06-b66e-4bc4d206b8ea@redhat.com> From: Alex =?utf-8?Q?Benn=C3=A9e?= In-reply-to: <54367505-7189-9f06-b66e-4bc4d206b8ea@redhat.com> Date: Thu, 14 Jul 2016 14:13:40 +0100 Message-ID: <87h9bs4b23.fsf@linaro.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Subject: Re: [Qemu-devel] [PATCH v3 00/11] Reduce lock contention on TCG hot-path List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Paolo Bonzini Cc: Sergey Fedorov , qemu-devel@nongnu.org, mttcg@greensocs.com, fred.konrad@greensocs.com, a.rigo@virtualopensystems.com, serge.fdrv@gmail.com, cota@braap.org, bobby.prani@gmail.com, rth@twiddle.net, peter.maydell@linaro.org, patches@linaro.org, claudio.fontana@huawei.com, mark.burton@greensocs.com, jan.kiszka@siemens.com Paolo Bonzini writes: > On 14/07/2016 14:02, Alex Bennée wrote: >> Looking at the perf data it looks like the hotest part of the code now >> is cpu_get_tb_cpu_state which is required to get the initial hash to >> search for the next tb. > > It should be possible to keep the flags up-to-date in a separate field > of CPUARMState, similar to what x86 does. Possibly, there is a tension between lazy and always upto date version of the flags. But this is work for another day I think ;-) > > Paolo -- Alex Bennée