From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mike Travis Date: Wed, 09 Dec 2009 18:10:39 +0000 Subject: Re: [PATCH] mm/vmalloc: don't use vmalloc_end Message-Id: <4B1FE81F.30408@sgi.com> List-Id: References: <4B1D3A3302000078000241CD@vpn.id2.novell.com> <20091207153552.0fadf335.akpm@linux-foundation.org> <4B1E1B1B0200007800024345@vpn.id2.novell.com> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: Christoph Lameter Cc: tony.luck@intel.com, Andrew Morton , Jan Beulich , Tejun Heo , linux-mm@kvack.org, Geert Uytterhoeven , linux-ia64@vger.kernel.org, linux-kernel@vger.kernel.org Christoph Lameter wrote: > On Tue, 8 Dec 2009, Jan Beulich wrote: > >> According to Tejun the problem is just cosmetic (i.e. causes build >> warnings), since the functions affected aren't being used (yet) on >> ia64. So feel free to drop the patch again, given that he has a patch >> queued to address the issue by renaming the arch variable. > > I thought the new code must be used in order for the new percpu allocator > to work? Or is this referring to other code? > >> I wonder though why that code is being built on ia64 at all if it's not >> being used (i.e. why it doesn't depend on a CONFIG_*, HAVE_*, or >> NEED_* manifest constant). > > Tony: Can you confirm that the new percpu stuff works on IA64? (Or is > there nobody left to care?) Christoph, I have access to a 640p system for a couple more weeks if there's anything you'd like me to check out. Thanks, Mike