From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753327AbbFHQbi (ORCPT ); Mon, 8 Jun 2015 12:31:38 -0400 Received: from mga11.intel.com ([192.55.52.93]:39973 "EHLO mga11.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752894AbbFHQbb (ORCPT ); Mon, 8 Jun 2015 12:31:31 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.13,574,1427785200"; d="scan'208";a="584138226" Date: Mon, 8 Jun 2015 09:30:20 -0700 (PDT) From: Vikas Shivappa X-X-Sender: vikas@vshiva-Udesk To: Thomas Gleixner cc: Vikas Shivappa , linux-kernel@vger.kernel.org, vikas.shivappa@intel.com, x86@kernel.org, hpa@zytor.com, mingo@kernel.org, tj@kernel.org, peterz@infradead.org, matt.fleming@intel.com, will.auld@intel.com, kanaka.d.juvva@intel.com Subject: Re: [PATCH 08/10] x86/intel_rdt: Implement scheduling support for Intel RDT In-Reply-To: Message-ID: References: <1433462497-27087-1-git-send-email-vikas.shivappa@linux.intel.com> <1433462497-27087-9-git-send-email-vikas.shivappa@linux.intel.com> 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 On Sat, 6 Jun 2015, Thomas Gleixner wrote: > On Thu, 4 Jun 2015, Vikas Shivappa wrote: >> +static inline void intel_rdt_sched_in(void) >> +{ >> + if (static_key_false(&rdt_enable_key)) >> + __intel_rdt_sched_in(); > > So if the enable_key is FALSE we call the RDT stuff? I might be > missing something important, but this does not make any sense and I > have to ask how that whole stuff has been tested. > >> /* >> * Protects cache_cgroups and cqm_rmid_free_lru and cqm_rmid_limbo_lru. >> @@ -403,8 +384,8 @@ static void __intel_cqm_event_count(void *info); >> static u32 intel_cqm_xchg_rmid(struct perf_event *group, u32 rmid) >> { >> struct perf_event *event; >> - struct list_head *head = &group->hw.cqm_group_entry; >> u32 old_rmid = group->hw.cqm_rmid; >> + struct list_head *head = &group->hw.cqm_group_entry; > > And this change is necessary because? Was a minor thing. Changed this to keep the length in increasing order but it should have been decreasing order to be consistent with other functions in cqm. For some reason the length was actually in increasing order in earlier versions of cqm. Will fix this. Thanks, Vikas > > Thanks, > > tglx >