Gilles Chanteperdrix wrote:
> Jan Kiszka wrote:
>> Gilles Chanteperdrix wrote:
>>> decision (we could store the first pending thread priority in a
>>> user/kernel shared area, with the complication that we would need
>>> updating this priority if it ever changes, but to get the priority of
>>> the
Jan Kiszka wrote:
> Gilles Chanteperdrix wrote:
>> decision (we could store the first pending thread priority in a
>> user/kernel shared area, with the complication that we would need
>> updating this priority if it ever changes, but to get the priority of
>> the current thread, we also need a sysc
Gilles Chanteperdrix wrote:
> Jan Kiszka wrote:
>> Gilles Chanteperdrix wrote:
>>> Gilles Chanteperdrix wrote:
Jan Kiszka wrote:
> Hi Gilles,
>
> do you - or anyone else - happen to have some patches under preparation
> to extend also the native skin with the newly added CONFIG
Jan Kiszka wrote:
> Gilles Chanteperdrix wrote:
>> Gilles Chanteperdrix wrote:
>>> Jan Kiszka wrote:
Hi Gilles,
do you - or anyone else - happen to have some patches under preparation
to extend also the native skin with the newly added CONFIG_XENO_FASTSEM
support? Just to a
Hi Gilles,
do you - or anyone else - happen to have some patches under preparation
to extend also the native skin with the newly added CONFIG_XENO_FASTSEM
support? Just to avoid duplicate work (we are about to work on this).
Jan
signature.asc
Description: OpenPGP digital signature
Gilles Chanteperdrix wrote:
> Jan Kiszka wrote:
>> Hi Gilles,
>>
>> do you - or anyone else - happen to have some patches under preparation
>> to extend also the native skin with the newly added CONFIG_XENO_FASTSEM
>> support? Just to avoid duplicate work (we are about to work on this).
>
> Not ye
Jan Kiszka wrote:
> Hi Gilles,
>
> do you - or anyone else - happen to have some patches under preparation
> to extend also the native skin with the newly added CONFIG_XENO_FASTSEM
> support? Just to avoid duplicate work (we are about to work on this).
Not yet. But the fastsem work is largely unf
