April 2015 - l4-hackers - example.com Site

Re: How L4Linux Linked the header file?
by Youren Shen 28 Apr '15

28 Apr '15

Hi, Adam, Sorry to disturb you again. I find the reason of this problem is because the "config GENERIC_CLOCKEVENTS" is removed from file arch/arm/Kconfig after Kernel 3.4. As a result, the GENERIC_CLOCKEVENTS is not defined in the arch/l4/kconfig.arm. And the CONFIG_SMP depends on GENERIC_CLOCKEVENTS. So the CONFIG_GENERIC_CLOCKEVENTS and CONFIG_SMP will be unmask in build processes. Is there any way to get previous version of L4Linux? For instance, If I can get the source code of the L4Linux 3.4, it will be very helpful. Thank you very much for your help! On Sun, Apr 26, 2015 at 12:18 AM, Youren Shen <shenyouren(a)gmail.com> wrote: > Hi, Adam > I'm not so sure how to reply the mail in L4-hackers-list, So I CC to both > the List mail address and thread mail address. > > Thank you for your reply, and that really helps. > > I find that those error occurred because the CONFIG_SMP and > CONFIG_GENERIC_CLOCKEVENTS_BUILD is not set in .config. > > I try to config them by 'make menuconfig' but there is none entry about > CONFIG_SMP or CONFIG_GENERIC_CLOCKEVENTS_BUILD appeared in menuconfig. So > I change the .config file directly, but once I invoke "make", the .config > will be rewrite. > > Would you mind give me any guide about how to set them? > > Thank you very much. > >> >> >> Hi, >> >> On Sat Apr 18, 2015 at 22:26:15 +0800, Youren Shen wrote: >> > I'm trying to port L4Linux 3.14 to Linux Kernel 3.4. But when I complied >> > the kernel, this error happened: >> > >> /home/shenyouren/workspace/kernel/kernel_exynos5250/arch/l4/kernel/main.c: >> > In function 'cpu0_startup': >> > >> /home/shenyouren/workspace/kernel/kernel_exynos5250/arch/l4/kernel/main.c:2124:2: >> > error: implicit declaration of function 'set_my_cpu_offset' >> > [-Werror=implicit-function-declaration] >> > >> > I checked main.c file: >> > >> > #include <asm/unistd.h> >> > #include <asm/percpu.h> >> > #include <asm/generic/l4lib.h> >> > >> > So I add one percpu.h file with definition of 'set_my_cpu_offset' in >> > >> /home/shenyouren/workspace/kernel/kernel_exynos5250/arch/l4/include/asm/arch-arm/, >> > however this error still happened. >> > >> > Then I add the definition of this function to >> > >> /home/shenyouren/workspace/kernel/kernel_exynos5250/include/linux/percpu.h, >> > then the error message will not show. >> > >> > Also, discard the change in $(src)/include/linux/percpu.h, then I change >> > the main.c file to include absolute path of percpu.h. >> > >> > #include <asm/unistd.h> >> > #include >> > >> </home/shenyouren/workspace/kernel/kernel_exynos5250/arch/l4/include/asm/arch-arm/percpu.h> >> > #include <asm/generic/l4lib.h> >> > >> > It passed the complied to. >> >> When you put a header file in arch/l4/include/asm/arch-arm/ including it >> via <asm/foo.h> should work. >> >> > So that is say, the #include <asm/percpu.h> is reference to >> > src/include/linux/percpu.h. That really strange. >> >> So, include <linux/percpu.h> in main.c right away? >> >> The L4 part of L4Linux you're looking at is for 3.14 and you apply it to >> Linux 3.4, please expect that things are different and need adaption. >> >> > I do not change the Makefile in arch/l4, and I really confused about >> this >> > error. >> > Now this problem occurs to me again, when complied the >> > arch/l4/kernel/timer.c file, this error happened: >> > >> > >> /home/shenyouren/workspace/kernel/kernel_exynos5250/arch/l4/kernel/timer.c:153:35: >> > warning: 'struct clock_event_device' declared inside parameter list >> > [enabled by default] >> > >> /home/shenyouren/workspace/kernel/kernel_exynos5250/arch/l4/kernel/timer.c:153:35: >> > warning: its scope is only this definition or declaration, which is >> > probably not what you want [enabled by default] >> > >> > but the definition of this to file should be defined in clockchips.h >> which >> > is include in timer.c: >> > >> > #include <linux/timex.h> >> > #include <linux/clockchips.h> >> > #include <linux/irq.h> >> > >> > Thank you for your reading, I just want to know what's the rule of >> L4Linux >> > header file linking, and solve this problem. >> > I'd be so appreciated if anyone can give me some help! >> >> There's a #ifdef CONFIG_GENERIC_CLOCKEVENTS_BUILD in clockchips.h. >> Not defined? >> >> >> >> Adam >> -- >> Adam adam(a)os.inf.tu-dresden.de >> Lackorzynski http://os.inf.tu-dresden.de/~adam/ >> >> -- > Best Regards. > Youren Shen. > -- Best Regards. Youren Shen.

