- l4-hackers - example.com Site

Codezero Microkernel v0.2 Released
by Bahadir Balban 07 Dec '09

07 Dec '09

I would like to announce that Codezero Microkernel v0.2 is released. On this release, the microkernel is now fully capability checked, and we introduced the notion of containers to provide isolated execution environments. Please see below for a brief description. 1.) Containers In Codezero containers provide the architectural infrastructure for isolation of execution environments. Each container is allocated with a set of address spaces, threads, and any other resource that would otherwise be globally available on the platform, such as virtual and physical memory. Using the simple notion of containers, it is possible to build any type of software design hierarchy. A hierarchical client/server design, or multi-threaded standalone applications are both possible scenarios. 2.) Capabilities Capabilities protect all resources maintained by the kernel. Currently, all system calls are protected by capabilities, except a few trivial ones that have been left out. Physical and virtual memory, typed memory pools, and inter-process communication are among other resources that are protected by capability checking. Capabilities build upon the foundation of containers, providing a fine-grained security architecture, inside and among container boundaries. We also introduced a capability control system call, by which the capabilities may be shared, granted and modified in different ways, enabling a highly flexible and configurable security architecture. 3.) Configuration We attempted to present the above two notions in an easily manageable kernel configuration system. Containers, their parameters and capabilities may be adjusted easily at configuration time, using our CML2-based kernel configuration system. We are aiming to evolve the L4 API into the future by feedback, hence this email post. Codezero Project is open with a GPLv3 license. If you are interested to learn more, download by: git-clone git://git.l4dev.org/codezero.git A useful jump-start guide: http://www.l4dev.org/doku.php?id=getting_started_quick API reference man pages: man -M codezero/docs/man pagename Thanks, -- Bahadir Balban

1 0

Problem compiling Fiasco Kernel (kip.cc)
by olivier 02 Dec '09

02 Dec '09

Hello all I'm currently trying compil current Fiasco Kernel under Cygwin, unfortunatly I have a problem of compilation. when compiler try compil kip.cc I have an assembler message that said: Error: junk at the end of line, first unrecognized character is ',' Any Idea? Thanks Olivier PS: my kip.cc // AUTOMATICALLY GENERATED -- DO NOT EDIT! -*- c++ -*- #include "kip.h" #include "kip_i.h" #line 47 "/tudos/kernel/fiasco/src/abi/kip.cpp" //============================================================================ #line 182 "/tudos/kernel/fiasco/src/abi/kip.cpp" //---------------------------------------------------------------------------- #line 188 "/tudos/kernel/fiasco/src/abi/kip.cpp" Kip *Kip::global_kip; #line 192 "/tudos/kernel/fiasco/src/abi/kip.cpp" asm(".section .initkip.version, \"a\", %progbits \n" \ ".string \"" CONFIG_KERNEL_VERSION_STRING "\" \n" \ ".previous \n"); #line 196 "/tudos/kernel/fiasco/src/abi/kip.cpp" asm(".section .initkip.features.fini, \"a\", %progbits \n" \ ".string \"\" \n" \ ".previous \n"); #line 110 "/tudos/kernel/fiasco/src/abi/kip.cpp" bool Kip::add_mem_region(Mem_desc const &md) { Mem_desc *m = mem_descs(); Mem_desc *end = m + num_mem_descs(); for (;m<end;++m) { if (m->type() == Mem_desc::Undefined) { *m = md; return true; } } // Add mem region failed -- must be a Fiasco startup problem. Bail out. assert (0); return false; } #line 130 "/tudos/kernel/fiasco/src/abi/kip.cpp" Mem_region Kip::last_free() const { Mem_desc const *m = mem_descs(); Mem_desc const *const end = m + num_mem_descs(); Mem_region r; r.start = 0; r.end = 0; for (;m<end;++m) { Address s = m->start(); Address e = m->end(); // Speep out stupid descriptors (that have the end before the start) if (s>=e) { const_cast<Mem_desc*>(m)->type(Mem_desc::Undefined); continue; } if (m->is_virtual()) // skip virtual memory descriptors continue; switch (m->type()) { case Mem_desc::Conventional: if (e>r.end) r.end = e; if (s>r.start) r.start = s; break; case Mem_desc::Reserved: case Mem_desc::Dedicated: case Mem_desc::Shared: case Mem_desc::Arch: case Mem_desc::Bootloader: if (e>=r.start && e<r.end) { r.start = e + 1; } if (s>=r.start && s<r.end) { r.end = s - 1; } break; default: break; } } return r; }

