From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:39391) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QkIjM-0002D9-LE for qemu-devel@nongnu.org; Fri, 22 Jul 2011 12:37:41 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QkIjK-0002AT-P6 for qemu-devel@nongnu.org; Fri, 22 Jul 2011 12:37:40 -0400 Received: from ch1ehsobe005.messaging.microsoft.com ([216.32.181.185]:48665 helo=ch1outboundpool.messaging.microsoft.com) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QkIjK-0002A7-Ka for qemu-devel@nongnu.org; Fri, 22 Jul 2011 12:37:38 -0400 Date: Fri, 22 Jul 2011 11:37:29 -0500 From: Scott Wood Message-ID: <20110722113729.14036c41@schlenkerla.am.freescale.net> In-Reply-To: <16A74968-CCA8-44F3-8DBF-C4D409ECE868@suse.de> References: <1311211654-14326-1-git-send-email-agraf@suse.de> <1311211654-14326-7-git-send-email-agraf@suse.de> <4E298475.7000002@adacore.com> <16A74968-CCA8-44F3-8DBF-C4D409ECE868@suse.de> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH 06/23] PPC: Fix IPI support in MPIC List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Alexander Graf Cc: Elie Richa , QEMU-devel Developers On Fri, 22 Jul 2011 17:01:11 +0200 Alexander Graf wrote: > On 22.07.2011, at 16:08, Elie Richa wrote: > > > > #if MAX_IPI > 0 > > > case 0x40: /* IDE */ > > > case 0x50: > > > idx = (addr - 0x40) >> 4; > > > retval = read_IRQreg(opp, opp->irq_ipi0 + idx, IRQ_IDE); > > > break; > > > #endif > > > > These are the IPI dispatch registers which are write only, so I suppose this shouldn't be here right? > > The code was there long before me :). No idea why it is there though - it tries to read out the IDE register for 2 IPIs. Maybe it was read-write in early versions of MPIC? Scott, any idea? I don't know about early MPICs, but I don't know how you'd even define that register for read -- it's a command, not state. I suspect it's just a bug -- especially given the initialization to 1, which suggests the author saw it as just another destination register. -Scott