From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id ABD5AC433FE for ; Tue, 18 Oct 2022 21:03:10 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230238AbiJRVDI (ORCPT ); Tue, 18 Oct 2022 17:03:08 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:47040 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230203AbiJRVDF (ORCPT ); Tue, 18 Oct 2022 17:03:05 -0400 Received: from mga09.intel.com (mga09.intel.com [134.134.136.24]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 5153BC4587 for ; Tue, 18 Oct 2022 14:02:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1666126973; x=1697662973; h=message-id:date:mime-version:subject:to:cc:references: from:in-reply-to:content-transfer-encoding; bh=HaNZmq41zK29iOnkJK28GdD5R+VHcXlZCvrP5NcvQyo=; b=VDnNTv+6K7/mM81eb0AkSO8eZ+eNSDa4KNZFSrmCWpoAncWRfZVpD4eG u9Jk+MrQCge1rufRo+w5KVemKaHAyBlpBuqhb4rdlBR6hxxek0+66i5fW PtpFmxqAGggF678MMTE/cIuz+Ti1HTpCJPRtZFm9pdMhFocf/V+O+DWNg vZiGR4ojlr+RghVrsIaaVl+UzH284rd3KpylReh8IydfrUM782Ji1gKT9 MYJiVm/E/EYnhP6HGUWFECj6ieFrQcEKnaZGqw/a7xCWzuFMHzT40uNHT ntJbPjnHC57eilYYsVA+BK+LIBWT21t62p3nfJxoLzK2d1yth8pH8tcC8 Q==; X-IronPort-AV: E=McAfee;i="6500,9779,10504"; a="307343803" X-IronPort-AV: E=Sophos;i="5.95,194,1661842800"; d="scan'208";a="307343803" Received: from fmsmga007.fm.intel.com ([10.253.24.52]) by orsmga102.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 18 Oct 2022 14:02:45 -0700 X-IronPort-AV: E=McAfee;i="6500,9779,10504"; a="631323993" X-IronPort-AV: E=Sophos;i="5.95,194,1661842800"; d="scan'208";a="631323993" Received: from jjsopko-mobl.amr.corp.intel.com (HELO [10.213.163.40]) ([10.213.163.40]) by fmsmga007-auth.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 18 Oct 2022 14:02:44 -0700 Message-ID: Date: Tue, 18 Oct 2022 14:02:43 -0700 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.2.2 Subject: Re: [PATCHv10 09/15] x86: Expose untagging mask in /proc/$PID/arch_status Content-Language: en-US To: "Kirill A. Shutemov" , Dave Hansen , Andy Lutomirski , Peter Zijlstra Cc: x86@kernel.org, Kostya Serebryany , Andrey Ryabinin , Andrey Konovalov , Alexander Potapenko , Taras Madan , Dmitry Vyukov , "H . J . Lu" , Andi Kleen , Rick Edgecombe , Bharata B Rao , Jacob Pan , Ashok Raj , linux-mm@kvack.org, linux-kernel@vger.kernel.org References: <20221018113358.7833-1-kirill.shutemov@linux.intel.com> <20221018113358.7833-10-kirill.shutemov@linux.intel.com> From: Dave Hansen In-Reply-To: <20221018113358.7833-10-kirill.shutemov@linux.intel.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 10/18/22 04:33, Kirill A. Shutemov wrote: > Add a line in /proc/$PID/arch_status to report untag_mask. It can be > used to find out LAM status of the process from the outside. It is > useful for debuggers. Considering that address masking is not x86-specific, it seems like this needs a better home (another file in /proc). This could even be left out of the series for now, right? Nothing, including the selftests, depends on it.