extra memory and queue memory was Re: [rtems commit] rhealstone/rhmlatency: Fix configuration

Joel Sherrill joel.sherrill at OARcorp.com
Fri Apr 4 15:10:33 UTC 2014


We generally need to make a sweep through the tests
for any cases that:

+ configure a message queue and don't reserve memory for
   message buffers.

+ Use CONFIGURE_MEMORY_OVERHEAD. This is supposed
   to be a work around.

+ Define CONFIGURE_EXECUTIVE_RAM_SIZE explicitly rather than
   letting confdefs.h compute it. I hope none actually do this but
   we should check.

--joel
On 4/4/2014 9:59 AM, Sebastian Huber wrote:
> Module:    rtems
> Branch:    master
> Commit:    cae120e23ce0f5923c5949a8de1d2eae7ef76a78
> Changeset: http://git.rtems.org/rtems/commit/?id=cae120e23ce0f5923c5949a8de1d2eae7ef76a78
>
> Author:    Sebastian Huber <sebastian.huber at embedded-brains.de>
> Date:      Fri Apr  4 16:32:10 2014 +0200
>
> rhealstone/rhmlatency: Fix configuration
>
> ---
>
>  testsuites/rhealstone/rhmlatency/mlatency.c |    2 ++
>  1 files changed, 2 insertions(+), 0 deletions(-)
>
> diff --git a/testsuites/rhealstone/rhmlatency/mlatency.c b/testsuites/rhealstone/rhmlatency/mlatency.c
> index 4ddf808..10104e6 100644
> --- a/testsuites/rhealstone/rhmlatency/mlatency.c
> +++ b/testsuites/rhealstone/rhmlatency/mlatency.c
> @@ -148,6 +148,8 @@ rtems_task Task02( rtems_task_argument ignored )
>  
>  #define CONFIGURE_MAXIMUM_TASKS              3
>  #define CONFIGURE_MAXIMUM_MESSAGE_QUEUES     1
> +#define CONFIGURE_MESSAGE_BUFFER_MEMORY \
> +  CONFIGURE_MESSAGE_BUFFERS_FOR_QUEUE(1, MESSAGE_SIZE)
>  #define CONFIGURE_TICKS_PER_TIMESLICE        0
>  #define CONFIGURE_RTEMS_INIT_TASKS_TABLE
>  
>
> _______________________________________________
> rtems-vc mailing list
> rtems-vc at rtems.org
> http://www.rtems.org/mailman/listinfo/rtems-vc

-- 
Joel Sherrill, Ph.D.             Director of Research & Development
joel.sherrill at OARcorp.com        On-Line Applications Research
Ask me about RTEMS: a free RTOS  Huntsville AL 35805
Support Available                (256) 722-9985




More information about the devel mailing list