Re: Proposal for hardware configuration dependent performance limits

I don't understand this proposal. Is this an approach used somewhere else where I can review how this works? If not I need a clearer explanation. > On Nov 13, 2020, at 14:01 , Gedare Bloom wrote: > > On Fri, Nov 13, 2020 at 3:48 AM Sebastian Huber > wrote: >> >> Hello, >> >> there is one

Re: [PATCH 0/8] Add test suite to validate performance requirements

I didn't really raise this in your other threads related to performance, but how are we (RTEMS Project) defining performance requirements? Are these simply the performance values we get by running the tests on our release? Do we aim to hit certain targets and reject patches if they don't? Or do we

Re: [PATCH] eng: Add performance specification items

On Fri, Nov 13, 2020 at 2:47 AM Sebastian Huber wrote: > > Add items to specify runtime performance requirements. > > Update #3715. > --- > > You find an updated document here: > > https://ftp.rtems.org/pub/rtems/people/sebh/eng.pdf > > eng/req/items.rst | 616

Re: Proposal for hardware configuration dependent performance limits

On Fri, Nov 13, 2020 at 3:48 AM Sebastian Huber wrote: > > Hello, > > there is one aspect with respect to performance limits which is > currently not considered in this proposal: > > https://lists.rtems.org/pipermail/devel/2020-November/063213.html > > You can run the some BSPs such as

RE: [PATCH 1/2] spec/aarch64: Ensure that libbsd can build properly

-Original Message- From: Sebastian Huber Sent: Friday, November 13, 2020 04:23 To: Kinsey Moore ; devel@rtems.org Subject: Re: [PATCH 1/2] spec/aarch64: Ensure that libbsd can build properly On 12/11/2020 14:32, Kinsey Moore wrote: >> install: >> +- destination: ${BSP_INCLUDEDIR}/bsp

RE: [PATCH 2/2] spec/aarch64: Only apply SUBALIGN(4) to ILP32

-Original Message- From: Sebastian Huber Sent: Friday, November 13, 2020 08:16 To: Kinsey Moore ; devel@rtems.org Subject: Re: [PATCH 2/2] spec/aarch64: Only apply SUBALIGN(4) to ILP32 >On 13/11/2020 15:13, Kinsey Moore wrote: > >> -Original Message- >> From: Sebastian Huber >>

Re: [PATCH 2/2] spec/aarch64: Only apply SUBALIGN(4) to ILP32

On 13/11/2020 15:13, Kinsey Moore wrote: -Original Message- From: Sebastian Huber Sent: Friday, November 13, 2020 04:26 To: Kinsey Moore;devel@rtems.org Subject: Re: [PATCH 2/2] spec/aarch64: Only apply SUBALIGN(4) to ILP32 On 12/11/2020 14:32, Kinsey Moore wrote: The SUBALIGN(4)

RE: [PATCH 2/2] spec/aarch64: Only apply SUBALIGN(4) to ILP32

-Original Message- From: Sebastian Huber Sent: Friday, November 13, 2020 04:26 To: Kinsey Moore ; devel@rtems.org Subject: Re: [PATCH 2/2] spec/aarch64: Only apply SUBALIGN(4) to ILP32 >On 12/11/2020 14:32, Kinsey Moore wrote: > >> The SUBALIGN(4) required on rtemsroset and rtemsrwset

Proposal for hardware configuration dependent performance limits

Hello, there is one aspect with respect to performance limits which is currently not considered in this proposal: https://lists.rtems.org/pipermail/devel/2020-November/063213.html You can run the some BSPs such as sparc/gr712rc on several boards. However, each board may have different

Re: [PATCH 2/2] spec/aarch64: Only apply SUBALIGN(4) to ILP32

On 12/11/2020 14:32, Kinsey Moore wrote: The SUBALIGN(4) required on rtemsroset and rtemsrwset for ILP32 builds was previously present on LP64 builds and causes no issues within RTEMS, but causes relocation/alignment issues when building libbsd. This restricts those alignment changes to ILP32

Re: [PATCH 1/2] spec/aarch64: Ensure that libbsd can build properly

On 12/11/2020 14:32, Kinsey Moore wrote: These files are required for libbsd to build against the AArch64 A53 BSPs. --- spec/build/bsps/aarch64/grp.yml | 4 1 file changed, 4 insertions(+) diff --git a/spec/build/bsps/aarch64/grp.yml b/spec/build/bsps/aarch64/grp.yml index

