<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>On 14/02/2020 16:31, Joel Sherrill wrote:<br>
</p>
<blockquote type="cite"
cite="mid:CAF9ehCXjrkQccBuiOEe+K-rZk8n_UGA8LQtqgi1m72QQip8FXA@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr">
<div dir="ltr"><br>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Fri, Feb 14, 2020 at 9:04
AM Sebastian Huber <<a
href="mailto:sebastian.huber@embedded-brains.de"
moz-do-not-send="true">sebastian.huber@embedded-brains.de</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex">On 14/02/2020 15:42, Joel
Sherrill wrote:<br>
<br>
> I guess it is time to kill it.<br>
<br>
I already have a smoking gun in my hands. I think it would
be possible <br>
to make it working again with some effort. However, it is
quite easy to <br>
add scheduler test scenarios in the RTEMS test suite itself,
for example:<br>
<br>
<a
href="https://git.rtems.org/rtems/tree/testsuites/smptests/smpschededf02/init.c#n108"
rel="noreferrer" target="_blank" moz-do-not-send="true">https://git.rtems.org/rtems/tree/testsuites/smptests/smpschededf02/init.c#n108</a></blockquote>
<div><br>
</div>
<div>The simulator allowed you to instance any number of cores
in a system and</div>
<div>reduce the testing to just the scheduling events -- no
interrupts, no hardware,</div>
<div>no device drivers, and native debug environment.</div>
<div><br>
</div>
<div>You can easily construct a system with 2, 4, 8, 32, or 64
nodes with it. It is</div>
<div>more flexible and really much simpler to debug with when
developing a</div>
<div>scheduler.</div>
</div>
</div>
</blockquote>
Ok, this is difficult with real hardware. If there is a need, we can
make it work again.<br>
</body>
</html>