From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753788AbdDNO3R (ORCPT ); Fri, 14 Apr 2017 10:29:17 -0400 Received: from Galois.linutronix.de ([146.0.238.70]:42321 "EHLO Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751852AbdDNO3Q (ORCPT ); Fri, 14 Apr 2017 10:29:16 -0400 Date: Fri, 14 Apr 2017 16:29:10 +0200 (CEST) From: Thomas Gleixner To: Shivappa Vikas cc: Vikas Shivappa , x86@kernel.org, LKML , "H. Peter Anvin" , Ingo Molnar , ravi.v.shankar@intel.com, Tony Luck , fenghua.yu@intel.com, Peter Zijlstra Subject: Re: [PATCH 0/8 V4] x86/intel_rdt: Intel Memory bandwidth allocation In-Reply-To: Message-ID: References: <1491611637-20417-1-git-send-email-vikas.shivappa@linux.intel.com> User-Agent: Alpine 2.20 (DEB 67 2015-01-07) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, 13 Apr 2017, Thomas Gleixner wrote: > On Wed, 12 Apr 2017, Shivappa Vikas wrote: > > This series has minor changes with respect to V3 addressing all your comments. > > Was wondering if there was any feedback or if we still have a chance for 4.12. > > It's on my radar and should make it, unless there is some major hickup. To be honest, I almost dropped it because as usual you cobbled it together in a hurry just to get it out the door. I asked for putting the CBM and MBA related data into seperate structs and make a anon union of them in struct rdt_resource. Instead you went and made it a anon union of anon structs, so you did not have to change anything else in the code. What's the point of this? That's a completely useless exercise and even worse than the data lump which was there before. I also asked several times in the past to split preparatory stuff from new stuff. No, the msr_update crap comes in one go. You introduce an update function and instead of replacing _ALL_ loops you keep one and then fix it up in some completely unrelated patch. The ordering of the new struct members was also completely random along with the kernel doc comments not being aligned. As a bonus, you reimplemented roundup() open coded in the bandwidth validation function. Instead of wasting my time for another round of review and another delivery of half baken crap, I fixed it up myself. The result is pushed out to tip/x86/cpu. Please do the following: 1) Verify that it still works as I have no hardware to test it. Once you confirmed, it's going to show up in -next. So please do that ASAP, i.e. yesterday. 2) Go through the patches one by one and compare it to your own to figure out yourself how it should be done. Next time, I'm simply going to drop such crap whether that makes it miss the merge window or not. Yours grumpy tglx