Re: [PATCH rtems-libbsd] Update arm64/aarch64 support

Looks good. -- embedded brains GmbH Sebastian HUBER Dornierstr. 4 82178 Puchheim Germany email: sebastian.hu...@embedded-brains.de Phone: +49-89-18 94 741 - 16 Fax: +49-89-18 94 741 - 08 PGP: Public key available on request. embedded brains GmbH Registergericht: Amtsgericht München

[PATCH 8/8] validation/ts-performance-0: Add partition tests

--- .../testsuites/validation/performance-0.yml | 1 + testsuites/validation/tc-part-performance.c | 437 ++ 2 files changed, 438 insertions(+) create mode 100644 testsuites/validation/tc-part-performance.c diff --git a/spec/build/testsuites/validation/performance-0.yml

[PATCH 2/8] libtest: Simplify runtime measurement support

Use the test case allocator functions T_zalloc() and T_malloc(). Restore the task affinity of the runner task. --- cpukit/libtest/t-test-rtems-measure.c | 79 +++ 1 file changed, 32 insertions(+), 47 deletions(-) diff --git a/cpukit/libtest/t-test-rtems-measure.c

[PATCH 6/8] libtest: Simplify "Load" environment reporting

Report all runtime measurement environments with a name only and encode the worker count of the "Load" environment in the name. Update #3199. --- cpukit/libtest/t-test-rtems-measure.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/cpukit/libtest/t-test-rtems-measure.c

[PATCH 5/8] libtest: Allow assert checks during test begin

Allow assert checks in test begin actions and setup fixture methods. --- cpukit/include/rtems/test.h | 2 +- cpukit/libtest/t-test.c | 29 + 2 files changed, 18 insertions(+), 13 deletions(-) diff --git a/cpukit/include/rtems/test.h b/cpukit/include/rtems/test.h

[PATCH 4/8] libtest: Rename ValidCache in FullCache

This name better reflects the execution envirnoment in which the cache is fully loaded with valid data unrelated to the body request handler. --- cpukit/include/rtems/test.h | 2 +- cpukit/libtest/t-test-rtems-measure.c | 10 +- 2 files changed, 6 insertions(+), 6 deletions(-)

[PATCH 1/8] libtest: Make test case allocator configurable

--- cpukit/Makefile.am | 1 - cpukit/include/rtems/test.h| 2 + cpukit/libtest/t-test-malloc.c | 112 - cpukit/libtest/t-test.c| 86 ++ cpukit/libtest/testrun.c | 4 ++

[PATCH 7/8] validation/ts-performance-0: Add test suite

Share a default test suite with ts-validation-0. --- spec/build/testsuites/validation/grp.yml | 2 + .../testsuites/validation/performance-0.yml | 19 ++ testsuites/validation/ts-default.h| 237 ++ testsuites/validation/ts-performance-0.c | 74 ++

[PATCH 0/8] Add test suite to validate performance requirements

This patch set introduces a test suite for runtimer performance validation tests and a test case for the Partition Manager. Sebastian Huber (8): libtest: Make test case allocator configurable libtest: Simplify runtime measurement support libtest: Add primitive test case memory allocator

[PATCH 3/8] libtest: Add primitive test case memory allocator

This primitive test case memory allocator uses memory from the low-level memory information provided by the BSP. At the beginning of each test case, the memory available to the test case is reinitialized. This allows the use of a simple allocate only allocator. --- cpukit/include/rtems/test.h

[PATCH] eng: Add performance specification items

Add items to specify runtime performance requirements. Update #3715. --- You find an updated document here: https://ftp.rtems.org/pub/rtems/people/sebh/eng.pdf eng/req/items.rst | 616 +- 1 file changed, 503 insertions(+), 113 deletions(-) diff

[PATCH] config: Initialize task stack alllocator on demand

--- cpukit/include/rtems/confdefs/wkspace.h | 14 ++ 1 file changed, 6 insertions(+), 8 deletions(-) diff --git a/cpukit/include/rtems/confdefs/wkspace.h b/cpukit/include/rtems/confdefs/wkspace.h index d40194cbec..6df3b15ca0 100644 --- a/cpukit/include/rtems/confdefs/wkspace.h +++