Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp1108235imu; Tue, 11 Dec 2018 12:52:19 -0800 (PST) X-Google-Smtp-Source: AFSGD/Vqugznt7LaQLMLt1CzXthW42ptYSsxZQ2ZUw4nN/p5dJ6qffWRTAN8yESKW4Eg+8E4f78F X-Received: by 2002:a63:c141:: with SMTP id p1mr15965276pgi.424.1544561539796; Tue, 11 Dec 2018 12:52:19 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1544561539; cv=none; d=google.com; s=arc-20160816; b=bPvt5x9lnglEugKuqo5pgVVqxlmcDsYmStSnB/aMOjrEAaGdH4cfEDYjW4fVCk3H3n 9mJGUU1AYz/O9iDm93lPLWhpozzU6SsehjQPembS9MKiIY+4cxVKkt71cvT+ljQeiHga PC1braHd8gErSMPRX9kUB8c7qV1xMuB8OwbY1QaWh6QBA994sTm49tsVkfd+2qYnbGMe jX0ZmzEEhDBRFseNPSJtR5VRh827Rtz7MQ6B8hlMeqHBJ9BxYF8hbKp1j2rNxn4CRK7b 9tlGs61Rfad0tjpLmeV/lhjv1KZjuC3yQ7qVQr9w1ufsnkfMbB6Up9pwFgR235fxKJwf +B0Q== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject; bh=FCFZSM6VO5TC0snahsiLAZ0yCGepzLOFj1wcaIO2GhM=; b=VPpDYVd9MRJELEXZx7qN6KbLZKdv58V63sdg2wrXeCqVYqTvwKwN9jD0tK4ao81oqy 8TV6VQO1Kn1m1H/Wm4e4CdZCv7crQTOLiYZK85R0WDMBrTAxOqHoyte9mFk9BH3pmZmb ECIItjiCQDWX7GljxM85dQ0nbpuGmPgjHaYa4jVlZsCnXt/PEJCza4ze2jE8l/05Cu0K T8HXVQ6GteHToPRFH0Nmbv2pNeO4KuGeLfY2Uq5Doxd+XSshkQvDZdiZSwGg/qRL5odc tl8AfwB0yzjEheSeDhEKV2N3MyXoYZTofeeAl3tSHdly9mtMZL64GeHTDckT2c/nVCDR D7Xw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id l1si13583069pld.324.2018.12.11.12.52.04; Tue, 11 Dec 2018 12:52:19 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726211AbeLKUvN (ORCPT + 99 others); Tue, 11 Dec 2018 15:51:13 -0500 Received: from mga02.intel.com ([134.134.136.20]:52621 "EHLO mga02.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726134AbeLKUvN (ORCPT ); Tue, 11 Dec 2018 15:51:13 -0500 X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga007.jf.intel.com ([10.7.209.58]) by orsmga101.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 11 Dec 2018 12:51:12 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.56,343,1539673200"; d="scan'208";a="97977143" Received: from rchatre-mobl.amr.corp.intel.com (HELO [10.24.14.157]) ([10.24.14.157]) by orsmga007.jf.intel.com with ESMTP; 11 Dec 2018 12:51:12 -0800 Subject: Re: [PATCH V2] x86/intel_rdt: Ensure usage of CPUs are locked while needed To: Borislav Petkov Cc: tglx@linutronix.de, fenghua.yu@intel.com, tony.luck@intel.com, gavin.hindman@intel.com, jithu.joseph@intel.com, mingo@redhat.com, hpa@zytor.com, x86@kernel.org, linux-kernel@vger.kernel.org, stable@vger.kernel.org References: <20181211123404.GC27375@zn.tnic> <20181211185059.GP27375@zn.tnic> <20181211204310.GQ27375@zn.tnic> From: Reinette Chatre Message-ID: <10fef6af-785e-c76f-d89b-ec115dcf460a@intel.com> Date: Tue, 11 Dec 2018 12:51:12 -0800 User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 In-Reply-To: <20181211204310.GQ27375@zn.tnic> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Boris, On 12/11/2018 12:43 PM, Borislav Petkov wrote: > On Tue, Dec 11, 2018 at 11:02:08AM -0800, Reinette Chatre wrote: >> I just wanted to emphasize that it is not the schemata writing that >> needs to be protected, but instead the pseudo-locking code that runs >> after schemata programming that needs to run on a particular CPU. The >> new patch subject could be interpreted to mean the former ... but that >> is starting to sound like nitpicking by me. > > Nah, that's not nitpicking - it is important that we sort out stuff > fully before committing. I really appreciate your patience. > > Now, I'm trying to understand what you're telling me and I believe you > mean what update_domains() does, yes? Yes. > > And I guess a more fitting subject in that case could be: > > x86/intel_rdt: Ensure a CPU remains online for the region's pseudo-locking sequence > > or so, and then the commit message explains in more detail what that > title actually means. :) > > Hmmm. That subject line matches exactly the goal of this patch. Thank you very much. Would you prefer that I send a new version with this subject line or would you rather make the change yourself while applying this patch? Reinette