Re: [Xenomai-core] xenomai-core ftrace
On 2011-09-05 04:32, rainbow wrote: > hi, > I did a test for ftrace-xenomai on x86_64 test just now: > the environment is : OS: debian 6.0 gcc-4.1 > I use origin/queues/2.6.37-x86 branch on git > git://git.kiszka.org/ipipe-2.6for linux kernel and use branch > origin/queues/ftrace on git git:// > git.xenomai.org/xenomai-jki.git > then I do as the following procedures: > 1,cd xenomai git > 2, ./scripts/prepare-kernel.sh --arch=x86_64 --linux=path_to_2.6.37-x86 > 3, cd path_to_2.6.37_x86 > 4,make menuconfig > then enble ftrace on kernel hacking option. > 5,install the kernel and reboot the machine. > 6,do ftrace test > 6.1 mount -t debugfs nodev /sys/kernel/debug > 6.2 cd /sys/kernel/debug/tracing > 6.3 echo function > current_tracer > At last the machine reboot. > Is there something wrong about the above procedure? Thanks! Only queues/2.6.35-x86-trace contains ftrace support. Jan signature.asc Description: OpenPGP digital signature ___ Xenomai-core mailing list Xenomai-core@gna.org https://mail.gna.org/listinfo/xenomai-core
Re: [Xenomai-core] xenomai-core ftrace
hi, I did a test for ftrace-xenomai on x86_64 test just now: the environment is : OS: debian 6.0 gcc-4.1 I use origin/queues/2.6.37-x86 branch on git git://git.kiszka.org/ipipe-2.6for linux kernel and use branch origin/queues/ftrace on git git:// git.xenomai.org/xenomai-jki.git then I do as the following procedures: 1,cd xenomai git 2, ./scripts/prepare-kernel.sh --arch=x86_64 --linux=path_to_2.6.37-x86 3, cd path_to_2.6.37_x86 4,make menuconfig then enble ftrace on kernel hacking option. 5,install the kernel and reboot the machine. 6,do ftrace test 6.1 mount -t debugfs nodev /sys/kernel/debug 6.2 cd /sys/kernel/debug/tracing 6.3 echo function > current_tracer At last the machine reboot. Is there something wrong about the above procedure? Thanks! 2011/9/4 Jan Kiszka > On 2011-09-04 15:16, rainbow wrote: > > 2011/9/4 Jan Kiszka > > > >> On 2011-09-04 14:21, rainbow wrote: > >>> Is the ipipe patch the same as patch like > >>> adeos-ipipe-2.6.37.6-x86-2.9-02.patch, > >> > >> Except that the trace branch is for 2.6.35, yes. More precisely it is > >> now the same, I just pushed the latest version that includes two more > >> backported ipipe fixes. > >> > >>> I know the latter is xenomai patch > >>> and after I patch it, I can see "Real-time sub-system ---> " Option. > But > >> If > >>> I use 2.6.35-x86-trace which contains ,there is no such option. > >> > >> That menu option is introduced by Xenomai, ie. after running > >> prepare-kernel.sh. You likely forgot that step. > >> > > > > > >> Yes,I forget the step. So I think I only have to run prepare-kernel.sh > >> --arch=x86_64 > > > > --linux=2.6.35-x86-trace , I do not need --adeos option because > >> the 2.6.35-x86-trace contains the ipipe patch. > >> > > > > > > > >> Note again that you have to use a Xenomai tree with the required ftrace > >> patches on top if you want Xenomai to generate ftrace events as well. > >> > >> "Xenomai tree with required ftrace patches on top" you mean the branch > > "remotes/origin/queues/ftrace"? > > Yep. I just pushed a rebased version of current git master. > > Jan > > -- Qingquan Lv School of Information Science & Engineering , Lanzhou University. mail: lvq...@gmail.com Do what you like, Enjoy your life. ___ Xenomai-core mailing list Xenomai-core@gna.org https://mail.gna.org/listinfo/xenomai-core
[Xenomai-core] PULL REQUEST: analogy
The following changes since commit fa167ed2f2d9ce569968d801796f7e760772e97b: doc: regenerate (2011-09-04 21:48:41 +0200) are available in the git repository at: ssh+git://git.xenomai.org/xenomai-abe.git analogy Alexis Berlemont (28): analogy: add first version of waveform generation analogy: rename waveform files analogy: minor changes analogy: add wf_generate tool analogy: add verbose output in wf_generate tool analogy: add a 1st version of wf_cmd_write analogy: 1st rework of fake driver analogy: [fake] minor fix in attach parameters handling analogy: [fake] validate the looping feature analogy: minor fix in wf_generate analogy: [fake] add instruction callbacks for the loop subdevices analogy: [loop] remove the driver analogy: [fake] correctly manage EOA events for loop subdevices analogy: minor change in cmd_read.c analogy: various basic bug fixes in wf_cmd_write analogy: minor cosmetic changes in wf_facilities.c analogy: [fake] fix synchronization bugs at cancel time analogy: minor change in the test program wf_cmd_write analogy: add signal injection in the cmd_write tool analogy: implement the configuration of a wake-up threshold analogy: update cmd_read and cmd_write with a wake-count option analogy: [ni_660x] replace spin_lock_* calls by al4_lock_* calls analogy: [pcimio] minor cosmetic change analogy: [ni_660x] review indentation analogy: [ni_660x] review coding style and traces analogy: [ni_670x] review coding style analogy: [ni_660x] remove useless headers analogy: [ni_670x] replace printk calls by a4l_[err,info] calls Anders Blomdell (2): analogy: fix duplicate symbols analogy: [pcimio] fix wrong IRQ setup after reboot Julien Delange (1): analogy: integrate the drivers ni_660x and ni_670x. include/analogy/analogy.h | 80 +- include/analogy/buffer.h | 23 + include/analogy/channel_range.h| 16 +- include/analogy/ioctl.h|7 +- ksrc/drivers/analogy/buffer.c | 86 +- ksrc/drivers/analogy/driver_facilities.c | 12 +- ksrc/drivers/analogy/intel/8255.c | 10 +- ksrc/drivers/analogy/intel/8255.h |8 +- ksrc/drivers/analogy/national_instruments/Kconfig | 18 + ksrc/drivers/analogy/national_instruments/Makefile |6 + .../analogy/national_instruments/mio_common.c | 152 +- ksrc/drivers/analogy/national_instruments/mite.c | 164 ++- ksrc/drivers/analogy/national_instruments/mite.h | 51 +- .../drivers/analogy/national_instruments/ni_660x.c | 1485 .../drivers/analogy/national_instruments/ni_670x.c | 446 ++ ksrc/drivers/analogy/national_instruments/ni_mio.h | 18 +- ksrc/drivers/analogy/national_instruments/ni_tio.h | 28 +- ksrc/drivers/analogy/national_instruments/pcimio.c | 70 +- .../analogy/national_instruments/tio_common.c | 82 +- ksrc/drivers/analogy/rtdm_interface.c |8 +- ksrc/drivers/analogy/sensoray/s526.c |4 +- ksrc/drivers/analogy/subdevice.c | 14 +- ksrc/drivers/analogy/testing/Config.in |1 - ksrc/drivers/analogy/testing/Kconfig | 11 +- ksrc/drivers/analogy/testing/Makefile | 11 +- ksrc/drivers/analogy/testing/fake.c| 427 +- ksrc/drivers/analogy/testing/loop.c| 287 src/drvlib/analogy/async.c | 31 + src/utils/analogy/Makefile.am | 18 +- src/utils/analogy/cmd_read.c | 24 +- src/utils/analogy/cmd_write.c | 721 ++ src/utils/analogy/wf_facilities.c | 158 +++ src/utils/analogy/wf_facilities.h | 36 + src/utils/analogy/wf_generate.c| 252 34 files changed, 3719 insertions(+), 1046 deletions(-) create mode 100644 ksrc/drivers/analogy/national_instruments/ni_660x.c create mode 100644 ksrc/drivers/analogy/national_instruments/ni_670x.c delete mode 100644 ksrc/drivers/analogy/testing/loop.c create mode 100644 src/utils/analogy/wf_facilities.c create mode 100644 src/utils/analogy/wf_facilities.h Alexis. ___ Xenomai-core mailing list Xenomai-core@gna.org https://mail.gna.org/listinfo/xenomai-core
[Xenomai-core] Xenomai 2.6.0-rc1
Hi, The first release candidate for the 2.6.0 version may be downloaded here: http://download.gna.org/xenomai/testing/xenomai-2.6.0-rc1.tar.bz2 This version fixes a few issues in the 2.5.x branch which required breaking the ABI: - user-space heap mapping; - user-space access to thread mode; - get threads running with SCHED_OTHER scheduling policy to automatically return to secondary mode after each primary mode only system call (except when holding a mutex); - fix both native and posix condition variables signal handling. contains a few improvements as well: - add support for CLOCK_HOST_REALTIME, a real-time clock synchronized with Linux clock; - factor proc filesystem handling; - the "xeno-test" scripts has been simplified and rebased on "xeno-test-run", which will allow writing custom test scripts; - add support for sh4 architecture; - simplify arm user-space configure script; - move rtdk to libxenomai library, printf is now rt-safe when using the posix skin; - add support for pkg-config, the xenomai skin libraries are available each as a "libxenomai_skin" pkg-config package. Regards. -- Gilles. ___ Xenomai-core mailing list Xenomai-core@gna.org https://mail.gna.org/listinfo/xenomai-core
Re: [Xenomai-core] xenomai-core ftrace
Thank you for so detailed answers!! I will test it. 2011/9/4 Jan Kiszka > On 2011-09-04 15:16, rainbow wrote: > > 2011/9/4 Jan Kiszka > > > >> On 2011-09-04 14:21, rainbow wrote: > >>> Is the ipipe patch the same as patch like > >>> adeos-ipipe-2.6.37.6-x86-2.9-02.patch, > >> > >> Except that the trace branch is for 2.6.35, yes. More precisely it is > >> now the same, I just pushed the latest version that includes two more > >> backported ipipe fixes. > >> > >>> I know the latter is xenomai patch > >>> and after I patch it, I can see "Real-time sub-system ---> " Option. > But > >> If > >>> I use 2.6.35-x86-trace which contains ,there is no such option. > >> > >> That menu option is introduced by Xenomai, ie. after running > >> prepare-kernel.sh. You likely forgot that step. > >> > > > > > >> Yes,I forget the step. So I think I only have to run prepare-kernel.sh > >> --arch=x86_64 > > > > --linux=2.6.35-x86-trace , I do not need --adeos option because > >> the 2.6.35-x86-trace contains the ipipe patch. > >> > > > > > > > >> Note again that you have to use a Xenomai tree with the required ftrace > >> patches on top if you want Xenomai to generate ftrace events as well. > >> > >> "Xenomai tree with required ftrace patches on top" you mean the branch > > "remotes/origin/queues/ftrace"? > > Yep. I just pushed a rebased version of current git master. > > Jan > > -- Qingquan Lv School of Information Science & Engineering , Lanzhou University. mail: lvq...@gmail.com Do what you like, Enjoy your life. ___ Xenomai-core mailing list Xenomai-core@gna.org https://mail.gna.org/listinfo/xenomai-core
Re: [Xenomai-core] xenomai-core ftrace
On 2011-09-04 15:16, rainbow wrote: > 2011/9/4 Jan Kiszka > >> On 2011-09-04 14:21, rainbow wrote: >>> Is the ipipe patch the same as patch like >>> adeos-ipipe-2.6.37.6-x86-2.9-02.patch, >> >> Except that the trace branch is for 2.6.35, yes. More precisely it is >> now the same, I just pushed the latest version that includes two more >> backported ipipe fixes. >> >>> I know the latter is xenomai patch >>> and after I patch it, I can see "Real-time sub-system ---> " Option. But >> If >>> I use 2.6.35-x86-trace which contains ,there is no such option. >> >> That menu option is introduced by Xenomai, ie. after running >> prepare-kernel.sh. You likely forgot that step. >> > > >> Yes,I forget the step. So I think I only have to run prepare-kernel.sh >> --arch=x86_64 > > --linux=2.6.35-x86-trace , I do not need --adeos option because >> the 2.6.35-x86-trace contains the ipipe patch. >> > > > >> Note again that you have to use a Xenomai tree with the required ftrace >> patches on top if you want Xenomai to generate ftrace events as well. >> >> "Xenomai tree with required ftrace patches on top" you mean the branch > "remotes/origin/queues/ftrace"? Yep. I just pushed a rebased version of current git master. Jan signature.asc Description: OpenPGP digital signature ___ Xenomai-core mailing list Xenomai-core@gna.org https://mail.gna.org/listinfo/xenomai-core
Re: [Xenomai-core] xenomai-core ftrace
2011/9/4 Jan Kiszka > On 2011-09-04 14:21, rainbow wrote: > > Is the ipipe patch the same as patch like > > adeos-ipipe-2.6.37.6-x86-2.9-02.patch, > > Except that the trace branch is for 2.6.35, yes. More precisely it is > now the same, I just pushed the latest version that includes two more > backported ipipe fixes. > > > I know the latter is xenomai patch > > and after I patch it, I can see "Real-time sub-system ---> " Option. But > If > > I use 2.6.35-x86-trace which contains ,there is no such option. > > That menu option is introduced by Xenomai, ie. after running > prepare-kernel.sh. You likely forgot that step. > > Yes,I forget the step. So I think I only have to run prepare-kernel.sh > --arch=x86_64 --linux=2.6.35-x86-trace , I do not need --adeos option because > the 2.6.35-x86-trace contains the ipipe patch. > > Note again that you have to use a Xenomai tree with the required ftrace > patches on top if you want Xenomai to generate ftrace events as well. > > "Xenomai tree with required ftrace patches on top" you mean the branch "remotes/origin/queues/ftrace"? > > Another problem is that there are so many xenomai gits , how can i > download > > the correct git? > > By cloning the the git repository you obtain all available branches. You > just need to checkout the desired one afterward. > > > I am a newby to xenomai and I am sorry to ask so many questions but I > want > > to do something on xenomai :) . Thank you for your detail answers. > > Setting up ftrace for Xenomai is not necessarily a newbie task, but I > think I know the background of this. :) > I think you really know the background :). > > Jan > > -- Qingquan Lv School of Information Science & Engineering , Lanzhou University. mail: lvq...@gmail.com Do what you like, Enjoy your life. ___ Xenomai-core mailing list Xenomai-core@gna.org https://mail.gna.org/listinfo/xenomai-core
Re: [Xenomai-core] xenomai-core ftrace
On 2011-09-04 14:21, rainbow wrote: > Is the ipipe patch the same as patch like > adeos-ipipe-2.6.37.6-x86-2.9-02.patch, Except that the trace branch is for 2.6.35, yes. More precisely it is now the same, I just pushed the latest version that includes two more backported ipipe fixes. > I know the latter is xenomai patch > and after I patch it, I can see "Real-time sub-system ---> " Option. But If > I use 2.6.35-x86-trace which contains ,there is no such option. That menu option is introduced by Xenomai, ie. after running prepare-kernel.sh. You likely forgot that step. Note again that you have to use a Xenomai tree with the required ftrace patches on top if you want Xenomai to generate ftrace events as well. > Another problem is that there are so many xenomai gits , how can i download > the correct git? By cloning the the git repository you obtain all available branches. You just need to checkout the desired one afterward. > I am a newby to xenomai and I am sorry to ask so many questions but I want > to do something on xenomai :) . Thank you for your detail answers. Setting up ftrace for Xenomai is not necessarily a newbie task, but I think I know the background of this. :) Jan signature.asc Description: OpenPGP digital signature ___ Xenomai-core mailing list Xenomai-core@gna.org https://mail.gna.org/listinfo/xenomai-core
Re: [Xenomai-core] xenomai-core ftrace
Is the ipipe patch the same as patch like adeos-ipipe-2.6.37.6-x86-2.9-02.patch, I know the latter is xenomai patch and after I patch it, I can see "Real-time sub-system ---> " Option. But If I use 2.6.35-x86-trace which contains ,there is no such option. Another problem is that there are so many xenomai gits , how can i download the correct git? I am a newby to xenomai and I am sorry to ask so many questions but I want to do something on xenomai :) . Thank you for your detail answers. 2011/9/4 Jan Kiszka > On 2011-09-04 13:49, rainbow wrote: > > you mean I use remotes/origin/queues/2.6.37-x86 branch and use the ipipe > > patch for 2.6.37 then install them on x86_64, the ftrace can work?I will > > have a try, thank you! > > Use the 2.6.35-x86-trace, it already contains the ipipe patch, and build > it for x86-64. > > Jan > > -- Qingquan Lv School of Information Science & Engineering , Lanzhou University. mail: lvq...@gmail.com Do what you like, Enjoy your life. ___ Xenomai-core mailing list Xenomai-core@gna.org https://mail.gna.org/listinfo/xenomai-core
Re: [Xenomai-core] xenomai-core ftrace
On 2011-09-04 13:49, rainbow wrote: > you mean I use remotes/origin/queues/2.6.37-x86 branch and use the ipipe > patch for 2.6.37 then install them on x86_64, the ftrace can work?I will > have a try, thank you! Use the 2.6.35-x86-trace, it already contains the ipipe patch, and build it for x86-64. Jan signature.asc Description: OpenPGP digital signature ___ Xenomai-core mailing list Xenomai-core@gna.org https://mail.gna.org/listinfo/xenomai-core
Re: [Xenomai-core] xenomai-core ftrace
you mean I use remotes/origin/queues/2.6.37-x86 branch and use the ipipe patch for 2.6.37 then install them on x86_64, the ftrace can work?I will have a try, thank you! 2011/9/4 Jan Kiszka > On 2011-09-04 07:10, rainbow wrote: > > Sorry to reply so late, I did a test about install ftrace on xenomai. the > > following is my procedure: > > #git://git.xenomai.org/xenomai-jki.git queues/ftrace > > #git://git.kiszka.org/ipipe-2.6 queues/2.6.35-x86-trace > > #cd queues/ftrace > > #git checkout -b remotes/origin/queues/ftrace > > origin/queues/2.6.35-x86-trace //change to the ftrace xenomai branch > > #cd ../2.6.35-x86-trace > > #git checkout > > -b origin/queues/2.6.35-x86-trace origin/queues/2.6.35-x86-trace > > #cd ../ftrace > > #./scripts/prepare-kernel.sh --arch=i386 > > --adeos=ksrc/arch/x86/patches/adeos-ipipe-2.6.35.9-x86-2.8-04.patch > > --linux=../2.6.35-x86-trace/ > > #cd /2.6.35-x86-trace/ > > > > then I compile the kernel but I get the following error message: > > arch/x86/kernel/ipipe.c:851: error: conflicting types for > ‘update_vsyscall’ > > include/linux/clocksource.h:316: note: previous declaration of > > ‘update_vsyscall’ was here > > make[2]: *** [arch/x86/kernel/ipipe.o] Error 1 > > make[1]: *** [arch/x86/kernel] Error 2 > > make: *** [arch/x86] Error 2 > > That's a build issues of the underlying old ipipe patch. However, it's > x86-32 only. And as the documentation stated, only x86-64 is supported > by the ftrace patches. So build for 64 bit instead. > > Jan > > -- Qingquan Lv School of Information Science & Engineering , Lanzhou University. mail: lvq...@gmail.com Do what you like, Enjoy your life. ___ Xenomai-core mailing list Xenomai-core@gna.org https://mail.gna.org/listinfo/xenomai-core
Re: [Xenomai-core] xenomai-core ftrace
On 2011-09-04 07:10, rainbow wrote: > Sorry to reply so late, I did a test about install ftrace on xenomai. the > following is my procedure: > #git://git.xenomai.org/xenomai-jki.git queues/ftrace > #git://git.kiszka.org/ipipe-2.6 queues/2.6.35-x86-trace > #cd queues/ftrace > #git checkout -b remotes/origin/queues/ftrace > origin/queues/2.6.35-x86-trace //change to the ftrace xenomai branch > #cd ../2.6.35-x86-trace > #git checkout > -b origin/queues/2.6.35-x86-trace origin/queues/2.6.35-x86-trace > #cd ../ftrace > #./scripts/prepare-kernel.sh --arch=i386 > --adeos=ksrc/arch/x86/patches/adeos-ipipe-2.6.35.9-x86-2.8-04.patch > --linux=../2.6.35-x86-trace/ > #cd /2.6.35-x86-trace/ > > then I compile the kernel but I get the following error message: > arch/x86/kernel/ipipe.c:851: error: conflicting types for ‘update_vsyscall’ > include/linux/clocksource.h:316: note: previous declaration of > ‘update_vsyscall’ was here > make[2]: *** [arch/x86/kernel/ipipe.o] Error 1 > make[1]: *** [arch/x86/kernel] Error 2 > make: *** [arch/x86] Error 2 That's a build issues of the underlying old ipipe patch. However, it's x86-32 only. And as the documentation stated, only x86-64 is supported by the ftrace patches. So build for 64 bit instead. Jan signature.asc Description: OpenPGP digital signature ___ Xenomai-core mailing list Xenomai-core@gna.org https://mail.gna.org/listinfo/xenomai-core
