On Tue, Sep 26, 2023, at 00:38, Zhangjin Wu wrote: > When CONFIG_TRIM_UNUSED_SYSCALLS is enabled, get used syscalls from > CONFIG_USED_SYSCALLS. CONFIG_USED_SYSCALLS may be a list of used > syscalls or a file to store such a list. > > If CONFIG_USED_SYSCALLS is configured as a list of the used syscalls, > directly record them in a used_syscalls variable, if it is a file to > store the list, record the file name to the used_syscalls_file variable > and put its content to the used_syscalls variable. > > Signed-off-by: Zhangjin Wu <falcon@xxxxxxxxxxx> I like the idea of configuring the set of syscalls more, but we should probably discuss the implementation of this here. You introduce two new ways of doing this, on top of the existing coarse-grained method (per syscall class Kconfig symbols). Both methods seem a little awkward to me, but are doable in principle if we can't come up with a better way. However, I'd much prefer to not add both the Kconfig symbol and the extra file here, since at least one of them is redundant. Do you have automatic tooling to generate these lists from a profile, or do you require manually writing them? Do you have an example list? Arnd