Hello, Waiman. On Wed, Oct 18, 2023 at 02:24:00PM -0400, Waiman Long wrote: > If you mean saving the exclusion cpumask no matter who the caller is, we can > add another exclusion cpumask to save it and expose it to sysfs. This should > be done in the first workqueue patch, not as part of this patch. I expose > this isolated cpumask for testing purpose to be checked by the > test_cpuset_prs.sh script for correctness. As said, I can expose it without > cgroup_debug if you think the information is useful in general. I don't really care where the cpumask is in the source tree. I just want all the workqueue cpumasks presented to the userspace in a single place. Also, I think it makes sense to publish it to userspace in an easily accessible manner as what the eventual configuration ends up being can be confusing and the effect it has on the system subtle. Thanks. -- tejun