2 1

Re: How L4Linux Linked the header file?
by Youren Shen 25 Apr '15

25 Apr '15

Hi, Adam I'm not so sure how to reply the mail in L4-hackers-list, So I CC to both the List mail address and thread mail address. Thank you for your reply, and that really helps. I find that those error occurred because the CONFIG_SMP and CONFIG_GENERIC_CLOCKEVENTS_BUILD is not set in .config. I try to config them by 'make menuconfig' but there is none entry about CONFIG_SMP or CONFIG_GENERIC_CLOCKEVENTS_BUILD appeared in menuconfig. So I change the .config file directly, but once I invoke "make", the .config will be rewrite. Would you mind give me any guide about how to set them? Thank you very much. > > > Hi, > > On Sat Apr 18, 2015 at 22:26:15 +0800, Youren Shen wrote: > > I'm trying to port L4Linux 3.14 to Linux Kernel 3.4. But when I complied > > the kernel, this error happened: > > > /home/shenyouren/workspace/kernel/kernel_exynos5250/arch/l4/kernel/main.c: > > In function 'cpu0_startup': > > > /home/shenyouren/workspace/kernel/kernel_exynos5250/arch/l4/kernel/main.c:2124:2: > > error: implicit declaration of function 'set_my_cpu_offset' > > [-Werror=implicit-function-declaration] > > > > I checked main.c file: > > > > #include <asm/unistd.h> > > #include <asm/percpu.h> > > #include <asm/generic/l4lib.h> > > > > So I add one percpu.h file with definition of 'set_my_cpu_offset' in > > > /home/shenyouren/workspace/kernel/kernel_exynos5250/arch/l4/include/asm/arch-arm/, > > however this error still happened. > > > > Then I add the definition of this function to > > > /home/shenyouren/workspace/kernel/kernel_exynos5250/include/linux/percpu.h, > > then the error message will not show. > > > > Also, discard the change in $(src)/include/linux/percpu.h, then I change > > the main.c file to include absolute path of percpu.h. > > > > #include <asm/unistd.h> > > #include > > > </home/shenyouren/workspace/kernel/kernel_exynos5250/arch/l4/include/asm/arch-arm/percpu.h> > > #include <asm/generic/l4lib.h> > > > > It passed the complied to. > > When you put a header file in arch/l4/include/asm/arch-arm/ including it > via <asm/foo.h> should work. > > > So that is say, the #include <asm/percpu.h> is reference to > > src/include/linux/percpu.h. That really strange. > > So, include <linux/percpu.h> in main.c right away? > > The L4 part of L4Linux you're looking at is for 3.14 and you apply it to > Linux 3.4, please expect that things are different and need adaption. > > > I do not change the Makefile in arch/l4, and I really confused about this > > error. > > Now this problem occurs to me again, when complied the > > arch/l4/kernel/timer.c file, this error happened: > > > > > /home/shenyouren/workspace/kernel/kernel_exynos5250/arch/l4/kernel/timer.c:153:35: > > warning: 'struct clock_event_device' declared inside parameter list > > [enabled by default] > > > /home/shenyouren/workspace/kernel/kernel_exynos5250/arch/l4/kernel/timer.c:153:35: > > warning: its scope is only this definition or declaration, which is > > probably not what you want [enabled by default] > > > > but the definition of this to file should be defined in clockchips.h > which > > is include in timer.c: > > > > #include <linux/timex.h> > > #include <linux/clockchips.h> > > #include <linux/irq.h> > > > > Thank you for your reading, I just want to know what's the rule of > L4Linux > > header file linking, and solve this problem. > > I'd be so appreciated if anyone can give me some help! > > There's a #ifdef CONFIG_GENERIC_CLOCKEVENTS_BUILD in clockchips.h. > Not defined? > > > > Adam > -- > Adam adam(a)os.inf.tu-dresden.de > Lackorzynski http://os.inf.tu-dresden.de/~adam/ > > -- Best Regards. Youren Shen.

1 0

(no subject)
by deng.chao1＠zte.com.cn 24 Apr '15

