From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from out-172.mta1.migadu.com (out-172.mta1.migadu.com [95.215.58.172]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 9FF2535950 for ; Wed, 10 Jun 2026 19:46:21 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=95.215.58.172 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1781120783; cv=none; b=Udqmp+pY4VPEMWYaHNMzg0mINV/tXOfn6XlJwXaGHwM++AKWAeVOd6h02o0oAmjjrOYBCD89rpWgSPgkA5YFQBC+3LKYnBGTv+TIdhQZ5vpReAku1MjDcDdGz3FQbgGH4Apq1Ju3xyqoB/nBPIQqvgHCL/gThlwOiEv+jiz4FPM= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1781120783; c=relaxed/simple; bh=Erlrx+OlP6TgdSE6AUVAhM/b26OGzjgbX6atINTlYa8=; h=MIME-Version:Date:Content-Type:From:Message-ID:Subject:To:Cc; b=drIdqMT/TnRF5FQRceNjLGbp73Wu6gJpdRjNQax+N0v4mN/QueH81WhatHQFv/R4OLKEbKQpY275W2rfgeBp2JJo2l5TgkJirBX3R2QAfIvw4XkFZFyx0WH9xS4P9ywLhSvwmHEkOxeksxks33W096Zc0vFMVohcifSTFwvW3wU= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=rjp.ie; spf=pass smtp.mailfrom=rjp.ie; dkim=pass (1024-bit key) header.d=rjp.ie header.i=@rjp.ie header.b=uj8kYFay; arc=none smtp.client-ip=95.215.58.172 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=rjp.ie Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=rjp.ie Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=rjp.ie header.i=@rjp.ie header.b="uj8kYFay" Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rjp.ie; s=key1; t=1781120779; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding; bh=Erlrx+OlP6TgdSE6AUVAhM/b26OGzjgbX6atINTlYa8=; b=uj8kYFayXpt55+NduC4PzgCx+Lap5VPPseEl03enD+jlA9LSzt+Per7H5PQTd6VE5mFuOz 0yi1B1ivE6wdqMZH6wGt0ZU1WRrR9l3CAYUkMK5XtV+RxgTlERNxRN8yAAjZMxtKF2T7EG vYJO5m1Lms52gCz8Y7Lc182K4ivxYiM= Date: Wed, 10 Jun 2026 19:46:11 +0000 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers. From: "Ronan Pigott" Message-ID: TLS-Required: No Subject: UMIP and clearcpuid= To: linux-kernel@vger.kernel.org Cc: bp@alien8.de, x86@kernel.org X-Migadu-Flow: FLOW_OUT Hi, In [1] the clearcpuid=3D flag was hidden, but afaik this remains the only= way to disable UMIP. At the time UMIP was enabled, clearcpuid was apparently determined to be the appropriate method of disablement in [2], and it rem= ains recommended by the documentation in [3]. If clearcpuid is no good, can we have a sanctioned method to disable UMIP protections instead then? [1] https://patch.msgid.link/20260520202508.160112-1-bp@kernel.org [2] https://lore.kernel.org/lkml/1478760361.2551.21.camel@ranerica-deskto= p/ [3] https://docs.kernel.org/arch/x86/cpuinfo.html#the-feature-is-disabled= -at-boot-time Cheers, Ronan