On 2013-01-06 16:26, Gilles Chanteperdrix wrote:
> On 01/06/2013 04:19 PM, Jan Kiszka wrote:
>
>> On 2013-01-06 16:15, Gilles Chanteperdrix wrote:
>>> On 01/06/2013 04:11 PM, Jan Kiszka wrote:
>>>
On 2013-01-06 16:09, Gilles Chanteperdrix wrote:
>> If you prefer to skip the warning in ipi
On 01/06/2013 04:19 PM, Jan Kiszka wrote:
> On 2013-01-06 16:15, Gilles Chanteperdrix wrote:
>> On 01/06/2013 04:11 PM, Jan Kiszka wrote:
>>
>>> On 2013-01-06 16:09, Gilles Chanteperdrix wrote:
> If you prefer to skip the warning in ipipe, then I will send a
> corresponding patch. The lock
On 2013-01-06 16:15, Gilles Chanteperdrix wrote:
> On 01/06/2013 04:11 PM, Jan Kiszka wrote:
>
>> On 2013-01-06 16:09, Gilles Chanteperdrix wrote:
If you prefer to skip the warning in ipipe, then I will send a
corresponding patch. The lock conversion is still necessary for forge,
th
On 01/06/2013 04:11 PM, Jan Kiszka wrote:
> On 2013-01-06 16:09, Gilles Chanteperdrix wrote:
>>> If you prefer to skip the warning in ipipe, then I will send a
>>> corresponding patch. The lock conversion is still necessary for forge,
>>> though.
>>
>>
>> There are other ways around, ipipe_virtual
On 2013-01-06 16:09, Gilles Chanteperdrix wrote:
>> If you prefer to skip the warning in ipipe, then I will send a
>> corresponding patch. The lock conversion is still necessary for forge,
>> though.
>
>
> There are other ways around, ipipe_virtualize_irq is already a wrapper
> used only by 2.6,
On 01/06/2013 03:46 PM, Jan Kiszka wrote:
> On 2013-01-06 15:26, Gilles Chanteperdrix wrote:
>> On 01/06/2013 03:20 PM, Jan Kiszka wrote:
>>
>>> On 2013-01-06 14:55, Gilles Chanteperdrix wrote:
On 01/06/2013 12:03 PM, Jan Kiszka wrote:
> On 2013-01-06 11:55, Jan Kiszka wrote:
>>
On 2013-01-06 15:26, Gilles Chanteperdrix wrote:
> On 01/06/2013 03:20 PM, Jan Kiszka wrote:
>
>> On 2013-01-06 14:55, Gilles Chanteperdrix wrote:
>>> On 01/06/2013 12:03 PM, Jan Kiszka wrote:
>>>
On 2013-01-06 11:55, Jan Kiszka wrote:
> On 2013-01-06 11:14, Philippe Gerum wrote:
>> O
On 01/06/2013 03:26 PM, Gilles Chanteperdrix wrote:
> On 01/06/2013 03:20 PM, Jan Kiszka wrote:
>
>> On 2013-01-06 14:55, Gilles Chanteperdrix wrote:
>>> On 01/06/2013 12:03 PM, Jan Kiszka wrote:
>>>
On 2013-01-06 11:55, Jan Kiszka wrote:
> On 2013-01-06 11:14, Philippe Gerum wrote:
On 01/06/2013 03:20 PM, Jan Kiszka wrote:
> On 2013-01-06 14:55, Gilles Chanteperdrix wrote:
>> On 01/06/2013 12:03 PM, Jan Kiszka wrote:
>>
>>> On 2013-01-06 11:55, Jan Kiszka wrote:
On 2013-01-06 11:14, Philippe Gerum wrote:
> On 01/03/2013 03:09 PM, Jan Kiszka wrote:
>
>> +stat
On 2013-01-06 14:55, Gilles Chanteperdrix wrote:
> On 01/06/2013 12:03 PM, Jan Kiszka wrote:
>
>> On 2013-01-06 11:55, Jan Kiszka wrote:
>>> On 2013-01-06 11:14, Philippe Gerum wrote:
On 01/03/2013 03:09 PM, Jan Kiszka wrote:
> +static struct xnvfile_lock_ops vfile_stat_lockops = {
>
On 01/06/2013 12:03 PM, Jan Kiszka wrote:
> On 2013-01-06 11:55, Jan Kiszka wrote:
>> On 2013-01-06 11:14, Philippe Gerum wrote:
>>> On 01/03/2013 03:09 PM, Jan Kiszka wrote:
>>>
+static struct xnvfile_lock_ops vfile_stat_lockops = {
+ .get = xnintr_get_query_lock,
+ .put = xnintr
On 2013-01-06 11:55, Jan Kiszka wrote:
> On 2013-01-06 11:14, Philippe Gerum wrote:
>> On 01/03/2013 03:09 PM, Jan Kiszka wrote:
>>
>>> +static struct xnvfile_lock_ops vfile_stat_lockops = {
>>> + .get = xnintr_get_query_lock,
>>> + .put = xnintr_put_query_lock,
>>> +};
>>> +
>>> static struct
On 2013-01-06 11:14, Philippe Gerum wrote:
> On 01/03/2013 03:09 PM, Jan Kiszka wrote:
>
>> +static struct xnvfile_lock_ops vfile_stat_lockops = {
>> +.get = xnintr_get_query_lock,
>> +.put = xnintr_put_query_lock,
>> +};
>> +
>> static struct xnvfile_snapshot stat_vfile = {
>> .priv
On 01/03/2013 03:09 PM, Jan Kiszka wrote:
> +static struct xnvfile_lock_ops vfile_stat_lockops = {
> + .get = xnintr_get_query_lock,
> + .put = xnintr_put_query_lock,
> +};
> +
> static struct xnvfile_snapshot stat_vfile = {
> .privsz = sizeof(struct vfile_stat_priv),
> .datas
Conceptually, all users of this lock are supposed to run over Linux
context already. Moreover, latest I-pipe patches complain that
ipipe_virtualize_irq is called with the Xenomai domain stalled which
invalidates that useful internal bug check.
So rework the locking for dumping scheduling statistic
15 matches
Mail list logo