2 7

ddekit and dde linux2.6
by Da Zheng 22 Nov '09

22 Nov '09

Hi, I'm trying to understand ddekit and hopefully to port it to Hurd. It seems that ddekit is still under active development. What is its current development status? I read http://demo.tudos.org/dsweeper_tutorial.html, which said that new features such as hotplugging and power management would be added ddekit but it was in 2006. Have those features been added to ddekit? Is it possible for me to move the Linux USB driver on the top of dde without modification? What is the status of dde linux2.6 (I mean the one in the directory l4/pkg/dde_linux26)? Is it still under development? Does it support the features I mentioned above? Thank you, Zheng Da

3 4

The errors i tried to map iomem to virtual memory
by Guanghui, Cheng 06 Nov '09

06 Nov '09

Hello: I tried to map the hpet iomem to the virtual memory but i got some error. The log is as following: vtimer | rmgr_pager 4:0 vtimer | hpet_address 0xfed00000 vtimer | hpet size 0x400000 vtimer | hpet_virt_address 0x400000 ROOT: Cannot map page at fed00000 log2_size=12 failed vtimer | IOMem mapping error : No fpage received vtimer | __handle_pf(): L4RM: page fault: no entry in region list vtimer | L4RM: [PF] read at 0x00400000, ip 0100024e, src 8.02 It seems that when I map the iomem the pagesize is not permitted but superpagesize is ok. But i still get the error as "No fpage received". Does anybody tell me what the problem is? Thanks. Cheng Guanghui

3 6

the preempter of one thread
by Guanghui, Cheng 29 Oct '09

29 Oct '09

Hi: Thread preempter is functional or ignored in the current fiasco. i read the lectures about microkernel-based operating systems and there are somethings about thread preempter. Thanks. Cheng Guanghui

2 1

Some Errors in DDE
by Jingyi WANG 29 Oct '09

29 Oct '09

hi, I'm porting a sound card(ens1370)to DDE, but found some errors in the function of kobj_map whic is in map.c(l4/pkg/dde/linux26/contrib.drivers/base/map.c) What's more, I check the ELF format of this sound card.The error is in the address of 821607. The related messages show as follows: /home/wangjingyi/l4/tudos/l4/pkg/dde/linux26/contrib/drivers/base/map.c:58 mutex_lock(domain->lock); 821603: 8b 55 08 mov 0x8(%ebp),%edx 821606: 58 pop %eax 821607: 8b 82 fc 03 00 00 mov 0x3fc(%edx),%eax 82160d: 50 push %eax 82160e: e8 cd 65 02 00 call 847be0 <mutex_lock> I was wondering what caused this error and how to fix it. Thanks!

2 1

ex_regs system call is forzed in the do_ipc process
by Guanghui, Cheng 23 Oct '09

23 Oct '09

Hello: When i use the ex_regs system call to trigger the exception ipc it seems to be frozed in the do_ipc stange. I use jdb to debug this current thread lists is like this: 9.04 l4ertl.exceptio 10 9.03 rcv,ipc_progr 9.03 l4ertl.timer0 10 9.02 rcv,ipc_progr 9.02 domain2.main 10 9.04 rcv,ipc_progr,exc_progr l4ertl.exceptio is the pager of domain2.main. And now l4ertl.timer0 is executing ex_regs system to trigger exception for domain2.main. l4ertl.exceptio is waiting for the exception ipc from the l4ertl2.main2. In detail l4ertl.exceptio is in ipc (user level registers). l4ertl.timer0 is in ipc (user level registers), too. domain2.main is in the exception 255. It seems to be dead lock in the kernel. Very strange. Thanks. Cheng Guanghui

2 5

About some unimplement functions in DDE
by Jingyi WANG 20 Oct '09

20 Oct '09

Hi~When I run a device driver on DDE(pkg/dde/linux26/example), the result shows up that pci_set_master() and pci_disable_device is unimplement. Could you give me some advice on how to make these functions work?

3 2