24 Apr '15

Hi: I am reading the code of fiasco kernel.I have a question about the function "Context::schedule". At line 894 in kernel/fiasco/src/kern/context.cpp： "while (EXPECT_FALSE(current_cpu != access_once(&_home_cpu)))" As I know, the variable "_home_cpu" indicates the CPU number which the thread that invokes the “schedue ” as a member function is running on。And the variable “current cpu” indicates the CPU number now this code fragment is running on。 The condition test tells me that it seems the class Context's member function "schedule" will run on a different cpu some time . If it does so, some extra work will need to be done in the "schedule" function. I have searched all of the fiasco kernel sources, but I did not find this special context. So would anybody please tell me whether there has a situation that the "schedule" function will run on different CPU， why does it happen？ Thanks！

2 1

where is the call_bootstrap?
by 水镜 24 Apr '15

24 Apr '15

Hi, in the file main-ia32-32.cpp, there's a line(line 60): call call_bootstrap where could i find the implemention of the call_bootstrap?

2 1

Static_object in fiasco kernel
by 水镜 23 Apr '15

23 Apr '15

hi, what is the Static_object in fiasco kernel used for?

2 1

How L4Linux Linked the header file?
by Youren Shen 23 Apr '15

23 Apr '15

Hi, I'm trying to port L4Linux 3.14 to Linux Kernel 3.4. But when I complied the kernel, this error happened: /home/shenyouren/workspace/kernel/kernel_exynos5250/arch/l4/kernel/main.c: In function 'cpu0_startup': /home/shenyouren/workspace/kernel/kernel_exynos5250/arch/l4/kernel/main.c:2124:2: error: implicit declaration of function 'set_my_cpu_offset' [-Werror=implicit-function-declaration] I checked main.c file: #include <asm/unistd.h> #include <asm/percpu.h> #include <asm/generic/l4lib.h> So I add one percpu.h file with definition of 'set_my_cpu_offset' in /home/shenyouren/workspace/kernel/kernel_exynos5250/arch/l4/include/asm/arch-arm/, however this error still happened. Then I add the definition of this function to /home/shenyouren/workspace/kernel/kernel_exynos5250/include/linux/percpu.h, then the error message will not show. Also, discard the change in $(src)/include/linux/percpu.h, then I change the main.c file to include absolute path of percpu.h. #include <asm/unistd.h> #include </home/shenyouren/workspace/kernel/kernel_exynos5250/arch/l4/include/asm/arch-arm/percpu.h> #include <asm/generic/l4lib.h> It passed the complied to. So that is say, the #include <asm/percpu.h> is reference to src/include/linux/percpu.h. That really strange. I do not change the Makefile in arch/l4, and I really confused about this error. Now this problem occurs to me again, when complied the arch/l4/kernel/timer.c file, this error happened: /home/shenyouren/workspace/kernel/kernel_exynos5250/arch/l4/kernel/timer.c:153:35: warning: 'struct clock_event_device' declared inside parameter list [enabled by default] /home/shenyouren/workspace/kernel/kernel_exynos5250/arch/l4/kernel/timer.c:153:35: warning: its scope is only this definition or declaration, which is probably not what you want [enabled by default] but the definition of this to file should be defined in clockchips.h which is include in timer.c: #include <linux/timex.h> #include <linux/clockchips.h> #include <linux/irq.h> Thank you for your reading, I just want to know what's the rule of L4Linux header file linking, and solve this problem. I'd be so appreciated if anyone can give me some help! -- Best Regards. Youren Shen.

2 1

How to compile the fiasco kernel test directory?
by Liu Xiaodong 23 Apr '15

23 Apr '15

Hi,I got a tar ball(l4re-snapshot-2014092821.tar.bz2) from fiasco website. I see a directory for test under the fiasco kernel source path: /l4re-snapshot-2014092821/src/kernel/fiasco/src/test/. But I can't compile them in the normal way, such as that you discrbed in the website http://os.inf.tu-dresden.de/fiasco/build.html. I really want to do some kernel tests on fiaso. If you can tell me how to compile the fiasco kernel test directory, it will be very helpful, and I will appreciate it. By the way, the test source code seems to not be included completely. Such as /l4re-snapshot-2014092821/src/kernel/fiasco/src/test/space/space.t.cc #include <iostream> #include <iomanip> #include <cassert> using namespace std; #include <flux/page.h> #include "space.h" int main() { // // Make task 4 the chief of task 5 // assert (space_index_t (5).lookup () == 0); assert (space_index_t (5).chief () == 0); assert (space_index_t (5).set_chief (space_index_t(0), space_index_t(4))); assert (space_index_t (5).lookup () == 0); assert (space_index_t (5).chief () == 4); ...... } I can't find headfile "space.h" in the tar ball, and there is no define about "space_index_t" too. can you tell me why? thanks again! -------------------------------------------------------- ZTE Information Security Notice: The information contained in this mail (and any attachment transmitted herewith) is privileged and confidential and is intended for the exclusive use of the addressee(s). If you are not an intended recipient, any disclosure, reproduction, distribution or other dissemination or use of the information contained is strictly prohibited. If you have received this mail in error, please delete it and notify us immediately.

