From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1759651AbYH2WdQ (ORCPT ); Fri, 29 Aug 2008 18:33:16 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1756163AbYH2Wc7 (ORCPT ); Fri, 29 Aug 2008 18:32:59 -0400 Received: from rv-out-0506.google.com ([209.85.198.225]:26799 "EHLO rv-out-0506.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755581AbYH2Wc7 (ORCPT ); Fri, 29 Aug 2008 18:32:59 -0400 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=SRFxi6ieI+900OTrhnElAIlRvfRWbOz3bADvYDrhLJVvumvf7Q7XkEssELtQMVAAiv CkWyj8dApbTyrGOA+nNr2SOlH5Ov0mv9c3holO48Bv/a48g0LJmeM7BdFzJ9ooxthbVq /k+hGYeb/LLAf/X9V23ijtnA177z45dCOsYak= Message-ID: <86802c440808291532r15dd581cj3f69755985578c2b@mail.gmail.com> Date: Fri, 29 Aug 2008 15:32:58 -0700 From: "Yinghai Lu" To: "Andrew Morton" Subject: Re: [PATCH] dyn_array: using %pF instead of print_fn_descriptor_symbol Cc: mingo@elte.hu, linux-kernel@vger.kernel.org In-Reply-To: <20080829152053.92fa6fd4.akpm@linux-foundation.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <1220047669-15029-1-git-send-email-yhlu.kernel@gmail.com> <20080829152053.92fa6fd4.akpm@linux-foundation.org> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Aug 29, 2008 at 3:20 PM, Andrew Morton wrote: > On Fri, 29 Aug 2008 15:07:49 -0700 > Yinghai Lu wrote: > >> + printk(KERN_DEBUG "per_cpu_dyn_array %pF ==> [%#lx - %#lx]\n", >> + da->name, phys, phys + size); > > This: > > struct dyn_array { > void **name; > > is a bit confusing. One normally expects a variable called "name" to > point at a character string. > > What _does_ this thing point at? There are no code comments which I > can find, it's unobvious from the source code, the type is the > information-free void** and the identifier is misleading. > > I find that documenting the data structures is the best way of making > code understandable (and hence maintainable). struct dyn_array { void **name; unsigned long size; unsigned int *nr; unsigned long align; void (*init_work)(void *); }; extern struct dyn_array *__dyn_array_start[], *__dyn_array_end[]; extern struct dyn_array *__per_cpu_dyn_array_start[], *__per_cpu_dyn_array_end[]; #define DEFINE_DYN_ARRAY_ADDR(nameX, addrX, sizeX, nrX, alignX, init_workX) \ static struct dyn_array __dyn_array_##nameX __initdata = \ { .name = (void **)&(nameX),\ .size = sizeX,\ .nr = &(nrX),\ .align = alignX,\ .init_work = init_workX,\ }; \ static struct dyn_array *__dyn_array_ptr_##nameX __used \ __attribute__((__section__(".dyn_array.init"))) = \ &__dyn_array_##nameX #define DEFINE_DYN_ARRAY(nameX, sizeX, nrX, alignX, init_workX) \ DEFINE_DYN_ARRAY_ADDR(nameX, nameX, sizeX, nrX, alignX, init_workX) and use is struct irq_desc *sparse_irqs; DEFINE_DYN_ARRAY(sparse_irqs, sizeof(struct irq_desc), nr_irq_desc, PAGE_SIZE, init_work); then sparse_irqs is pointer, and .name store the address of that pointer. later use *da->name = phys_to_virt(phys); to take back the dyn address. YH