Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752387Ab2BQNMF (ORCPT ); Fri, 17 Feb 2012 08:12:05 -0500 Received: from mail-bk0-f46.google.com ([209.85.214.46]:52580 "EHLO mail-bk0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751823Ab2BQNMD (ORCPT ); Fri, 17 Feb 2012 08:12:03 -0500 MIME-Version: 1.0 In-Reply-To: <20120217115627.GA25601@elte.hu> References: <20120212111914.GC21493@elte.hu> <1329178356-16645-1-git-send-email-kjwinchester@gmail.com> <20120217115627.GA25601@elte.hu> Date: Fri, 17 Feb 2012 09:12:01 -0400 Message-ID: Subject: Re: [PATCH v2] x86: Move per cpu cpu_llc_shared_map to a field in struct cpuinfo_x86 From: Kevin Winchester To: Ingo Molnar Cc: "H. Peter Anvin" , Thomas Gleixner , Borislav Petkov , Randy Dunlap , Nick Bowler , linux-kernel@vger.kernel.org Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 839 Lines: 28 On 17 February 2012 07:56, Ingo Molnar wrote: > >> >> I'm still wondering if I should I give the same treatment to: >> >> cpu_sibling_map >> cpu_core_map >> cpu_llc_id >> cpu_number >> > > Yeah, I'd definitely give them the same treatment. > > Would you like to update your series? I'd suggest you keep patch > #1 in place, as it's already probably reasonably well tested. > Sure, I'll leave that patch as #1, and add an additional patch per field. It will take me a week or two to find the time to get it all together, but I'll keep working away at it. -- Kevin Winchester -- 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/