From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755969AbaHFLbB (ORCPT ); Wed, 6 Aug 2014 07:31:01 -0400 Received: from mail-la0-f53.google.com ([209.85.215.53]:44461 "EHLO mail-la0-f53.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754118AbaHFLa7 (ORCPT ); Wed, 6 Aug 2014 07:30:59 -0400 Date: Wed, 6 Aug 2014 13:30:54 +0200 From: Christoffer Dall To: Peter Maydell Cc: Marc Zyngier , "kvmarm@lists.cs.columbia.edu" , arm-mail-list , lkml - Kernel Mailing List , Catalin Marinas , Thomas Gleixner , Will Deacon , Eric Auger Subject: Re: [RFC PATCH 3/9] irqchip: GIC: Convert to EOImode == 1 Message-ID: <20140806113054.GB14205@cbox> References: <1403688530-23273-1-git-send-email-marc.zyngier@arm.com> <1403688530-23273-4-git-send-email-marc.zyngier@arm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Jun 25, 2014 at 03:06:33PM +0100, Peter Maydell wrote: > On 25 June 2014 10:28, Marc Zyngier wrote: > > For this case, the GIC architecture provides EOImode == 1, where: > > - A write to the EOI register drops the priority of the interrupt and leaves > > it active. Other interrupts at the same priority level can now be taken, > > but the active interrupt cannot be taken again > > - A write to the DIR marks the interrupt as inactive, meaning it can > > now be taken again. > > > > We only enable this feature when booted in HYP mode. Also, as most device > > trees are broken (they report the CPU interface size to be 4kB, while > > the GICv2 CPU interface size is 8kB), output a warning if we're booted > > in HYP mode, and disable the feature. > > Does that mean you guarantee not to write to the DEACTIVATE > register if not booted in Hyp mode? I ask because QEMU's > GIC emulation doesn't emulate that register, so it would be > useful to know if this patch means newer kernels are going to fall > over under TCG QEMU... > > (The correct fix, obviously, is to actually implement the QEMU > support for split prio-drop and deactivate. Christoffer, you're our > GIC emulation expert now, right? :-) ) > Missed this. Sure, I can have a go at that some time, there are a number of things I've been meaning to look at in the QEMU GIC emulation code. -Christoffer