From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:38529) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YlFFf-0000B7-JM for qemu-devel@nongnu.org; Thu, 23 Apr 2015 07:25:04 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YlFFb-0006bQ-5l for qemu-devel@nongnu.org; Thu, 23 Apr 2015 07:25:03 -0400 Received: from mail-pa0-x231.google.com ([2607:f8b0:400e:c03::231]:35229) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YlFFa-0006bF-UD for qemu-devel@nongnu.org; Thu, 23 Apr 2015 07:24:59 -0400 Received: by pabtp1 with SMTP id tp1so15683239pab.2 for ; Thu, 23 Apr 2015 04:24:58 -0700 (PDT) Date: Thu, 23 Apr 2015 21:24:49 +1000 From: "Edgar E. Iglesias" Message-ID: <20150423112449.GT30629@toto> References: <1429722561-12651-1-git-send-email-greg.bellows@linaro.org> <1429722561-12651-10-git-send-email-greg.bellows@linaro.org> <20150423024929.GC17116@toto> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Subject: Re: [Qemu-devel] [PATCH v2 9/9] target-arm: Add WFx instruction trap support List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Peter Maydell Cc: Sergey Fedorov , Alex =?iso-8859-1?Q?Benn=E9e?= , QEMU Developers , Greg Bellows On Thu, Apr 23, 2015 at 11:57:10AM +0100, Peter Maydell wrote: > On 23 April 2015 at 11:39, Edgar E. Iglesias wrote: > > > > On 23/04/2015 6:00 pm, "Peter Maydell" wrote: > >> In theory you could maybe check has_work() for the WFI case, > >> since doing an EXCP_HLT really should cause us to stop until > >> has_work is true, but it seems a bit fragile -- could we really > >> guarantee that nothing would change between this point and > >> when we went back through the main loop that would change > >> whether has_work evaluates true or not? I think that it's better > >> there too to just always take the trap: setting EXCP_HLT is our > >> "going into a low power state" and so we should take the trap > >> if we would otherwise have done that. > > > > I think functional wise we are OK. > > The implementation can AFAIK always choose to nop for whatever reason (e.g > > has_work()). Only when we choose to enter low power, the trap comes into > > play. > > Ah, so in helper_wfi() do something like > > if (!has_work()) { > if (trapping wfi) { > EXCP_UDEF code; > } else { > EXCP_HALT code; > } > } > /* otherwise just return, making this WFI a nop */ > > ? > > I think that would work. Yes. Maybe we can consider YIELD instead of NOP when has_work() is true as a WFI is probably a good hint from guests to reschedule QEMU CPUs. > > > Maybe wfe is the most problematic one because it fires more frequently and > > often when has_work() is true? > > Yes, I think we should start by not trapping on WFE and then look > at how good/bad perf is. Sounds good to me. Thanks! Edgar