Re: Coding Style: inline functions Was: Posix patchs to support affinity attribute in newlib

On 2014-03-03 15:20, Gedare Bloom wrote: On Mon, Mar 3, 2014 at 9:03 AM, Sebastian Huber wrote: I would like to add this to the RTEMS Coding Style: http://www.rtems.org/wiki/index.php/Coding_Conventions#RTEMS_Coding_Style === Inline Functions === Declare and define inline functions in one p

Re: Condition Variables for RTEMS

Dear all, Recently i have been study the RTEMS code and all related resource about condition variables. At the meantime i am preparing a proposal for this GSOC project. Although it is just a skeleton draft, i think it is better to throw it ASAP. So that everyone can give me some valuable suggestio

Re: Condition Variables for RTEMS

Hi Sebastian, Thank you for your reply! 2014-03-03 15:06 GMT+08:00 Sebastian Huber < sebastian.hu...@embedded-brains.de>: > On 2014-03-02 03:40, zhang json wrote: > >> >> 2014-02-28 15:15 GMT+08:00 Sebastian Huber > brains.de >> >: >> >> >> On 2014-

RE: Posix patchs to support affinity attribute in newlib

> -Original Message- > From: ged...@gwmail.gwu.edu [mailto:ged...@gwmail.gwu.edu] On > Behalf Of Gedare Bloom > Sent: Monday, March 03, 2014 10:46 AM > To: Sebastian Huber > Cc: Jennifer Averett; rtems-devel@rtems.org > Subject: Re: Posix patchs to support affinity attribute in newlib > >

Re: [GSoC 2014] Paravirtualization Layer of RTEMS.

Hi Youren, can you please explain your proposed hypercall solution in more detail. Lets assume RTEMS requests notification for an interrupt line, e.g IRQ 0. How is the request delivered from RTEMS to POK in your solution? The big issue is the delivery of interrupts to the guest system (RTEMS): Ho

Re: GSoC 2014 | Poring RTEMS for OpenRISC

Hesham, On Mon, Mar 3, 2014 at 11:06 AM, Hesham Moustafa wrote: > > > > On Mon, Mar 3, 2014 at 5:06 PM, Joel Sherrill > wrote: >> >> >> On Mar 3, 2014 8:23 AM, Gedare Bloom wrote: >> > >> > Hesham, >> > >> > The first question to figure out is why was the older port dropped. >> >> This I can an

Re: [PATCH 3/3] rtems: Add RTEMS_INTERRUPT_REPLACE

Summary: A new option RTEMS_INTERRUPT_REPLACE is introduced that permits updating the 'first' interrupt handler for the registered interrupt vector and matching argument. If no match is found, the install function fails with RTEMS_UNSATISFIED. On Mon, Mar 3, 2014 at 10:29 AM, Sebastian Huber wrot

Re: Posix patchs to support affinity attribute in newlib

On Mon, Mar 3, 2014 at 10:56 AM, Sebastian Huber wrote: > On 2014-03-03 16:36, Jennifer Averett wrote: >>> >>> >Is the implementation correct for CPU sets which are not pre-allocated? >>> > >> >> Until we have a system that supports over 32 CPU's the implementation can >> not be tested for this.

Re: GSoC 2014 | Poring RTEMS for OpenRISC

On Mon, Mar 3, 2014 at 5:06 PM, Joel Sherrill wrote: > > On Mar 3, 2014 8:23 AM, Gedare Bloom wrote: > > > > Hesham, > > > > The first question to figure out is why was the older port dropped. > > This I can answer. The tool chain rotted and had no maintainer. I also > recall not having a simulat

Re: Posix patchs to support affinity attribute in newlib

On 2014-03-03 16:36, Jennifer Averett wrote: >Is the implementation correct for CPU sets which are not pre-allocated? > Until we have a system that supports over 32 CPU's the implementation can not be tested for this. I minimized the locations that will have to be touched when we support this b

RE: Posix patchs to support affinity attribute in newlib

> -Original Message- > From: Sebastian Huber [mailto:sebastian.hu...@embedded-brains.de] > Sent: Monday, March 03, 2014 8:10 AM > To: Jennifer Averett > Cc: rtems-devel@rtems.org > Subject: Re: Posix patchs to support affinity attribute in newlib > > On 2014-02-28 16:30, Jennifer Averett

[PATCH 3/3] rtems: Add RTEMS_INTERRUPT_REPLACE

