On 23/07/2020 08:12, Richi Dubey wrote:
I am still having a hard time understanding this. What do you mean by
no code which blocks? Does the thread which executes our task (Say a
function Loop with 30k loops) block? What does block mean here?
Block means here that the thread calls _Scheduler_
Thank you for the clarification.
I am still having a hard time understanding this. What do you mean by no
code which blocks? Does the thread which executes our task (Say a
function Loop with 30k loops) block? What does block mean here?
On Wed, Jul 22, 2020 at 7:46 PM Sebastian Huber <
sebastian.h
Hello，
I have a TI bsp which uses a ARM cortex A72 process. It has 4 cores and MMU
enabled.
So does rtems support SMP and MMU in such a platform?
After searching the mail and source code, I only find a cortex A53 platform.
small...@aliyun.com
___
deve
On 23/07/2020 00:25, Chris Johns wrote:
On 22/7/20 7:16 pm, Sebastian Huber wrote:
On 22/07/2020 07:04, Chris Johns wrote:
On 22/7/20 1:04 am, Sebastian Huber wrote:
b) As previously discussed there are a few more states a test result can be
other than pass and fail and I thikn the wording her
Hello,
I see the user commands in libbsd use a generated header file created by
`userspace-header-gen.py` however it does not run on my host because I do not
have an `elftools` package installed. I cannot find any details on what needs to
be installed so this tool can be used. I get the impression
On 22/7/20 6:02 pm, Sebastian Huber wrote:
> Rename this header file to later move to . The main
> feature provided by is the output of standard test
> information which is consumed by the RTEMS Tester.
Looks good. Thanks for the change.
Chris
___
de
On 22/7/20 7:16 pm, Sebastian Huber wrote:
> On 22/07/2020 07:04, Chris Johns wrote:
>> On 22/7/20 1:04 am, Sebastian Huber wrote:
>> b) As previously discussed there are a few more states a test result can be
>> other than pass and fail and I thikn the wording here may need tightening. I
>> am
>>
On Wed, Jul 22, 2020 at 2:26 PM Christian Mauderer
wrote:
> Ping again.
>
> It's clearly not BSP specific. So I would like to get an approval for
> that before pushing it anywhere.
>
CentOS 7's gcc appears to have the option and I would assume this is the
oldest distribution anyone is using.
$
Ping again.
It's clearly not BSP specific. So I would like to get an approval for
that before pushing it anywhere.
On 15/06/2020 17:36, Christian Mauderer wrote:
> Ping.
>
> Currently shouldn't be a matter for much hosts (less than 20 including
> FreeBSD, Fedora, Arch, openSUSE according to dist
On 22/07/2020 15:36, Richi Dubey wrote:
Threads that get created automatically when a CPU starts have their
scheduler nodes with node->idle set to the thread itself, while the
nodes that are created due to a task being created have NULL in their
node->idle (If not using helper function atm).
Hi,
Please clear a doubt of mine.
Threads that get created automatically when a CPU starts have their
scheduler nodes with node->idle set to the thread itself, while the nodes
that are created due to a task being created have NULL in their node->idle
(If not using helper function atm). Am I righ
Thank you for the clarification.
On Sat, Jul 18, 2020 at 9:06 PM Gedare Bloom wrote:
> On Fri, Jul 17, 2020 at 2:22 AM Richi Dubey wrote:
> >>
> >>
> >> > Scheduler_Node *nodes;
> >> > } Thread_Scheduler_control;
> >> >
> >> > Why do we have a Scheduler_Node *nodes? What does it indicate? Sin
Make sure that the esp is restored before the eflags register.
When the init task is initially restored, system interrupts are activated when
the
eflags register is loaded.
If the esp register still points to an address in the interrupt stack
area (from early system initlization) the ISR might ov
Ran into this problem sometimes when testing examples of rtems-libbsd,
but it should be general.
I opened tickets https://devel.rtems.org/ticket/4030 and
https://devel.rtems.org/ticket/4031 correspondintly.
Cheers,
Jan
Jan Sommer (1):
i386: Fix possible race condition on first context rest
Document the dynamic text fixtures, utility functions, and the interrupt
test support. Reorder some sections and reword some paragraphs based on
review comments.
Update #3199.
---
v2:
Address review comments. I updated:
https://ftp.rtems.org/pub/rtems/people/sebh/eng2.pdf
eng/index.rst
On 22/07/2020 07:04, Chris Johns wrote:
On 22/7/20 1:04 am, Sebastian Huber wrote:
This patch set adds a couple of improvements to the test framework:
* The header file changes from to .
* Support for a stack of test fixtures. This helps to write test
building blocks.
* The test check m
This helps. Thanks a lot.
On Tue, Jul 21, 2020 at 6:55 PM Sebastian Huber <
sebastian.hu...@embedded-brains.de> wrote:
> On 21/07/2020 14:36, Richi Dubey wrote:
>
> > Could you please explain what _User_extensions_Thread_start does? It's
> > hard to understand it all by myself since it has a lot
17 matches
Mail list logo