2 3

How to do quickly in order to starting fiasco with a console shell?
by zhou.li9＠zte.com.cn 23 Apr '15

23 Apr '15

How to do quickly in order to starting fiasco with a console shell? After copying src/l4/conf/examples/x86-fb.list to src/l4/conf/modules.list,I use QEMU to boot,the boot process appears to be normal: ....... fbdrv | Starting server loop mag | mapped frame buffer at 0x200000 mag | View::Info: mag | flags: 0 mag | size: 1280x1024 pos: 0, 0 mag | bytes_per_line: 2560 mag | buffer_offset: 0 mag | RGBA(2): 5(11):6(5):5(0):0(0) mag | memory 200000-600000 mag | Plugin: Mag_client service started mag | Plugin: Frame-buffer service started mag | L4INPUT native mode activated mag | L4INPUT: !!! W A R N I N G !!! mag | L4INPUT: Please, do not use Fiasco's "-esc" with L4INPUT. mag | L4INPUT: !!! W A R N I N G !!! mag | serio: i8042 AUX port at 0x60,0x64 irq 12 mag | serio: i8042 KBD port at 0x60,0x64 irq 1 mag | input: ImExPS/2 Generic Explorer Mouse on isa0060/serio1 mag | input: AT Translated Set 2 keyboard on isa0060/serio0 mag | connect "ImExPS/2 Generic Explorer Mouse", isa0060/serio1/input0 mag | connect "AT Translated Set 2 keyboard", isa0060/serio0/input0 spectrum| x:640 y:480 bit/pixel:16 bytes/line:1280 But How can I input some shell command? -------------------------------------------------------- ZTE Information Security Notice: The information contained in this mail (and any attachment transmitted herewith) is privileged and confidential and is intended for the exclusive use of the addressee(s). If you are not an intended recipient, any disclosure, reproduction, distribution or other dissemination or use of the information contained is strictly prohibited. If you have received this mail in error, please delete it and notify us immediately.

3 4

Re: Using a second UART to control a serial device
by Pflaum, Clemens 20 Apr '15

20 Apr '15

Thank you for your fast response, I've adapted your code to my needs (using the uart_pxa driver in drivers-frst). It compiles and starts up fine on the BananaPi but sadly I'm not getting any response on the uart3 pins... It seems to have a problem in the l4\pkg\drivers-frst\uart\src\uart_pxa.cc when calling the Uart_16550::startup(regs). I get a few wierd boxlike characters on the console and then "failed to startup uart regs". This is my init() : #define IRQ_NUM 86 #define UART_BASE 0x01C28C00 . . . bool Maestro_server::init() { l4_addr_t virt_base = 0; if (l4io_request_iomem((l4_addr_t)UART_BASE, 0x1000, L4IO_MEM_NONCACHED, &virt_base)) { printf("maestro-drv: request io-memory from l4io failed.\n"); return false; } printf("maestro-drv: virtual base at:%lx\n", virt_base); L4::Io_register_block_mmio *regs = new L4::Io_register_block_mmio(virt_base); _uart = new (malloc(sizeof(L4::Uart_16550))) L4::Uart_16550((unsigned long) 115200); if(!(_uart->startup(regs))){ printf("failed to startup uart regs!"); } if(!(_uart->change_mode(0x00 | 0x03 | 0x00, 115200))){ printf("failed to change uart mode!"); } the rest of it is equal to the serial-drv example. Any idea what i couldve done wrong? regard, Clemens

1 0

Using multiple NICs within one application
by Stark, Josef 19 Apr '15

19 Apr '15

Hello, is it possible to use more than one network card in one L4Re-application and how would I do that? I would guess from the example lwip lua-script that I had to create a separate shm-area and/or communication channel (for ankh-sessions) for each device that my app wants to access, but I don't know how I would supply these additional channels to ankh and if this would be enough to enable multi-NIC networking. Any help would be appreciated. Regards, Josef

1 0