From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:36413) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YDLGc-0007zC-FC for qemu-devel@nongnu.org; Mon, 19 Jan 2015 17:57:55 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YDLGZ-00045F-8N for qemu-devel@nongnu.org; Mon, 19 Jan 2015 17:57:54 -0500 Received: from mail-oi0-x233.google.com ([2607:f8b0:4003:c06::233]:33832) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YDLGZ-000453-4F for qemu-devel@nongnu.org; Mon, 19 Jan 2015 17:57:51 -0500 Received: by mail-oi0-f51.google.com with SMTP id x69so8492384oia.10 for ; Mon, 19 Jan 2015 14:57:49 -0800 (PST) Date: Tue, 20 Jan 2015 08:54:16 +1000 From: "Edgar E. Iglesias" Message-ID: <20150119225416.GB24013@toto> References: <1413910544-20150-1-git-send-email-greg.bellows@linaro.org> <1413910544-20150-6-git-send-email-greg.bellows@linaro.org> <54BD426A.5070107@twiddle.net> <54BD5B6B.6090708@twiddle.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <54BD5B6B.6090708@twiddle.net> Subject: Re: [Qemu-devel] [PATCH v7 05/32] target-arm: make arm_current_el() return EL3 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Richard Henderson Cc: Peter Maydell , Sergey Fedorov , QEMU Developers , Fabian Aggeler , Greg Bellows On Mon, Jan 19, 2015 at 11:30:51AM -0800, Richard Henderson wrote: > On 01/19/2015 11:00 AM, Peter Maydell wrote: > > Alternatively (better!), for a lot of the tlb_flush()es triggered > > by target-arm code we could be more precise about the affected > > mmu_idx values, since the common case is going to be > > "NS EL1 did something that needs a TLB flush", and by definition > > that can't affect TLB entries for EL2, EL3 or S-EL1/EL0. > > > > So I think my preference would be to use 7 mmu indexes, > > and add a tlb_flush_mmuidx() function. (Assuming I'm > > not missing anything that makes that not workable...) > > That new interface does seem very reasonable. > > As to whether you've missed something in the ARM semantics, > I guess we'll find out. ;-) > Sounds like a good option to me too. Cheers, Edgar