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

2020-11-15 Thread Sebastian Huber
On 16/11/2020 00:53, Chris Johns wrote: On 13/11/20 9:07 pm, Sebastian Huber wrote: 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

Re: Proposal for hardware configuration dependent performance limits

2020-11-15 Thread Sebastian Huber
On 16/11/2020 00:33, Chris Johns wrote: In the proposal, limits are specified like this: limits:     sparc/gr712rc:   DirtyCache:     max-upper-bound: 0.05     mean-upper-bound: 0.05   FullCache:     max-upper-bound: 0.05     mean-upper-bound: 0.0

Re: [PATCH] config: Initialize task stack alllocator on demand

2020-11-15 Thread Sebastian Huber
On 15/11/2020 22:51, Chris Johns wrote: How does this effect this documentation ... https://docs.rtems.org/branches/master/c-user/config/task-stack-alloc.html#configure-task-stack-allocator-init ? No, the allocator initialization handler is documented as optional. However, I missed that _Stac

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

2020-11-15 Thread Chris Johns
On 13/11/20 9:07 pm, Sebastian Huber wrote: > 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 ++ > tes

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

2020-11-15 Thread Chris Johns
On 14/11/20 11:13 pm, Sebastian Huber wrote: > On 13/11/2020 20:21, Gedare Bloom wrote: > >> 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

Re: Proposal for hardware configuration dependent performance limits

2020-11-15 Thread Chris Johns
On 14/11/20 11:20 pm, Sebastian Huber wrote: > On 13/11/2020 20:01, Gedare Bloom wrote: > >> 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:/

Re: [PATCH] config: Initialize task stack alllocator on demand

2020-11-15 Thread Chris Johns
Hi, How does this effect this documentation ... https://docs.rtems.org/branches/master/c-user/config/task-stack-alloc.html#configure-task-stack-allocator-init ? What drives the demand? Thanks Chris On 13/11/20 8:24 pm, Sebastian Huber wrote: > --- > cpukit/include/rtems/confdefs/wkspace.h |

Re: [PATCH rtems-tools] bsps/a53_*: Fix typo in qemu options

2020-11-15 Thread Vijay Kumar Banerjee
On Sun, Nov 15, 2020 at 11:17 PM Gedare Bloom wrote: > On Sun, Nov 15, 2020 at 8:37 AM Vijay Kumar Banerjee > wrote: > > > > Hi Kinsey, > > > > Thanks for reviewing the patch... > > > > On Sun, Nov 15, 2020 at 9:51 AM Kinsey Moore > wrote: > >> > >> Odd, "gic_version" works just fine in the ver

Re: [PATCH rtems-tools] bsps/a53_*: Fix typo in qemu options

2020-11-15 Thread Gedare Bloom
On Sun, Nov 15, 2020 at 8:37 AM Vijay Kumar Banerjee wrote: > > Hi Kinsey, > > Thanks for reviewing the patch... > > On Sun, Nov 15, 2020 at 9:51 AM Kinsey Moore wrote: >> >> Odd, "gic_version" works just fine in the version of qemu-system-aarch64 in >> the Debian package repos which is what I'v

Re: [PATCH rtems-tools] bsps/a53_*: Fix typo in qemu options

2020-11-15 Thread Vijay Kumar Banerjee
Hi Kinsey, Thanks for reviewing the patch... On Sun, Nov 15, 2020 at 9:51 AM Kinsey Moore wrote: > Odd, "gic_version" works just fine in the version of qemu-system-aarch64 > in the Debian package repos which is what I've been testing against. As > you've provided in the patch, the official opti