- Am 5. Sep 2019 um 7:25 schrieb Chris Johns chr...@rtems.org:
> On 5/9/19 2:25 pm, Sebastian Huber wrote:
>> - Am 4. Sep 2019 um 23:41 schrieb Chris Johns chr...@rtems.org:
>>
>>> On 5/9/19 2:09 am, Sebastian Huber wrote:
Hello,
I would like to wrap calls to interrupt hand
On 5/9/19 2:42 pm, Sebastian Huber wrote:
> - Am 5. Sep 2019 um 0:28 schrieb Chris Johns chr...@rtems.org:
>
>> On 4/9/19 9:46 pm, Sebastian Huber wrote:
>>> On 04/09/2019 08:06, Chris Johns wrote:
> +void LTTNGClient::WriteIRQHandlerExit(PerCPUContext* pcpu, const
> ClientItem&
>
Hello Ricardo,
- Am 4. Sep 2019 um 15:52 schrieb Ricardo Gomes (1161078)
1161...@isep.ipp.pt:
> Greetings,
>
> During the last six months, I have been studying RTEMS as part of my final
> project to complete my degree, more specifically analysing the MrsP protocol
> in
> order to perform a
On 5/9/19 2:25 pm, Sebastian Huber wrote:
> - Am 4. Sep 2019 um 23:41 schrieb Chris Johns chr...@rtems.org:
>
>> On 5/9/19 2:09 am, Sebastian Huber wrote:
>>> Hello,
>>>
>>> I would like to wrap calls to interrupt handlers which use the generic
>>> interrupt
>>> framework () to get RTEMS_RECO
- Am 5. Sep 2019 um 0:28 schrieb Chris Johns chr...@rtems.org:
> On 4/9/19 9:46 pm, Sebastian Huber wrote:
>> On 04/09/2019 08:06, Chris Johns wrote:
+void LTTNGClient::WriteIRQHandlerExit(PerCPUContext* pcpu, const
ClientItem&
item) {
+ pcpu->content_size += kEventIRQHan
- Am 4. Sep 2019 um 23:41 schrieb Chris Johns chr...@rtems.org:
> On 5/9/19 2:09 am, Sebastian Huber wrote:
>> Hello,
>>
>> I would like to wrap calls to interrupt handlers which use the generic
>> interrupt
>> framework () to get RTEMS_RECORD_INTERRUPT_ENTRY and
>> RTEMS_RECORD_INTERRUPT_EX
On 4/9/19 9:46 pm, Sebastian Huber wrote:
> On 04/09/2019 08:06, Chris Johns wrote:
>>> +void LTTNGClient::WriteIRQHandlerExit(PerCPUContext* pcpu, const
>>> ClientItem&
>>> item) {
>>> + pcpu->content_size += kEventIRQHandlerExitBits;
>>> + pcpu->packet_size += kEventIRQHandlerExitBits;
>>> +
>
On 5/9/19 2:09 am, Sebastian Huber wrote:
> Hello,
>
> I would like to wrap calls to interrupt handlers which use the generic
> interrupt framework () to get
> RTEMS_RECORD_INTERRUPT_ENTRY and RTEMS_RECORD_INTERRUPT_EXIT events. This
> cannot be done by the linker since the loop to call the han
Remove the unfinished sentence
"Since a barrier is, by definition, never immediately [...]"
and jump directly to
"The task may wait [forever or for a timeout]"
instead.
I cannot figure out what the unfinished sentence is supposed to be -
"released"? "passed"?
---
c-user/barrier_manager.rst | 7 ++
Remove various incorrect references to "lock" and "obtain" and to an
option set which is not part of the barrier interface.
It looks like the barrier documentation was started based on a copy of
the semaphore documentation and these things are surviving remnants.
Also remove an unfinished sentenc
The School of Computer Science and Statistics in Trinity College Dublin is
seeking a post-doctoral Research Fellow in the field of formal software
verification, for a duration of 15-18 months, to start as soon as possible.
Salary range €40k-€51.5k p.a., depending on experience and precise duration.
> Hello Chris,
>
> I would like to check in the latest documentation patch from Ravindra as
> is and then work on top of it. Otherwise his work is not included in the
> project history
>
I have already sent the v5 of LTTng sched_switch documentation patch:
https://lists.rtems.org/pipermail/devel/
Hello,
I would like to wrap calls to interrupt handlers which use the generic
interrupt framework () to get
RTEMS_RECORD_INTERRUPT_ENTRY and RTEMS_RECORD_INTERRUPT_EXIT events. This
cannot be done by the linker since the loop to call the handlers is inlined due
to performance reasons. I would
Greetings,
During the last six months, I have been studying RTEMS as part of my final
project to complete my degree, more specifically analysing the MrsP protocol in
order to perform an evaluation of its implementation on RTEMS.
In order to accomplish this analysis, I developed a set of samples
On 04/09/2019 08:06, Chris Johns wrote:
+void LTTNGClient::WriteIRQHandlerExit(PerCPUContext* pcpu, const ClientItem&
item) {
+ pcpu->content_size += kEventIRQHandlerExitBits;
+ pcpu->packet_size += kEventIRQHandlerExitBits;
+
+ EventIRQHandlerExit& ih = pcpu->irq_handler_exit;
+ ih.header.n
Hello Chris,
I would like to check in the latest documentation patch from Ravindra as
is and then work on top of it. Otherwise his work is not included in the
project history.
--
Sebastian Huber, embedded brains GmbH
Address : Dornierstr. 4, D-82178 Puchheim, Germany
Phone : +49 89 189 47
On 4/9/19 5:37 pm, Sebastian Huber wrote:
> On 04/09/2019 08:44, Chris Johns wrote:
>> On 4/9/19 4:27 pm, Sebastian Huber wrote:
>>> On 04/09/2019 08:06, Chris Johns wrote:
> +}
> +
> void LTTNGClient::AddThreadName(PerCPUContext* pcpu, const ClientItem&
> item) {
> if
On 04/09/2019 08:44, Chris Johns wrote:
On 4/9/19 4:27 pm, Sebastian Huber wrote:
On 04/09/2019 08:06, Chris Johns wrote:
+}
+
void LTTNGClient::AddThreadName(PerCPUContext* pcpu, const ClientItem& item)
{
if (pcpu->thread_name_index >= THREAD_NAME_SIZE) {
return;
@@ -286,6 +339
18 matches
Mail list logo
