From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <sourceware-bugzilla@sourceware.org>
Received: by sourceware.org (Postfix, from userid 48)
	id D2F6F3858D35; Tue,  3 Jan 2023 19:24:54 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org D2F6F3858D35
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org;
	s=default; t=1672773894;
	bh=pv5FkcPN+5Wta9qR2g/OubbWPEdYaqQvOha4oCSYAOc=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=O0BRFLgUc3aDMLd5sDRHPbnejivHyUaWxksDZ9o6ALJjKG/qoxKa4Idw0dr2RFVzN
	 fzLM1s7FUTX3fIer1xvby0vWJaGJZseF+HeGEEXUsB7osc6pWEtZMg2SobhbJKMGtg
	 +PyCJ74bvp/Z2MGMbwecbhA5JS5CVSecnveC1Wi0=
From: "goldstein.w.n at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug dynamic-link/29953] Invalid x86_non_temporal_threshold without
 cache info
Date: Tue, 03 Jan 2023 19:24:54 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: glibc
X-Bugzilla-Component: dynamic-link
X-Bugzilla-Version: 2.36
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: minor
X-Bugzilla-Who: goldstein.w.n at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at sourceware dot org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-29953-131-IJzpYjXoaY@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-29953-131@http.sourceware.org/bugzilla/>
References: <bug-29953-131@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
List-Id: <glibc-bugs.sourceware.org>

https://sourceware.org/bugzilla/show_bug.cgi?id=3D29953

--- Comment #12 from Noah Goldstein <goldstein.w.n at gmail dot com> ---
(In reply to Alexis Engelke from comment #11)
> (In reply to H.J. Lu from comment #4)
> > Try this.
> This fixes the problem, thanks.
>=20
> (In reply to Noah Goldstein from comment #9)
> > Created attachment 14552 [details]
> > Fix with new API for clamping tunable value
> This also fixes the bug when tunables are enabled, but has the problem th=
at
> no clamping will happen when tunables are disabled.

We can go with H.J's fix, making the tunable setter clamping can be an
independent QOL change later on.

--=20
You are receiving this mail because:
You are on the CC list for the bug.=