This method adds a "root" hierarchy level, if the system topology doesnt have one. Necessary for iterating through the whole topology.

now chooses the right starting core for the next thread

…r fixes

…function

…blings mapping added

…edits

Also turn value checks into asserts,
as this is an internal method.

This fixes complaints from Ruff.

This helps us to be more convinced that the data structures
created by the unit tests are the same as in real use.

This is redundant because hierarchy_levels[0] is the same
and there is only effort to keep the two in sync.

- First create the final list of hierarchy levels, then create the
  VirtualCore objects.
  Previously one level was potentially created afterwards and needed
  adjustments to the VirtualCore objects.

- Always insert root level and rely on the filter that we use anyway
  to remove it if necessary. This is the same strategy that we use for
  the siblings_of_core level and thus easier to follow.

All the information in these instances is also present in
hierarchy_levels, it is just a more convenient way to access it.
Creating it locally makes it easier to write tests.

Because the tests were changed significantly together with the
implementation of the core allocation in this branch,
it is hard to see whether the tests still test the same things.
But we want regression tests that ensure that the new allocation
behaves in the same way.
So we restore the old tests and keep the new tests in a separate file
until we are sure that there are no regressions,
and then we can unify the test suites.

For now the old tests fail due to API changes,
this will be adapted next.

This makes most of the tests succeed, but some still fail.
Potentially some further adjustments are needed,
but there is also one regression
(https://github.com/sosy-lab/benchexec/pull/892/files#r1229136970).

The new get_cpu_distribution method has no information about
partial physical cores anymore,
this is checked outside of it.

It is better to have CI green to be able to notice further regressions.

Also add unit tests for this function.

Also do not use "raise Exception", use assert to encode coding
assumptions.

Only the standard format is lazy.

- Function name starting with "read" to indicate it reads from kernel.
- Parameters in better order.
- Identifier naming according to Python standard.
- Actually use generic identifiers in a generic function
  and not names that are specific to one use case.
- Also replace all trivial callers with a single function.

- Crucial constants should be present only once, documented,
  and defined in a central place.
- Reading from the system and logic should be separate
  such that the latter is testable.
- For reading from the system we can use an existing helper method.
- Add tests.

Uses of plain dicts may catch errors in callers earlier.
Furthermore, some of the functions even returned a defaultdict
in some cases and a plain dict in other cases.
The return type should be consistent.

With dict.setdefault() the use of a plain dict
is almost as convenient as a defaultdict.

…lity

It is not really necessary.

We always want the user to allow us to use entire physical cores.
This check was broken, because forbidden sibling cores
were already removed from the data structure before the check.
Furthermore, cores forbidden via cgroups and via the
--allowedCores parameter were treated somehow differently,
but the effect should be exactly the same.

So far we read the information about the hyperthreading hierarchy level
differently from the other levels.
This made the code more difficult to understand,
and the way how the ids in the hierarchy_levels[0] dict were chosen
differed from the other levels.
But we can also read this information in the same way as for the other
levels, so let's do this.

We still also need to use the previous way of reading all siblings from
a given list of cores, but we can also simplify that
and the separation of concerns still provides
an understandability benefit.

The allocation algorithm already supports an arbitrary number of levels,
so we can future proof the allocation
and read all information about cache levels
that the kernel provides.

We can also use the assumption that caches are named the same
across all cores, and read the cache names only once
instead of separately for every core.

This method actually has nothing to do with "sub" units (children),
it just takes a set of cores and a level and groups the cores
as appropriate for the level.
So the names should reflect that.

To allow easier generation of new tests (where we ideally can automatically generate tests for a large number
of (also weird) CPU configurations), it's desireable to be able to specify arbitrary layers more or less directly, without
having to create new test classes.

The final goal is to be able to generate machine configurations given a single argument (or two arguments: layer configuration as a list
and total core count), so we can utilize pytest to write easily maintainable test cases.

As the new method already keeps the layers in the correct order and doesn't create duplicate layers,
we can remove those parts from the code

After showing that the new layer generation code is equivalent to the existing one, we can
remove the old code with the hardcoded layers and use the new code.