From: Li Wang <li.wang@linux.dev>
To: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH v4 1/2] lib: Introduce tst_path_defs.h to consolidate system paths
Date: Thu, 21 May 2026 11:46:15 +0800 [thread overview]
Message-ID: <ag6AB0v9am5pNoLQ@linux.dev> (raw)
In-Reply-To: <20260521032759.18727-1-li.wang@linux.dev>
Li Wang wrote:
...
> +/* KERNEL */
> +#define PATH_KERNEL_HOSTNAME "/proc/sys/kernel/hostname"
> +#define PATH_KERNEL_OSRELEASE "/proc/sys/kernel/osrelease"
> +#define PATH_KERNEL_VERSION "/proc/sys/kernel/version"
> +#define PATH_KERNEL_DOMAINNAME "/proc/sys/kernel/domainname"
> +#define PATH_KERNEL_PRINTK "/proc/sys/kernel/printk"
> +#define PATH_KERNEL_PID_MAX "/proc/sys/kernel/pid_max"
> +#define PATH_KERNEL_SHMMAX "/proc/sys/kernel/shmmax"
> +#define PATH_KERNEL_SHMMNI "/proc/sys/kernel/shmmni"
> +#define PATH_KERNEL_SHMALL "/proc/sys/kernel/shmall"
> +#define PATH_KERNEL_SHM_NEXT_ID "/proc/sys/kernel/shm_next_id"
> +#define PATH_KERNEL_MSGMNI "/proc/sys/kernel/msgmni"
> +#define PATH_KERNEL_MSG_NEXT_ID "/proc/sys/kernel/msg_next_id"
> +#define PATH_KERNEL_SEM "/proc/sys/kernel/sem"
> +#define PATH_KERNEL_CORE_PATTERN "/proc/sys/kernel/core_pattern"
> +#define PATH_KERNEL_CAP_LAST_CAP "/proc/sys/kernel/cap_last_cap"
> +#define PATH_KERNEL_NUMA_BALANCING "/proc/sys/kernel/numa_balancing"
> +#define PATH_KERNEL_IO_URING_DISABLED "/proc/sys/kernel/io_uring_disabled"
> +#define PATH_KERNEL_OVERFLOWUID "/proc/sys/kernel/overflowuid"
> +#define PATH_KERNEL_OVERFLOWGID "/proc/sys/kernel/overflowgid"
> +#define PATH_KERNEL_PERF_EVENT_PARANOID "/proc/sys/kernel/perf_event_paranoid"
> +#define PATH_KERNEL_PERF_EVENT_MLOCK_KB "/proc/sys/kernel/perf_event_mlock_kb"
> +#define PATH_KERNEL_PERF_EVENT_MAX_SAMPLE_RATE "/proc/sys/kernel/perf_event_max_sample_rate"
> +#define PATH_KERNEL_SCHED_RT_PERIOD_US "/proc/sys/kernel/sched_rt_period_us"
> +#define PATH_KERNEL_SCHED_RT_RUNTIME_US "/proc/sys/kernel/sched_rt_runtime_us"
> +#define PATH_KERNEL_SCHED_RR_TIMESLICE_MS "/proc/sys/kernel/sched_rr_timeslice_ms"
> +#define PATH_KERNEL_UNPRIVILEGED_USERNS_CLONE "/proc/sys/kernel/unprivileged_userns_clone"
And, we could shorten those with PATH_KERN_* if people thinks
the marco string is too long.
--
Regards,
Li Wang
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2026-05-21 3:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-21 3:27 [LTP] [PATCH v4 1/2] lib: Introduce tst_path_defs.h to consolidate system paths Li Wang
2026-05-21 3:27 ` [LTP] [PATCH v4 2/2] metaparse: Explicitly parse essential headers for macros Li Wang
2026-06-03 9:18 ` Cyril Hrubis
2026-05-21 3:46 ` Li Wang [this message]
2026-05-21 3:46 ` [LTP] lib: Introduce tst_path_defs.h to consolidate system paths linuxtestproject.agent
2026-06-02 16:21 ` [LTP] [PATCH v4 1/2] " Andrea Cervesato via ltp
2026-06-03 9:19 ` Cyril Hrubis
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=ag6AB0v9am5pNoLQ@linux.dev \
--to=li.wang@linux.dev \
--cc=ltp@lists.linux.it \
/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