- Ursprüngliche Mail -
> Von: "Philippe Gerum"
>> So the tests have assumptions about the scheduling order of threads?
>> I always thought even with a single CPU such assumptions can break.
>
> Not if the scheduling core Xenomai provides does its job properly.
I see.
Thanks,
//richard
Richard Weinberger writes:
> Philippe,
>
> - Ursprüngliche Mail -
>> Von: "Philippe Gerum"
>>> Why is this "special" cpu-affinity necessary? What would happen if we
>>> remove that? Asking because I want to make sure that we do not miss any
>>> concurrency problems by adding this
Philippe,
- Ursprüngliche Mail -
> Von: "Philippe Gerum"
>> Why is this "special" cpu-affinity necessary? What would happen if we
>> remove that? Asking because I want to make sure that we do not miss any
>> concurrency problems by adding this constraint.
>>
>
> The reason to pin the
"Bezdeka, Florian via Xenomai" writes:
> Hi Richard,
>
> On Fri, 2022-04-08 at 10:03 +0200, Richard Weinberger via Xenomai
> wrote:
>> +static int __run_extprog(struct smokey_test *t, int argc, char *const
>> argv[])
>> +{
>> +int ret;
>> +char *tst_path;
>> +
>> +ret =
Florian,
- Ursprüngliche Mail -
> Why is this "special" cpu-affinity necessary? What would happen if we
> remove that? Asking because I want to make sure that we do not miss any
> concurrency problems by adding this constraint.
I don't know. I copied it as-is from the old Makefile.
Hi Richard,
On Fri, 2022-04-08 at 10:03 +0200, Richard Weinberger via Xenomai
wrote:
> +static int __run_extprog(struct smokey_test *t, int argc, char *const argv[])
> +{
> + int ret;
> + char *tst_path;
> +
> + ret = asprintf(_path, "%s/%s --cpu-affinity=0", mydir, t->name);
> +
In their current shape, every alchemy test has to be a single
program and does not use the smokey test framework.
alchemytest_driver uses smokey and runs each test as new process.
Signed-off-by: Richard Weinberger
---
testsuite/alchemytests/Makefile.am | 11 +++
