From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-wm1-f74.google.com (mail-wm1-f74.google.com [209.85.128.74]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 1F12647DD72 for ; Wed, 21 Jan 2026 09:45:25 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=209.85.128.74 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1768988728; cv=none; b=A0WIyENTxfhG/g4EYqN/Xeyo4abh9spJ0mP0agy095E+0VdZsexPSYOhYR3IciO9H0iIenWa98Nf1dCW7OMRdiK69aBEV/7ifDisEkLU4bGj8L376N6NZgGthI2n2JiblqbWET84bQq0PrSdzJzx/aidOAfhlEjyEvTwjKGA0f8= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1768988728; c=relaxed/simple; bh=ZzMvEJPUcDpg2FRsjtHlf0t5SKeF6HmeKgid+xQDJ5s=; h=Date:In-Reply-To:Mime-Version:References:Message-ID:Subject:From: To:Cc:Content-Type; b=ibGH+OfmPUubtXm3yGHL86gjI9IP/oTnWkhFvcXdABfjlzwOd7+WR33oY/cGQ0ElB0xxye0QcqSAxHqm4fyYwHhyie4lCSf6UCNMtE5qdu9E25XC3GP53yzHzhHGOcwujdOBuIcldpTyd282vwO1uY9fGdyodk3+NUvWiVX8cgM= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=reject dis=none) header.from=google.com; spf=pass smtp.mailfrom=flex--jackmanb.bounces.google.com; dkim=pass (2048-bit key) header.d=google.com header.i=@google.com header.b=otyKXA7i; arc=none smtp.client-ip=209.85.128.74 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=reject dis=none) header.from=google.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=flex--jackmanb.bounces.google.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=google.com header.i=@google.com header.b="otyKXA7i" Received: by mail-wm1-f74.google.com with SMTP id 5b1f17b1804b1-47d5bd981c8so48547735e9.0 for ; Wed, 21 Jan 2026 01:45:25 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20230601; t=1768988724; x=1769593524; darn=vger.kernel.org; h=cc:to:from:subject:message-id:references:mime-version:in-reply-to :date:from:to:cc:subject:date:message-id:reply-to; bh=Gghs4HmZuAZUYe8i+9UuXL2fYyVqn4MLWTMMYop8B0U=; b=otyKXA7itJ7Tmf9yYxfgS9Ue5oE0uLmAsN9rdg2IBO1QcaCo0qkJuSeaodp29n1kRp l8WQP2SwQURE1NkMw2oqZX9fhuEJe9sbzQvq5DqpnrPRNIFFv2qJDjeM4hWuoD/ziKRr cAFXTGkXxdit1tqWVie5S8rWJ2fTPOBC8HsS5iXgD4POMkk8uRLKrqcWdqTDF4h29G9w 60puRNw5jp9oTWScgGK40TdZWg6pj/qcEnG8piCdfqhYA7FXfGMoPS6qBPm1p46DeOM2 LVWcrUAPD4aBv7TUasUsz8y4OJC39TMceeNgDCNhiLHC5SLytWbFcbTkE5YqoiR1P9dk b6Vw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1768988724; x=1769593524; h=cc:to:from:subject:message-id:references:mime-version:in-reply-to :date:x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=Gghs4HmZuAZUYe8i+9UuXL2fYyVqn4MLWTMMYop8B0U=; b=v7VdlJstzAq+lu+t/p9Ev3OBr2XEc3TgvvQX+JiLlrV+ws/D7boMFKz37qrHVQeUqB D68dSaGydkCJw2pfS9SvXsgGnKX1eVxlHpjmbQGLUwxMEd9lqoTPnz8zJtBoO0Bbtk+L nkDCqnT7oVMYu8q41UY7mTAUVeFodx5OJBUxocmppEdDV/G3l80tcyxgeAy77wojsIzc OIqdJtAJp5OijvTBaKTSb5IJtpdoqzSRIRSsskMeVopw7XQeMEqXPOctVbaXJK5jjJTS YlJ5f3m/imBMHpGIAYVWL0Ad6cjrrgZzBRZeOYeC5E40Jz3vOEzgQ7olD41Vwhxxq0Lp g1LA== X-Forwarded-Encrypted: i=1; AJvYcCVKka79/lU2t5U21FC1v5ESGOF5xTxQ657Da+8o+ZmzktFowpDCpmvycLfETF2+CQ5HndC81sCfBSYK1To=@vger.kernel.org X-Gm-Message-State: AOJu0Yw6nlk/XNYGOnH9NNdqVez2k51LHktCAeNDFCP0qzwJjvGJXmta eS5LECF7v8FkadX1L+JD8/VSbgU7jmFw4zllj+HJ7tKEWCjuejyP4pEILFtiOfHKb3AGdLEHbiL Cqx6p7E1NqhPQMw== X-Received: from wmpq42.prod.google.com ([2002:a05:600c:332a:b0:480:43b6:1171]) (user=jackmanb job=prod-delivery.src-stubby-dispatcher) by 2002:a05:600c:4e92:b0:475:de14:db1e with SMTP id 5b1f17b1804b1-4801eb0426fmr243434915e9.24.1768988723921; Wed, 21 Jan 2026 01:45:23 -0800 (PST) Date: Wed, 21 Jan 2026 09:45:22 +0000 In-Reply-To: <20260120163728.GDaW-vSLGY1P_E0DqS@fat_crate.local> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: Mime-Version: 1.0 References: <20250924-b4-asi-page-alloc-v1-0-2d861768041f@google.com> <20250924-b4-asi-page-alloc-v1-5-2d861768041f@google.com> <08338619-6aa1-4905-bdf8-bf1a90857307@intel.com> <19e5012a-3c58-4696-9e4e-39e2b7d2b5af@intel.com> <20260120163728.GDaW-vSLGY1P_E0DqS@fat_crate.local> X-Mailer: aerc 0.21.0 Message-ID: Subject: Re: [PATCH 05/21] x86/mm/pat: mirror direct map changes to ASI From: Brendan Jackman To: Borislav Petkov , Brendan Jackman Cc: Dave Hansen , Andy Lutomirski , Lorenzo Stoakes , "Liam R. Howlett" , Suren Baghdasaryan , Michal Hocko , Johannes Weiner , Zi Yan , Axel Rasmussen , Yuanchu Xie , Roman Gushchin , , , , , , , , , , , , , , , , Yosry Ahmed Content-Type: text/plain; charset="UTF-8" On Tue Jan 20, 2026 at 4:37 PM UTC, Borislav Petkov wrote: > On Thu, Oct 02, 2025 at 05:08:59PM +0000, Brendan Jackman wrote: >> OK, then it probably just sounds wrong to me because I'm steeped in the >> current jargon. For v2 I'll try just dropping "[un]restricted". > > So AFAIU, we have two address spaces - the full one - which has *everything* > mapped in and the limited one, with things removed from it. Right? > > So calling the unrestricted "the full address space" makes sense to me. I.e., > it has *everything* in it. > > And then there's the subset of the full address space which has holes in it. > Looking at Merriam Webster, it suggests those antonyms to "complete": > > partial, incomplete, reduced, abbreviated, diminished. > > Yahaa, they all make sense. > > "partial address space" sounds good to me. "Reduced" even better. So having > the full and the reduced address space would make the nomenclature very easy, > IMO. > > Thoughts? Full/partial sounds like good naming for the address spaces, but that doesn't help with the issue that we have two related concepts that we need jargon for: 1. Address spaces (current patch's terminology: restricted/unrestricted) 2. The property of some memory being mapped or unmapped in the "restricted"/"partial"/"sensitive" address space (current patch's terminology: sensitive/nonsensitive). IIUC Dave's complaint wasn't that the word choices don't work for their respective concepts. His issue was that we have separte jargon for 1 and 2 even though they are closely entangled concepts. Since I'm now convinced that "sensitive/nonsensitive" makes sense for both, I think we should stick to that.