Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757572AbbFQQZ6 (ORCPT ); Wed, 17 Jun 2015 12:25:58 -0400 Received: from mga11.intel.com ([192.55.52.93]:39795 "EHLO mga11.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751001AbbFQQZw (ORCPT ); Wed, 17 Jun 2015 12:25:52 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.13,633,1427785200"; d="scan'208";a="748445158" Date: Wed, 17 Jun 2015 09:23:07 -0700 (PDT) From: Vikas Shivappa X-X-Sender: vikas@vshiva-Udesk To: Peter Zijlstra cc: Vikas Shivappa , Vikas Shivappa , linux-kernel@vger.kernel.org, x86@kernel.org, hpa@zytor.com, tglx@linutronix.de, mingo@kernel.org, Matt Fleming , "Juvva, Kanaka D" , "Williamson, Glenn P" , "Auld, Will" Subject: Re: [PATCH 10/10] x86/intel_rdt: Intel haswell Cache Allocation enumeration In-Reply-To: <20150616091857.GK3644@twins.programming.kicks-ass.net> Message-ID: References: <1434133037-25189-1-git-send-email-vikas.shivappa@linux.intel.com> <1434133037-25189-11-git-send-email-vikas.shivappa@linux.intel.com> <20150615140503.GD3644@twins.programming.kicks-ass.net> <20150616091857.GK3644@twins.programming.kicks-ass.net> User-Agent: Alpine 2.10 (DEB 1266 2009-07-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1546 Lines: 45 On Tue, 16 Jun 2015, Peter Zijlstra wrote: > On Mon, Jun 15, 2015 at 02:44:32PM -0700, Vikas Shivappa wrote: >>> Secondly, there's more HSW models: >>> >>> case 60: /* 22nm Haswell Core */ >>> case 63: /* 22nm Haswell Server */ >>> case 69: /* 22nm Haswell ULT */ >>> case 70: /* 22nm Haswell + GT3e (Intel Iris Pro graphics) */ >>> >>> Is this really only HSW server, >> >> Yes , this probe is only targeted at HSW servers as of now. > > But do the others have it? What you're targeting this code for is > irrelevant, if those models have the hardware we should support them. > >> or should they all be listed? > > If they support it, yes. In any case, be explicit on which models have > the hardware. IIRC your current Changelog has the words 'certain SKUs' > in, which is as ambiguous as one can get. Its a little confusing because the quirks we have to use in the clients or even the details of those is not public. Hence the linux kernel would only support it in servers for now. Just checked the latest info again and its the same status as of now. As far as servers are concerned , its only supported in certain SKUs and subSKus and some require a ucode patch. The probe should takes care of them all.. Hope that answers both the questions. Thanks, Vikas > -- 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/