Re: [Xenomai-help] Analogy cmd_write example explanation

[Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>]

Jan Kiszka wrote:
> Gilles Chanteperdrix wrote:
>> ...
>> Argh.... The switchtest driver is relying on __xn_exec_current to have
>> context switches occur precisely in the mode we want. __xn_exec_adaptive
>> introduce more context switches around which we can not place separate
>> checks for fpu context, so, in short, breaks it badly. Fixing this
>> requires turning the switchtest driver into a skin with its own syscalls.
> 
> Independent of how switchtest (or RTDM) is fixed again: Do you already
> have a patch like this in your queue?
> 
> diff --git a/ksrc/drivers/testing/switchtest.c b/ksrc/drivers/testing/switchtest.c
> index 057094b..09cd0ec 100644
> --- a/ksrc/drivers/testing/switchtest.c
> +++ b/ksrc/drivers/testing/switchtest.c
> @@ -665,6 +665,9 @@ static int rtswitch_ioctl_rt(struct rtdm_dev_context *context,
>  	struct rttst_swtest_dir fromto;
>  
>  	switch (request) {
> +	case RTTST_RTIOC_SWTEST_SET_TASKS_COUNT:
> +	case RTTST_RTIOC_SWTEST_SET_CPU:
> +	case RTTST_RTIOC_SWTEST_SET_PAUSE:
>  	case RTTST_RTIOC_SWTEST_REGISTER_UTASK:
>  	case RTTST_RTIOC_SWTEST_CREATE_KTASK:
>  	case RTTST_RTIOC_SWTEST_GET_SWITCHES_COUNT:
> 
> I.e. add the missing reflections of NRT IOCTLs.

Yes, I had this fix in my tree. But switchtest is broken not only for
this reason. I am just waiting what will be decided with regard to the
two mode switches when calling an nrt ioctl from a shadowed thread
running in secondary mode, to implement a complete fix (most probably
rewriting it as a skin).

-- 
					    Gilles.