The Interrupt Manager Extension offers interrupt handlers with an argument pointer. It is impossible to update two words (handler and argument) atomically on most architectures. In order to avoid an SMP lock in bsp_interrupt_handler_dispatch() which would degrade the interrupt response time an al

[PATCH 2/3] bsps: SMP support for generic interrupt support

--- c/src/lib/libbsp/shared/include/irq-generic.h | 30 ++-- c/src/lib/libbsp/shared/src/irq-generic.c | 47 +--- 2 files changed, 59 insertions(+), 18 deletions(-) diff --git a/c/src/lib/libbsp/shared/include/irq-generic.h b/c/src/lib/libbsp/shared/includ

[PATCH 1/3] score: Add _Atomic_Fence()

--- cpukit/score/include/rtems/score/atomic.h |7 +++ cpukit/score/include/rtems/score/cpustdatomic.h |7 +++ testsuites/smptests/smpatomic01/init.c | 63 --- testsuites/smptests/smpatomic01/smpatomic01.scn | 26 + 4 files changed, 84 insertio

Re: GSoC 2014 | Poring RTEMS for OpenRISC

On Mar 3, 2014 8:23 AM, Gedare Bloom wrote: > > Hesham, > > The first question to figure out is why was the older port dropped. This I can answer. The tool chain rotted and had no maintainer. I also recall not having a simulator to test on. The final issue was some discrepancy between multiple

Re: GSoC 2014 | Poring RTEMS for OpenRISC

Hesham, The first question to figure out is why was the older port dropped. The second is what is your interest in porting to OpenRISC? Gedare On Sun, Mar 2, 2014 at 12:39 AM, Hesham Moustafa wrote: > Hi, > > I am thinking of porting RTEMS for OpenRISC as a proposal for GSoC project > this year

Coding Style: inline functions Was: Posix patchs to support affinity attribute in newlib

On Mon, Mar 3, 2014 at 9:03 AM, Sebastian Huber wrote: > > I would like to add this to the RTEMS Coding Style: > > http://www.rtems.org/wiki/index.php/Coding_Conventions#RTEMS_Coding_Style > > === Inline Functions === > > Declare and define inline functions in one place. This makes code review >

Re: SuperCore Scheduler (GSOC 2014)

On Mon, Mar 3, 2014 at 2:21 AM, Sebastian Huber wrote: > On 2014-03-01 01:13, Andre Marques wrote: >> >> Hello, >> >> As stated in [1] I will be working with RTEMS for my undergraduate thesis, >> but >> I'm also looking to work with RTEMS through GSOC. >> >> For the last month I have been working

Re: Posix patchs to support affinity attribute in newlib

On 2014-02-28 16:30, Jennifer Averett wrote: >-Original Message- >From:rtems-devel-boun...@rtems.org [mailto:rtems-devel- >boun...@rtems.org] On Behalf Of Sebastian Huber >Sent: Friday, February 28, 2014 1:12 AM >To:rtems-devel@rtems.org >Subject: Re: Posix patchs to support affinity a

Re: Posix patchs to support affinity attribute in newlib

On 2014-02-28 16:30, Jennifer Averett wrote: + * structure to copy from. > >+ */ > >+RTEMS_INLINE_ROUTINE void _POSIX_Threads_Copy_attributes( > >+ pthread_attr_t *attr1, > >+ const pthread_attr_t *attr2 > >+); > >+ > >Why do we have the definition of this inline function separated from the

[GSoC 2014] Paravirtualization Layer of RTEMS.

Hi, everyone, These days I’m running the hello world example on POK, reading the source code of POK and the patch to RTEMS, knowing the work has been done before me. After that, I draft my proposal. Could you review it? However, as the time gets tight , I can’t catch every detail. So if there are

SMP Requirements

Hello, I updated the SMP wiki page with a set of requirements that came into my mind. Please correct, update and review this section: http://www.rtems.org/wiki/index.php/SMP#Requirements -- Sebastian Huber, embedded brains GmbH Address : Dornierstr. 4, D-82178 Puchheim, Germany Phone : +4

Re: [PATCH 12/17] libbsp/xilinx-zynq: Share handling for ARM cache controller L2C-310

So far I only made sure that all ARM BSPs still build OK. I plan to do some testing on a Zynq board tomorrow. Ideas for tests would be: - Create network traffic by doing uploads and downlowds via curl to/from /dev/NULL / /dev/ZERO. This should stress the cache handling and problems should become vi