Re: About the exception ipc reply
by Guanghui, Cheng 16 Oct '09

16 Oct '09

On Wednesday 14 October 2009 06:52:10 you wrote: > On Tue Oct 13, 2009 at 13:01:46 +0800, Guanghui, Cheng wrote: > > On Monday 12 October 2009 02:03:41 Adam Lackorzynski wrote: > > > On Sun Oct 11, 2009 at 22:17:49 +0800, Guanghui, Cheng wrote: > > > > From the l4-x2 manual it is said the reply from the exception > > > > handler contains a label, an instruction pointer where the faulting > > > > thread is resumed. I want to know whether it is implemented in the > > > > Fiasco. I try to do this. Modify the utcb before send ipc resume the > > > > exception thread but it seems no any effect about the instruction > > > > pointer and stack pointer of resumed exception thread. > > > > > > My guess would be that you did not set the number of words to send in > > > the reply. Set L4_UTCB_EXCEPTION_REGS_SIZE in the msgtag-words field of > > > the reply. > > > > Hello Adam: > > Now i use L4_UTCB_EXCEPTION_REGS_SIZE and i could fix the thread with > > esp and eip by exception handler UTCB. And the thread could start with > > new instruction pointer and new stack pointer. But it still has some > > problem when the thread quit from new function. So i want to know how an > > thread is resumed by exception reply. I mean which part of code in kernel > > could finish the thread wakeup. I read the receive.c but i don't find it. > > The function copy_utcb_to_ts copies the state from the utcb of the > exception handler over the state of the thread. The thread then resumes > with this new state. I think what you have to do is to e.g. prepare the > stack of the thread in a way that when the new function's ret is > called it resumes at the position it was intercepted. Is this possible? Hello, Adam: Now the demo could work according to your design. And this demo is so simple only to emulate the situation we talked about before. I introduced a little about this demo: 3 threads: timer_thread, exception_thread, main_thread main_thread emulates the behaviour of system which is a endless loop to output. the function body is thread_func1. timer_thread emulates the behaviour of timer thread which could trigger the exception periodically. exception_thread emulates the behaviour of handling interrupt. The function body is exception_handler. When the timer_thread modify the status of main_thread with flag L4_THREAD_EX_REGS_RAISE_EXCEPTION. The main thread will be suspend and the exception_thread could get the exception ipc from main_thread. Exception_thread will modify the ESP and EIP in the utcb and then reply to main thread. The main thread will resume to the function about handling interrupt. When the handling interrupt function is over. The main thread could go back to the status before the exception happens. The output: count 49 ... count 58 id: 8:1, 12 0xeacff011 15 0x100711c do irq 0 ... do irq 9 l4_sleep(): IPC error 00 count 59 ... count 67 id: 8:1, 12 0xeacff011 15 0x100711c The output between "count ..." is execution of main thread. The output between "do_irq ..." is execution of exception thread which emulates the interrupt handling. BUT. I have a problem about my code when i fixing the stack of main thread. The correct code which could work well is like this: utcb = l4_utcb_get(); eip = utcb->exc.eip; esp = utcb->exc.esp; utcb->values[12] = (l4_umword_t)(do_irq); esp_loc = 1024 - (esp - (l4_umword_t)stack)/4; stack[esp_loc - 1] = eip; l4_msgtag ... l4_ipc_send_tag In the code above i only reset the next stack with return address (old eip). But it seems i can't reset the new stack pointer like utcb->values[15] = esp - 4 In my opinion it should do but if i did it can't work. It seems some tricky here. Can you tell me why it is like this? Additinally, i tried this way about handling interrupt with interrupt number like this: void do_irq(int irq) it can't work either. Thanks. Cheng Guanghui

2 2

Split console with two keyboards
by Shakthi Kannan 16 Oct '09

16 Oct '09

Hi, I would like to know if it is possible in any of the L4* systems to have a setup like the following: * The console (framebuffer) to be split into two frames/windows, say top and bottom halves, but, each one should be used/accessed independently of each other. * With two keyboards connected to this single system, one should be able to use (shell) one of the keyboards with the top window, while the other should use the bottom one. Appreciate any thoughts/inputs in this regard. Thanks! SK -- Shakthi Kannan http://www.shakthimaan.com

2 1