Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S262061AbUKJWGM (ORCPT ); Wed, 10 Nov 2004 17:06:12 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S262063AbUKJWGM (ORCPT ); Wed, 10 Nov 2004 17:06:12 -0500 Received: from fed1rmmtao04.cox.net ([68.230.241.35]:21440 "EHLO fed1rmmtao04.cox.net") by vger.kernel.org with ESMTP id S262061AbUKJWGK (ORCPT ); Wed, 10 Nov 2004 17:06:10 -0500 Date: Wed, 10 Nov 2004 15:06:08 -0700 From: Tom Rini To: Kumar Gala Cc: akpm@osdl.org, linuxppc-dev@ozlabs.org, paulus@samba.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH][PPC32] Update cpu_spec for performance monitor counters, C99, and e500 userland CPU features Message-ID: <20041110220608.GB26631@smtp.west.cox.net> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.6+20040907i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1103 Lines: 33 On Tue, Nov 09, 2004 at 08:30:43PM -0600, Kumar Gala wrote: > Andrew, > > This patch replaces the previous patch for adding performance monitor > counters to cpu_spec. > > - > > Adds the number of performance monitor counters on each PowerPC processor > has to the cpu table. Makes oprofile support a bit cleaner since we dont > need a case statement on processor version to determine the number of > counters. > > Reformatted cpu_spec to use C99 initialization. > > Added userland CPU features for SPE, Embedded Floating Point Single > precision, and Embedded Floating Point Double precision on e500. > > Signed-off-by: Kumar Gala [snip] Now that we're doing C99 inits, can we just drop the empty fields finally (And if __setup_cpu_8xx really is empty, just kill it) ? -- Tom Rini http://gate.crashing.org/~trini/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/