Hi, For the footprint you can get most information from the GNU Binutils. Startup time you will have to implement. you can always use a HW timer early in redboot and dump it when your application is fully up and running but you will have to implement such timer for all architecture you are going to test. Response time? Not sure what this is. You can run some test applications such as:
- packages\kernel\current\tests\tm_basic.cxx or the Dhrystone kernel\current\tests\dhrystone.c Only the i386 HAL support more than 1 core, if you google around, you will find some LEON3, ARM, PPC SMP HAL. You could look at QEMU but it is not cycle accurate so not necessarily what you are looking for. Christophe -----Original Message----- From: ecos-discuss-ow...@ecos.sourceware.org [mailto:ecos-discuss-ow...@ecos.sourceware.org] On Behalf Of Jianmei Guo Sent: 4. mai 2012 16:03 To: ecos-disc...@sources.redhat.com Subject: [ECOS] Tools or commands for eCos to test footprint, startup time, and response time Hi, Is there any tool or command available for ECOS to test footprint, startup time, and response time (or any other performance metrics) conveniently when eCos is running on different hardware platforms (e.g., i386 vs. Powerpc) and/or different software configurations (e.g., 2 cpu vs. 4 cpu)? Another question is about the simulation of many different hardware platform. Now I just have several i386 PC and Apple MacBook... Any help or suggestion would be appreciable. Thanks! Best Regards, Jianmei Guo, PhD Postdoctoral Fellow University of Waterloo http://gsd.uwaterloo.ca/gjm -- Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
