Timeline



10/28/21:

19:58 Changeset in rtems-tools [ba4648b] by Alex White <alex.white@…>
rtems-bsp-builder: Fix mail support This fixes a problem with mailer options support that occurred because check.py uses argparse.ArgumentParser? instead of tester.rt.options.
19:58 Changeset in rtems-tools [bdd785a]5 by Alex White <alex.white@…>
rtems-bsp-builder: Fix mail support This fixes a problem with mailer options support that occurred because check.py uses argparse.ArgumentParser? instead of tester.rt.options. Closes #4553
19:21 Changeset in rtems-central [a827b7c] by Sebastian Huber <sebastian.huber@…>
spec: Fix typo
18:57 Changeset in rtems-central [7bdca91] by Sebastian Huber <sebastian.huber@…>
modules: Update rtems
18:29 Ticket #4536 (acess JFFS2 sb->s_root) closed by Sebastian Huber
invalid: Replying to chenjin_zhong: > Replying to Sebastian Huber: > > Thanks for your interest in the RTEMS port of JFFS2. If you have questions, then you could also ask them on the devel@… mailing list. The RTEMS port of JFFS2 does not use a file system internal locking. There is a global lock for each JFFS2 instance: > > {{{#!c > > static void rtems_jffs2_do_lock(struct super_block *sb) > > { > > rtems_recursive_mutex_lock(&sb->s_mutex); > > } > > > > static void rtems_jffs2_do_unlock(struct super_block *sb) > > { > > rtems_recursive_mutex_unlock(&sb->s_mutex); > > } > > }}} > > Suppose that a GC thread or other thread/task calls jffs2_garbage_collect_pass, and then operates sb->s_root by jffs2_iget.meanwhile, the main task accesing sb->s_root. a global lock for each JFFS2 instance can't work. It is not a high performance approach, but it works. See testsuites/fstests/fsjffs2gc01/init.c.
18:26 Ticket #4538 (mutex is not initilaized in jffs2_read_inode) closed by Sebastian Huber
invalid: Replying to chenjin_zhong: > Replying to Sebastian Huber: > > Yes, the f->sem is an empty structure, it is not initialized, it is not used, locked or whatever in RTEMS. This is intentional and not a bug. I repeat: The RTEMS port of JFFS2 does not use a file system internal locking. There is a global lock for each JFFS2 instance. > > Thank you! I got it. but we Suppose that a GC thread or other thread/task and main task calls jffs2_do_readinode simultaneous. a global lock for each JFFS2 instance can't work. It is not a high performance approach, but it works. See testsuites/fstests/fsjffs2gc01/init.c.
18:17 Changeset in rtems-central [611b9a2] by Sebastian Huber <sebastian.huber@…>
modules: Update rtems
16:54 Changeset in rtems-tools [d1df4f6] by Ryan Long <ryan.long@…>
TraceConverter?.cc: Add catch for exception CID 1471639: Add catch for exception Closes #4501
15:07 Ticket #4538 (mutex is not initilaized in jffs2_read_inode) reopened by chenjin_zhong
14:53 Ticket #4536 (acess JFFS2 sb->s_root) reopened by chenjin_zhong
Replying to Sebastian Huber: > Thanks for your interest in the RTEMS port of JFFS2. If you have questions, then you could also ask them on the devel@… mailing list. The RTEMS port of JFFS2 does not use a file system internal locking. There is a global lock for each JFFS2 instance: > {{{#!c > static void rtems_jffs2_do_lock(struct super_block *sb) > { > rtems_recursive_mutex_lock(&sb->s_mutex); > } > > static void rtems_jffs2_do_unlock(struct super_block *sb) > { > rtems_recursive_mutex_unlock(&sb->s_mutex); > } > }}} Suppose that a GC thread or other thread/task calls jffs2_garbage_collect_pass, and then operates sb->s_root by jffs2_iget.meanwhile, the main task accesing sb->s_root. a global lock for each JFFS2 instance can't work.
14:45 Ticket #4537 (mutex is not initilaized in jffs2_new_inode) closed by Sebastian Huber
invalid: Yes, the f->sem is an empty structure, it is not initialized, it is not used, locked or whatever in RTEMS. This is intentional and not a bug. I repeat: The RTEMS port of JFFS2 does not use a file system internal locking. There is a global lock for each JFFS2 instance.
14:43 Ticket #4538 (mutex is not initilaized in jffs2_read_inode) closed by Sebastian Huber
invalid: Yes, the f->sem is an empty structure, it is not initialized, it is not used, locked or whatever in RTEMS. This is intentional and not a bug. I repeat: The RTEMS port of JFFS2 does not use a file system internal locking. There is a global lock for each JFFS2 instance.
14:42 Ticket #4537 (mutex is not initilaized in jffs2_new_inode) reopened by chenjin_zhong
14:40 Ticket #4538 (mutex is not initilaized in jffs2_read_inode) reopened by chenjin_zhong
Replying to Sebastian Huber: > Thanks for your interest in the RTEMS port of JFFS2. If you have questions, then you could also ask them on the devel@… mailing list. The RTEMS port of JFFS2 does not use a file system internal locking. There is a global lock for each JFFS2 instance: > {{{#!c > static void rtems_jffs2_do_lock(struct super_block *sb) > { > rtems_recursive_mutex_lock(&sb->s_mutex); > } > > static void rtems_jffs2_do_unlock(struct super_block *sb) > { > rtems_recursive_mutex_unlock(&sb->s_mutex); > } > }}} I have compared it with Linux JFFS2. The peice of source code in Linux is as follows,As shown in black-body section, the f->sem is not be initialized and locked in RTEMS. […]
14:09 Changeset in rtems-central [45237bf] by Sebastian Huber <sebastian.huber@…>
spec: Improve SMP-specific timecounter validation
12:28 Changeset in rtems-central [bcb0753] by Sebastian Huber <sebastian.huber@…>
spec: Specify NTP support
11:06 Changeset in rtems-central [da36db3] by Sebastian Huber <sebastian.huber@…>
spec: Specify _Timecounter_Tick_simple()
09:14 Changeset in rtems [5382f617]5 by Sebastian Huber <sebastian.huber@…>
score: Add _Timecounter_Set_NTP_update_second() Allow the installation of an NTP update second handler which may be used by an NTP service. Update #4549.
09:14 Changeset in rtems [ffb8833d] by Sebastian Huber <sebastian.huber@…>
score: Add _Timecounter_Set_NTP_update_second() Allow the installation of an NTP update second handler which may be used by an NTP service. Update #2348.
08:22 Changeset in rtems [34675587] by Sebastian Huber <sebastian.huber@…>
kern_tc.c: Scaling/large delta recalculation This change is a slight performance optimization for systems with a slow 64-bit division. The th->th_scale and th->th_large_delta values only depend on the timecounter frequency and the th->th_adjustment. The timecounter frequency of a timehand only changes when a new timecounter is activated for the timehand. The th->th_adjustment is only changed by the NTP second update. The NTP second update is not done for every call of tc_windup(). Move the code block to recalculate the scaling factor and the large delta of a timehand to the new helper function recalculate_scaling_factor_and_large_delta(). Call recalculate_scaling_factor_and_large_delta() when a new timecounter is activated and a NTP second update occurred. MFC after: 1 week
08:22 Changeset in rtems [4f13092]5 by Sebastian Huber <sebastian.huber@…>
kern_tc.c: Scaling/large delta recalculation This change is a slight performance optimization for systems with a slow 64-bit division. The th->th_scale and th->th_large_delta values only depend on the timecounter frequency and the th->th_adjustment. The timecounter frequency of a timehand only changes when a new timecounter is activated for the timehand. The th->th_adjustment is only changed by the NTP second update. The NTP second update is not done for every call of tc_windup(). Move the code block to recalculate the scaling factor and the large delta of a timehand to the new helper function recalculate_scaling_factor_and_large_delta(). Call recalculate_scaling_factor_and_large_delta() when a new timecounter is activated and a NTP second update occurred. MFC after: 1 week
05:20 Ticket #4538 (mutex is not initilaized in jffs2_read_inode) closed by Sebastian Huber
invalid: Thanks for your interest in the RTEMS port of JFFS2. If you have questions, then you could also ask them on the devel@… mailing list. The RTEMS port of JFFS2 does not use a file system internal locking. There is a global lock for each JFFS2 instance: […]
05:20 Ticket #4537 (mutex is not initilaized in jffs2_new_inode) closed by Sebastian Huber
invalid: Thanks for your interest in the RTEMS port of JFFS2. If you have questions, then you could also ask them on the devel@… mailing list. The RTEMS port of JFFS2 does not use a file system internal locking. There is a global lock for each JFFS2 instance: […]
05:19 Ticket #4536 (acess JFFS2 sb->s_root) closed by Sebastian Huber
invalid: Thanks for your interest in the RTEMS port of JFFS2. If you have questions, then you could also ask them on the devel@… mailing list. The RTEMS port of JFFS2 does not use a file system internal locking. There is a global lock for each JFFS2 instance: […]
05:19 Ticket #4535 (acess JFFS2 sb->s_root question) closed by Sebastian Huber
invalid: Thanks for your interest in the RTEMS port of JFFS2. If you have questions, then you could also ask them on the devel@… mailing list. The RTEMS port of JFFS2 does not use a file system internal locking. There is a global lock for each JFFS2 instance: […]

10/27/21:

15:13 Ticket #4538 (mutex is not initilaized in jffs2_read_inode) created by chenjin_zhong
HI, I have found when call jffs2_read_inode to read inode. the f->sem …
14:59 Ticket #4537 (mutex is not initilaized in jffs2_new_inode) created by chenjin_zhong
HI, I have found when call jffs2_new_inode to create inode. the f->sem …
14:47 Ticket #4536 (acess JFFS2 sb->s_root) created by chenjin_zhong
Hi, I have found when access global structure without mutex or …
14:34 Ticket #4535 (acess JFFS2 sb->s_root question) created by chenjin_zhong
Hi, I have found when access global structure without mutex or …
14:12 Changeset in rtems-central [94ed8b1] by Sebastian Huber <sebastian.huber@…>
spec: Fix sporadic test failure
10:59 Changeset in rtems [240a1f7] by Sebastian Huber <sebastian.huber@…>
score: Introduce CPU budget operations This patch set replaces the CPU budget algorithm enumeration with a set of CPU budget operations which implement a particular CPU budget algorithm. This helps to hide the CPU budget algorithm implementation details from the general thread handling. The CPU budget callouts are turned into CPU budget operations. This slightly reduces the size of the thread control block. All schedulers used the default scheduler tick implementation. The tick scheduler operation is removed and the CPU budget operations are directly used in _Watchdog_Tick() if the executing thread uses a CPU budget algorithm. This is performance improvement for all threads which do not use a CPU budget algorithm (default behaviour).
07:46 Changeset in rtems [75527ef3] by Sebastian Huber <sebastian.huber@…>
score: Optimize SMP EDF move to ready operation If a node is moved from the scheduled chain to the ready queue, then we know that it is the highest priority ready node. So, it can be prepended to the ready queue without doing any comparisons. Update #4531.
07:40 Ticket #4534 (SMP EDF scheduler violates priority group ordering) created by Sebastian Huber
The SMP EDF scheduler supports one-to-one and one-to-all thread to …
06:48 Changeset in rtems [b9990b8d] by Sebastian Huber <sebastian.huber@…>
score: Fix SMP EDF priority group ordering The SMP EDF scheduler supports one-to-one and one-to-all thread to processor affinities. The one-to-one thread to processor affinity introduces a constraint on the ordering of threads. The implementation uses one ready queue for threads which have a one-to-all affinity and one for each one-to-one affinity group. To order threads across the ready queues, a generation number is used. However, the approach to update the generation number each time a thread is inserted into a ready queue was wrong. The generation number needs to be updated only in the enqueue and enqueue scheduled operations where an insert priority is available. The scheduled chain needs to take the generation number into account. An example scenario which shows the bug is this. Let T be a high priority task affine to processor X. Let A be a lower priority task affine to processor X. Let B be a lower priority task with no affinity to a particular processor which executes on processor Y. Let B be in the same priority group than A and after A. Let T set the affinity to all processors. Now A (higher priority relative to B) should execute on X and T (high priority) should execute on Y. Close #4534.
06:35 Changeset in rtems [6d20f0c5] by Sebastian Huber <sebastian.huber@…>
score: Add node to insert to Chain_Node_order This allows to use additional members of the nodes for comparision. Update #4534.

10/26/21:

14:35 Changeset in rtems-central [940bfeb0] by Sebastian Huber <sebastian.huber@…>
spec: Update documentation

10/25/21:

17:19 Changeset in rtems [a857a22] by Kinsey Moore <kinsey.moore@…>
cpukit/aarch64: Add libdebugger support This adds support for libdebugger under AArch64 using software breakpoints and the single-step execution mode present in all AArch64 CPUs.
16:03 Changeset in rtems [75c133bd] by Sebastian Huber <sebastian.huber@…>
sptests/sp69: Remove test case This error condition no longer exists. Update #4528.
14:56 Changeset in rtems [750bde8] by Kinsey Moore <kinsey.moore@…>
bsps/aarch64: Mask debug events from startup Debug events should be masked at least until after the first context switch and should usually be masked until a debugger is attached for application debugging.
14:53 Changeset in rtems [2d27725] by Kinsey Moore <kinsey.moore@…>
bsps/aarch64: Set interrupt level correctly The existing code is functional but inccorrect and blindly modifies the other masking bits. It is important to preserve those other bits since they control masking of important system events.
14:50 Changeset in rtems [55a93ae] by Kinsey Moore <kinsey.moore@…>
bsps/aarch64: Add missing MMU map recursion check Certain input parameters for MMU mapping operations could cause an infinite recursion if block end boundaries didn't align to 4k. This ensures that recursion descent does not exceed 2 levels and instead rounds up to the nearest 4k block if necessary.
14:47 Changeset in rtems [2055e42] by Kinsey Moore <kinsey.moore@…>
aarch64: Break out MMU definitions This moves the AArch64 MMU memory type definitions into cpukit for use by libdebugger since remapping of memory is required to insert software breakpoints.
06:15 Changeset in rtems [24922d0] by Sebastian Huber <sebastian.huber@…>
rtems: rtems_rate_monotonic_get_status() Mention that resetting the processor usage time of tasks has no impact on the period status and statistics. Remove no longer relevant RTEMS_NOT_DEFINED error status. Update #4528.
06:10 Ticket #4528 (rate monotonic: reset of CPU usage time not always detected) closed by Sebastian Huber <sebastian.huber@…>
fixed: In feb4687/rtems-docs: […]
06:09 Changeset in rtems-docs [feb4687] by Sebastian Huber <sebastian.huber@…>
c-user: rtems_rate_monotonic_get_status() Mention that resetting the processor usage time of tasks has no impact on the period status and statistics. Remove no longer relevant RTEMS_NOT_DEFINED error status. Close #4528.
02:55 Ticket #4533 (libdebugger should only build for archs with a backend) closed by Chris Johns <chrisj@…>
fixed: In 3f0ad2b/rtems: […]

10/22/21:

19:10 Changeset in rtems-tools [366807c] by Ryan Long <ryan.long@…>
SymbolTable?.cc: Fix formatting
18:16 Changeset in rtems-tools [29f00bd] by Ryan Long <ryan.long@…>
ObjdumpProcessor?.h: Fix formatting
17:17 Changeset in rtems-tools [2ddc316] by Ryan Long <ryan.long@…>
ObjdumpProcessor?: Convert to C++
05:31 Changeset in rtems [577262a7] by Sebastian Huber <sebastian.huber@…>
score: Add red-black tree append/prepend These functions are a faster alternative to _RBTree_Insert_inline() if it is known that the new node is the maximum/minimum node. Update #4531.

10/21/21:

09:07 Changeset in rtems [757a1096] by Sebastian Huber <sebastian.huber@…>
score: Remove return value from enqueue scheduled The return value was unused. Remove it. Update #4531.
02:08 Changeset in rtems [3f0ad2b] by Chris Johns <chrisj@…>
spec/libdebugger: Only enable for supported architectures Closes #4533
02:04 Ticket #4533 (libdebugger should only build for archs with a backend) created by Chris Johns
Libdebugger has limited backend support however the generic parts are …

10/20/21:

20:57 Changeset in rtems-tools [d7eccfd] by Ryan Long <ryan.long@…>
ConfigFile?: Fix formatting
20:36 Changeset in rtems-tools [7578f43] by Ryan Long <ryan.long@…>
ConfigFile?: Convert to C++
17:14 Changeset in rtems [28632b5] by Sebastian Huber <sebastian.huber@…>
score: Fix typo
14:11 Changeset in rtems-tools [361e304] by Ryan Long <ryan.long@…>
Target: Convert to C++
12:21 Changeset in rtems [ff20bc9] by Sebastian Huber <sebastian.huber@…>
score: Rework idle handling in SMP schedulers This patch fixes an issue with the idle thread handling in the SMP scheduler framework used for the MrsP locking protocol. The approach to use a simple chain of unused idle threads is broken for schedulers which support thread to processor affinity. The reason is that the thread to processor affinity introduces another ordering indicator which may under certain conditions lead to a reordering of idle threads in the scheduled chain. This reordering is not propagated to the chain of unused idle threads. This could lead to use an idle thread for a sticky scheduler node which is already in use. This locks up the system in infinite loops in the thread context switch procedure. To fix this, the SMP scheduler implementations must now provide callbacks to get and release an unused idle thread. Update #4531.
06:24 Changeset in rtems [3781709] by Sebastian Huber <sebastian.huber@…>
score: Add SMP scheduler idle exchange callback Update #4531.
06:23 Changeset in rtems [81659420] by Sebastian Huber <sebastian.huber@…>
score: Add missing idle thread exchanges Update #4531.
06:20 Changeset in rtems [e787091] by Sebastian Huber <sebastian.huber@…>
score: Add missing idle thread releases Update #4531.
05:37 Ticket #4532 (Priority inversion issues with MrsP locking protocol implementation) created by Sebastian Huber
While a thread is scheduled on a helping scheduler, while it does not …
05:32 Ticket #4531 (Data corruption in SMP schedulers) created by Sebastian Huber
Certain operations involving sticky thread queues, thread to processor …
03:15 Changeset in rtems-libbsd [25a8832]6-freebsd-12 by Chris Johns <chrisj@…>
Add support for Xilinx Versal APAC
03:13 Changeset in rtems-libbsd [87a5b45]6-freebsd-12 by Chris Johns <chrisj@…>
rtemsbsd/nfsclient: Fix the error code return value
02:47 Changeset in rtems-libbsd [6ee31ae]6-freebsd-12 by Chris Johns <chrisj@…>
waf: Move the tools/BSP include path to be last - This change lets you rebuild libbsd after it is installed
02:42 Changeset in rtems-libbsd [f94a67a]6-freebsd-12 by Chris Johns <chrisj@…>
rtemsbsd: Clear bus DMA memory a byte at a time - memset may be optimized for performance and might work with device type memory. Clear a byte at a time.

10/19/21:

20:50 Changeset in rtems [087e4ec] by Kinsey Moore <kinsey.moore@…>
spec/aarch64: Enable previously unbuildable tests The spconfig01 and spmisc01 tests were disabled for all AArch64 BSPs due to a toolchain issue preventing them from compiling correctly. The binutils version that contains the fix has been released and integrated into RSB such that these two tests now build and operate correctly.
15:12 Changeset in rtems-central [fd227bf] by Sebastian Huber <sebastian.huber@…>
spec: Fix typo
15:00 Changeset in rtems-central [a312b2b] by Sebastian Huber <sebastian.huber@…>
spec: Clarify boot time
14:51 Changeset in rtems-central [3207e03] by Sebastian Huber <sebastian.huber@…>
spec: Add idle task stack allocator option
14:42 Changeset in rtems-docs [46dbb6d] by Sebastian Huber <sebastian.huber@…>
c-user: Regenerate for IDLE task allocator option Update #4524.
14:37 Changeset in rtems [9be97a3] by Sebastian Huber <sebastian.huber@…>
score: Optimize default idle task stack allocator Update #4524.
14:29 Changeset in rtems [f1723d12] by Sebastian Huber <sebastian.huber@…>
rtems: Regenerate for IDLE task allocator option Update #4524.
13:49 Ticket #4218 (aarch64 as internal error with spconfig01) closed by Ryan Long <ryan.long@…>
fixed: In e04fddc/rtems-source-builder: […]
12:28 Changeset in rtems [9d3e8212] by Sebastian Huber <sebastian.huber@…>
score: Rework affine ready queue handling Rework the handling of the affine ready queue for the EDF SMP scheduler. Do the queue handling in the node insert, move, and extract operations. Remove the queue handling from _Scheduler_EDF_SMP_Allocate_processor(). Update #4531.
11:06 Changeset in rtems [a53229bb] by Sebastian Huber <sebastian.huber@…>
score: Use extract from scheduled callbacks Use the extract from scheduled callback provided by the scheduler implementation in the SMP scheduler framework. Update #4531.
10:43 Changeset in rtems [6286a40] by Sebastian Huber <sebastian.huber@…>
score: Scheduler insert after move Insert nodes after moving the second node to reduce the items in the data structure for the insert operation. This also avoids having two nodes for the same processor inserted into the scheduled chain. Update #4531.
09:25 Changeset in rtems [bd55f69] by Sebastian Huber <sebastian.huber@…>
score: Simplify _Scheduler_Exchange_idle_thread() Remove superfluous idle parameter. Update #4531.
09:21 Changeset in rtems [f0f60a1e] by Sebastian Huber <sebastian.huber@…>
score: Change _Scheduler_Try_to_schedule_node() Add the victim node as parameter instead of the idle thread. Update #4531.

10/18/21:

23:46 Changeset in rtems [19c10128] by zack leung <zakthertemsdev@…>
libtests/calloc.c: Fix reported memory leak This fix came from Code Inspector, flagged by one of the analysis that was done. This test code is compiled only but better to address the issues so future static analysis reports will not include it.
15:32 Ticket #4501 (TraceConverter.cc: Uncaught exception issue spotted by Coverity) reopened by Ryan Long
11:14 Changeset in rtems [6c3976e2] by Sebastian Huber <sebastian.huber@…>
score: Move code block to separate function Move a code block to the new function _Thread_Scheduler_withdraw_nodes() to ease code review.
11:13 Changeset in rtems [940b9b1] by Sebastian Huber <sebastian.huber@…>
score: Do not shadow lock_context local variable
10:28 Changeset in rtems-central [dbfea64b] by Sebastian Huber <sebastian.huber@…>
spec: Specify SMP EDF scheduler set affinity
07:07 Changeset in rtems [7ae4f569] by Sebastian Huber <sebastian.huber@…>
score: Not set CPU in _Scheduler_Use_idle_thread() Do not set the CPU of the idle thread in _Scheduler_Use_idle_thread(). This helps to use _Scheduler_Try_to_schedule_node() under more general conditions in the future, for example in case the owner and user of a node are not the same. Update #4531.
07:05 Changeset in rtems [45e942d] by Sebastian Huber <sebastian.huber@…>
score: Rename _Scheduler_Set_idle_thread() Rename _Scheduler_Set_idle_thread() in _Scheduler_Node_set_idle_user() and move it to <rtems/score/schedulernodeimpl.h>. Update #4531.

10/17/21:

15:00 Changeset in rtems-libbsd [66923c7]6-freebsd-12 by Konstantin Belousov <kib@…>
Kernel-side infrastructure to implement nvlist-based set/get ifcaps Reviewed by: hselasky, jhb, kp (previous version) Sponsored by: NVIDIA Networking MFC after: 3 weeks Differential revision: https://reviews.freebsd.org/D32551
15:00 Changeset in rtems-libbsd [7974c8b] by Konstantin Belousov <kib@…>
Kernel-side infrastructure to implement nvlist-based set/get ifcaps Reviewed by: hselasky, jhb, kp (previous version) Sponsored by: NVIDIA Networking MFC after: 3 weeks Differential revision: https://reviews.freebsd.org/D32551

10/16/21:

13:46 Changeset in rtems [e27dc9d]5 by Mark Johnston <markj@…>
timecounter: Lock the timecounter list Timecounter registration is dynamic, i.e., there is no requirement that timecounters must be registered during single-threaded boot. Loadable drivers may in principle register timecounters (which can be switched to automatically). Timecounters cannot be unregistered, though this could be implemented. Registered timecounters belong to a global linked list. Add a mutex to synchronize insertions and the traversals done by (mpsafe) sysctl handlers. No functional change intended. Reviewed by: imp, kib MFC after: 2 weeks Sponsored by: The FreeBSD Foundation Differential Revision: https://reviews.freebsd.org/D32511
13:46 Changeset in rtems [ea389aaa] by Mark Johnston <markj@…>
timecounter: Lock the timecounter list Timecounter registration is dynamic, i.e., there is no requirement that timecounters must be registered during single-threaded boot. Loadable drivers may in principle register timecounters (which can be switched to automatically). Timecounters cannot be unregistered, though this could be implemented. Registered timecounters belong to a global linked list. Add a mutex to synchronize insertions and the traversals done by (mpsafe) sysctl handlers. No functional change intended. Reviewed by: imp, kib MFC after: 2 weeks Sponsored by: The FreeBSD Foundation Differential Revision: https://reviews.freebsd.org/D32511
00:18 Changeset in rtems [10226104] by Kinsey Moore <kinsey.moore@…>
cpukit/libdebugger: Use uintptr_t for pointers Use uintptr_t instead of DB_UINT when the variable in question describes a pointer.

10/15/21:

09:21 Changeset in rtems [3d6ebde1] by Sebastian Huber <sebastian.huber@…>
score: Add SMP scheduler make/clean sticky This patch fixes the following broken behaviour: While a thread is scheduled on a helping scheduler, while it does not own a MrsP semaphore, if it obtains a MrsP semaphore, then no scheduler node using an idle thread and the ceiling priority of the semaphore is unblocked for the home scheduler. This could lead to priority inversion issues and is not in line with the MrsP protocol. Introduce two new scheduler operations which are only enabled if RTEMS_SMP is defined. The operations are used to make the scheduler node of the home scheduler sticky and to clean the sticky property. This helps to keep the sticky handing out of the frequently used priority update operation. Close #4532.
08:25 Changeset in rtems-central [f30f7c3] by Sebastian Huber <sebastian.huber@…>
spec: Fix rtems_cpu_usage_report() test

10/14/21:

06:44 Changeset in rtems-source-builder [e845bd5] by Alex White <alex.white@…>
rtems-tools-6.cfg: Bump hash to include MicroBlaze? Hash: 323007a6b520140a20b2e268c90b78ff67afaf45
Note: See TracTimeline for information about the timeline view.