[LTP] [PATCH] doc: add tests catalog page

[Petr Vorel]

> Hi!
> > I also have a question: what test configuration keys should be seen in 
> > the documentation tests list?
> > I.e. needs_forks, needs_kconfigs, etc.

> That's a good question. We should keep the information the tester is
> interested in, however we should add too much either.

> I guess that we want group the data somewhat like:

>  - options (because command line options may be useful there)

>  - min_kver, needs_kconfigs, min_cpus, needs_drivers, needs_cmds...
>    (because it may describe why tests are skipped)

>  - needs_cgroup_ctrls + cgroup knobs (for tests that use cgroups)
Also .needs_cgroup_ver, .needs_cgroup_nsdelegate

>  - all_filesystems, skip_filesystems, filesystems

>  - timeout, runtime         (here as well, run for longer)

>  - needs_root      maybe?
>  - needs_device    maybe?
IMHO both can be interesting - you can list tests you loose if you don't use
root or you don't have kernel with loop device configured.

Also there are more: .caps, .hugepages, .needs_hugetlbfs, .min_mem_avail,
.min_swap_avail, .dev_min_size, .needs_abi_bits, .needs_overlay (at least).

Why not to show all the info like it was previously? We never know what the
reader will be interested in.

If we are really not interested at all, I would just avoid few LTP true
internals, e.g.: .needs_checkpoints, .forks_child, .child_needs_reinit.

Kind regards,
Petr