On Fri, Aug 14, 2015 at 8:33 AM, Chris Johns chr...@rtems.org wrote:
On 14/08/2015 7:44 am, Rohini Kulkarni wrote:
---
-BSP_START_DATA_SECTION static const arm_cp15_start_section_config
-zynq_mmu_config_table[] = {
+BSP_START_DATA_SECTION const arm_cp15_start_section_config
From: YANG Qiao yangqiao0...@me.com
---
source-builder/config/microwindows-1.cfg | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/source-builder/config/microwindows-1.cfg
b/source-builder/config/microwindows-1.cfg
index 5057d71..5ff1b22 100644
---
Joel Sherrill joel.sherr...@oarcorp.com schrieb am Fr., 14. Aug. 2015 um
04:26 Uhr:
On August 13, 2015 7:15:08 PM CDT, Chris Johns chr...@rtems.org wrote:
On 14/08/2015 6:34 am, Daniel Gutson wrote:
I'd recommend a gcc plugin that generates your annotations;
There is a Python framework
From: YANG Qiao yangqiao0...@me.com
---
tools/4.11/t1lib/t1lib-5.1.2.diff | 75 +++
1 file changed, 75 insertions(+)
create mode 100644 tools/4.11/t1lib/t1lib-5.1.2.diff
diff --git a/tools/4.11/t1lib/t1lib-5.1.2.diff
b/tools/4.11/t1lib/t1lib-5.1.2.diff
new
Hi,
I have implemented the validate method. following are the links for it:
github: https://github.com/saurabhgadia4/rtems/tree/nested-mutex
commit:
https://github.com/saurabhgadia4/rtems/commit/e7f0f169c056076c46ef5ea17b0c38efe33fe576
I am waiting on the decision of how to integrate call to
And in respect of efficiency, we have to traverse through all the mutex
held my the thread and do the checking. There is no other way to confirm
that priority inversion has occurred or not. One way we can do is have
default argument variable for core_mutex_surrender but then there is change
in API
When a thread releases a semaphore/mutex we call this validate method to
make sure that there does not exists any priority inversion. Following is
the course of action that needs to be performed:
1. Validate method needs to be called within mutex_surrender method because
after releasing a mutex a
