From: Siddhesh Poyarekar <siddhesh@gotplt.org>
To: DJ Delorie <dj@redhat.com>
Cc: adhemerval.zanella@linaro.org, libc-alpha@sourceware.org
Subject: Re: RFC: system-wide default tunables
Date: Tue, 17 Oct 2023 12:55:42 -0400 [thread overview]
Message-ID: <11fa1777-d31f-6968-982e-0e05900e326c@gotplt.org> (raw)
In-Reply-To: <xnr0lturi5.fsf@greed.delorie.com>
On 2023-10-17 12:45, DJ Delorie wrote:
> Siddhesh Poyarekar <siddhesh@gotplt.org> writes:
>> Only stricter overrides to systemwide tunables should be allowed,
>
> This leads to the next question: how to express these constraints in the
> tunables.conf file. A the simplest, prefixing each tunable with '+',
> '-', or '=' for example? For stricter, looser, or can't change? Else
> we need to come up with some more flexible "flag parser".
>
Actually I wasn't thinking of any conf file related constraint markup, I
was thinking of TUNABLE_CALLBACKs encoding constraints in whichever way
they deem fit. e.g. for ibt it could be:
void
TUNABLE_CALLBACK (set_x86_ibt) (tunable_val_t *valp)
{
if (!strcmp (valp->system_default, "always_on"))
return;
/* Otherwise read the value. */
}
next prev parent reply other threads:[~2023-10-17 16:55 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-04 20:55 DJ Delorie
2023-10-06 14:44 ` Adhemerval Zanella Netto
2023-10-06 17:12 ` Adhemerval Zanella Netto
2023-10-06 18:29 ` DJ Delorie
2023-10-06 19:14 ` Adhemerval Zanella Netto
2023-10-06 20:25 ` DJ Delorie
2023-10-17 14:10 ` Adhemerval Zanella Netto
2023-10-17 14:17 ` Siddhesh Poyarekar
2023-10-17 14:37 ` Siddhesh Poyarekar
2023-10-17 15:43 ` DJ Delorie
2023-10-17 15:58 ` Siddhesh Poyarekar
2023-10-17 16:45 ` DJ Delorie
2023-10-17 16:55 ` Siddhesh Poyarekar [this message]
2023-10-17 17:14 ` DJ Delorie
2023-10-18 14:20 ` Siddhesh Poyarekar
2023-10-17 17:40 ` Zack Weinberg
2023-10-17 17:47 ` DJ Delorie
2023-10-17 18:17 ` Zack Weinberg
2023-10-17 18:21 ` DJ Delorie
2023-10-06 22:04 ` DJ Delorie
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=11fa1777-d31f-6968-982e-0e05900e326c@gotplt.org \
--to=siddhesh@gotplt.org \
--cc=adhemerval.zanella@linaro.org \
--cc=dj@redhat.com \
--cc=libc-alpha@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).