From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id D204D3858D39; Tue, 3 Jan 2023 18:22:07 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org D204D3858D39 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1672770127; bh=5aY9Rp3cvkjs9ShyjCBHgldfSUzdm9O+vDWiHd4IhYY=; h=From:To:Subject:Date:In-Reply-To:References:From; b=qz4/VJIebvrGMTuc2PTr11aMdDGcTITpF2Qj860YGXkKSUdD2NDDvmhrS3NSs8oJw EVxXpujGi+qPRDCVwvKVKS6KgfoM3+HKUn+tyoUW78N1mf2bOqBI9nQNA5Ur+aTdAB Ino8nH+DmKtxVWhOyIWQTstPRtIcZNn/unCeM2Bg= From: "hjl.tools at gmail dot com" To: glibc-bugs@sourceware.org Subject: [Bug dynamic-link/29953] Invalid x86_non_temporal_threshold without cache info Date: Tue, 03 Jan 2023 18:22:07 +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: hjl.tools 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: In-Reply-To: References: 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: https://sourceware.org/bugzilla/show_bug.cgi?id=3D29953 --- Comment #10 from H.J. Lu --- (In reply to Noah Goldstein from comment #9) > Created attachment 14552 [details] > Fix with new API for clamping tunable value >=20 > Personally more infavor of an approach like this. >=20 > Seems a bit insane that when we have a minval > 0, we default to potentia= lly > leaving the tunable at zero. TUNABLE_SET_WITH_BOUNDS is used to update dynamic bounds for display purpos= e. The tunable value may be retrieved before TUNABLE_SET_WITH_BOUNDS. --=20 You are receiving this mail because: You are on the CC list for the bug.=