gmane.comp.micro-kernel.l4.devel

Using pthread on L4/Fiasco

석현철 — 2012-05-23T09:13:00

Thank you.

 

I made a stupid mistake.

 

When I added “REQUIRES_LIBS = libpthread” into Makefile, I modified three
Makefiles.

There are hello/Makefile, hello/server/Makefile, and
hello/server/src/Makefile.

 

I tested one by one.

But I found I made a mistake.

At last try, I wrote REQUIRES = libpthread instead of REQUIRES_LIBS =
libpthread on hello/server/src/Makefile.

 

After correcting my mistake, I can test pthread application.

 

Thank you! Marcus

 

Hyunchul Seok.

 

_______________________________________________
l4-hackers mailing list
l4-hackers< at >os.inf.tu-dresden.de
http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers

Using pthread on L4/Fiasco

석현철 — 2012-05-23T07:01:41

Hi. Hackers

 

I’m trying to use pthread in an application which runs on L4.

I modified “main.c” in Hello application, including “#include
<pthread.h>”.

And when I compiled L4Re, I got error messages:

 

 

main.o: In function `main':

/root/l4re-core-2011081207/src/l4/pkg/hello/server/src/main.c:39: undefined
reference to `pthread_create'

/root/l4re-core-2011081207/src/l4/pkg/hello/server/src/main.c:44: undefined
reference to `pthread_join'

make[5]: *** [hello] Error 1

 

 

I think this is because it cannot fine pthread.h header file. But I don’t
know how to fix it.

 

When I looked up previous lists, I could find one thread related to pthread
in 2011 list.

(the thread title is “Silly Pthread Issues”)

I think that it is the same problem, but the reply is only one. Said “Add
REQUIRES_LIBS = libpthread to the Makefile.”

Actually, I tried it, but I couldn’t solve the problem.

 

How can I use the pthread? Please, Help me!!

 

Thank you!

Hyunchul Seok

 

 

 

The modified

[l4ankh] Problems with fixed l4ankh

Timur — 2012-05-22T17:16:39

Hi!
I had fixed the l4ankh driver and after that it started to work properly. Now 
only thread is used to receive packets. In lines 158-162 we clear the rcv 
buffer: that is necessary to be done as after opening a session we start to 
receive packets that should not be served; otherwise the response time will be 
quite slow. This is not the best solution, but I do not have time to make it 
better.
Now I face the following problem: the driver in ankh (I use 8139cp) stops 
receiving packets after some time (for me it is usually 3-4 minutes). This 
situation occurs when  the interrupt handler was called and the device 
register IntrStatus already equals "zero". An interrupt doesn't work after 
that.

Booting L4/Fiasco + L4Re on PC

석현철 — 2012-05-16T05:59:54

Hello.

 

I’ve tried to boot L4/Fiasco on PC.

 

I followed the directions for building from both “http://os.inf.tu-dresden.
de/fiasco/build.html” and “http://os.inf.tu-dresden.de/L4Re/build.html”

And I could run L4/Fiasco on QEMU.

 

Now I hope I want to boot L4 on PC environment.

As I searched, it can be done through GRUB. (But, I am not convinced that
it is right way.)

Anyway, I’ve tried to boot L4 by using GRUB.

 

I use Ubuntu Linux for compiling L4/Fiasco and L4Re. In this, there is
GRUBv2.

 

I made the bootable ISO image.

(It is done by “make grub2iso E=hello MODULE_SEARCH_PATH={mypath}”)

 

And then, what should I do in order to boot L4 on PC?

 

How should I configure the GRUB configuration?

 

I really want to know how to boot L4 on PC. Please, help me!

 

 

Kind Regards,

Hyunchul Seok.

 

 

_______________________________________________
l4-hackers mailing list
l4-hackers< at >os.inf.tu-dresden.de
http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers

[Announcement] Karma VMM first public release

Matthias Lange — 2012-05-14T09:44:34

We are happy to announce the first public release of the Karma Virtual
Machine Monitor [0].

Karma is a virtual machine monitor (VMM) that runs Linux in a virtual
machine on top of the Fiasco.OC [1] microkernel. Its main design
directives are speed and simplicity. Unlike KVM, VirtualBox or VMWare,
Karma does no emulation, but resorts to aggressive paravirtualization
and therefore has low complexity and shows superior performance for a
number of benchmarks.

Karma requires hardware assisted CPU virtualization. A feature that is
available on all recent x86 CPUs (SVM or VT). Optionally, it can make
use of hardware assisted memory virtualization (Nested Paging or ePT),
if available.

The Karma VMM is currently being used as a research vehicle at
Technische Universität Berlin and Technische Universität Dresden.

It main features are:
- Trustworthy isolation of virtual machines by means of the microkernel.
  VMM compromise does no harm to other virtual machines as one instance
  of Karma runs exactly one virtual

Fiasco.OC on Cortex-A9

Johan Dams — 2012-05-11T14:01:29

Hi all,

I'm wondering if anyone has come across an issue with Fiasco.OC on
Cortex-A9 based systems. The problem is that I do not get past this
instruction (and with that I mean that the system just locks up): 

"mcr p15, 0, %[control], c1, c0 \n" // control

in src/kern/arm/bootstrap.cpp. The exact same code works fine on a
Cortex-A8 based processor. Changing cache on or off (in the control
variable) does not change anything. Also, just reading the current
content of the register and writing it back locks the system.

I have been going over compiler flags, tried different compilers
altogether (using 4.5.3-r1 right now), and looked if something odd was
going on with the generated assembly code, etc. with no results.

This code is a standard ARM instruction, and comes well before any
paging or even the actual kernel starts.

The SOC in question is a Freescale i.MX6 Quad core Cortex A9, which I
realize not many have actually used yet. However, if similar issues
presented itself on other platforms, these might

understanding l4re

Ryan Brown — 2012-05-11T01:15:01

Hi. I'm exploring developing software that runs on Fiasco.OC/L4re, so I'm
trying to understand how the various pieces fit together.  If I'm following
the makefiles correctly it looks like some uclibc files (like libc/inet)
are getting compiled, but they seem to be making linux system calls. I also
see the libc_backends code, and I'm not sure how this fits in. It looks
like these are mostly stubs, is it expected that you'll link the final
binary with the real implementation you want?

I also took a look at libpthreads, and I don't see much l4 specific code.
It looks like mutexes are implemented as spinlocks? Isn't there a better
way to do synchronization in fiasco?
_______________________________________________
l4-hackers mailing list
l4-hackers< at >os.inf.tu-dresden.de
http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers

[ankh+l4linux] Doesn't work

Timur — 2012-04-28T19:14:01

Hi, 
after 
ifconfig eth0 up 
l4linux crashes with errors: 

--------------------------
l4lx_irq_dev_startup: creating IRQ thread for 66 (IRQ-cap 42d000)
l4lx_irq_dev_startup: creating IRQ thread for 66 (IRQ-cap 42d000)
l4linux | l4lx_thread_create: Created thread 433 (IRQ66) (u:b3000e00,
sp:006c9ff4)
l4linux | irq_thread: Started IRQ thread for IRQ 66
l4linux | wait_for_irq_message: IRQ 66 (42d) receive failed, error = 0x4
------------------------

l4_is_invalid_cap(p->irq_cap) return false in wait_for_irq_message, 
but l4_irq_wait_u(p->irq_cap, &src_id, L4_IPC_NEVER, utcb) return 
L4_IPC_ENOT_EXISTENT.   How can this be?

Running Fiasco.OC in Bochs

Norman Feske — 2012-04-28T19:14:37

Hello,

for tracing/profiling purposes, I'd like to run Genode on Fiasco.OC in
Bochs. My prior attempts with the OKL4 and Pistachio kernels went fine.
However, when booting the setup with Fiasco.OC, I get the following
kernel message right at the start:

  Freeing init code/data: 28672 bytes (7 pages)

  DOUBLE FAULT!
  EAX=ec7ff000  ESI=00000000  DS=0023
  EBX=fcdcf000  EDI=fcdcf170  ES=0023
  ECX=ec7ff000  EBP=f0060100  GS=0043
  EDX=ec7ff000  ESP=fcdcffbc  SS=0010   ESP0=00000000
  EFL=00200246  EIP=f006592c  CS=0008
  Return reboots, "k" tries to enter the L4 kernel debugger...

Has anyone successfully used Fiasco.OC with Bochs before? If yes, I
would very much appreciate a known-good starting point for experimentation.

For reference, I am using the following kernel configuration:


https://raw.github.com/genodelabs/genode/master/base-foc/config/x86_32.kernel

My 'bochsrc' file looks as follows:

  display_library: x
  romimage: file=/usr/local/share/bochs/BIOS-bochs-latest
  megs: 128
  com1: enabled=1

Performance of l4_task_unmap call

Chen Tian — 2012-04-25T00:36:52

Hi,

I did a small test: a parent task first maps and then unmaps a page to its
child. Both parent and child task are running on the same core.

I found the execution is very slow and 99% time are spent on l4_task_unmap(
L4_FP_OTHER_SPACES flag is used).

After some investigation, I found the flag "need_xcpu_tlb_flush" in
map_util.cpp:766 is set to true. My guess is that this flag controls the
tlb of the cpu at which the child task is running. However, in my case,
both tasks are running on the same core, setting this flag can have huge
negative impact on performance.

I am thinking to put a check before this statement: if (current_cpu() !=
space's CPU) set the flag to true. Is this correct? If so, how to get
space's cpu?
space->cpu() ?

Thanks for the help.

Chen
_______________________________________________
l4-hackers mailing list
l4-hackers< at >os.inf.tu-dresden.de
http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers

Bootfs got overwritten

Haohui Mai — 2012-04-19T18:40:30

Hi,

I'm encountering a problem where the memory region of BOOTFS of L4Re got overwritten. Interestingly, the page is overwritten by things in the bootfs.

Here are the physical memory mapping set up by BOOTFS:

...
  BOOTFS: [2227000-23297b8] [C:506000] rtc
  BOOTFS: [232a000-26d5411] [C:507000] mag
  BOOTFS: [26d6000-2848a94] [C:508000] fb-drv
  BOOTFS: [129d000-129daa4] [C:509000] vandroid-x86.cfg
  BOOTFS: [126b000-126b3b7] [C:50a000] x86-legacy.devs
…

The page 0x2239000 (which belongs to rtc) is magically overwritten by the first page of x86-legacy.devs. I confirmed it with both JDB and QEMU monitor.

I'm running the newest snapshot of L4Re / L4Android on top of the UP version L4.Fiasco kernel.

What would be the best approach to debug the problem? is it there a way to mark the whole BOOTFS as read-only so that I can figure out what's going on?

Thanks!

~Haohui

Fiasco.OC development status

QiuYi — 2012-04-19T08:03:56

I am interested in the drivers of touchscreen, keypad and NANDflash on the beagleboard at the L4RE and L4linux.

qiuy.


_______________________________________________
l4-hackers mailing list
l4-hackers< at >os.inf.tu-dresden.de
http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers

l4_task_cap_equal broken?

Stefan kalkowski — 2012-04-18T13:01:21

Dear Fiasco.OC developers,

while working with Genode on top of Fiasco.OC, I've encountered the
following problem. When I transfer ipc-gates via ipc between tasks, it
comes to the point where a task receives a gate it already owns. These
duplicates are detected due to an additional identifier that is
transfered together with the gate. To detect fraud (whether somebody has
send an invalid gate/id combination) the received gate gets compared
with the locally available one via "l4_task_cap_equal". Now, the problem
is "l4_task_cap_equal" often fails even when both capabilities point to
the same ipc-gate. The following code-snippet demonstrates this issue:

...
tag = l4_task_cap_equal(L4_BASE_TASK_CAP, i->kcap(), rcv_cap);
if (!l4_msgtag_label(tag)) {
   unsigned long id1 = l4_debugger_global_id(i->kcap()),
                 id2 = l4_debugger_global_id(rcv_cap);
   printf("my_cap=%lx (id=%lx) rcv_cap=%lx (id=%lx)",
          i->kcap(), id1, rcv_cap, id2);
   if (id1 == id2)
     enter_kdebug("FAIL");
}
...

This s

Windows in QEMU on KVM-L4

Rolf Sommerhalder — 2012-04-18T09:44:30

Hi,

In their paper [1], the authors mention that they were able to run
32-bit versions of Windows XP and 7, among other guest OSes, in KVM-L4
on AMD x86 processors with AMD-V extensions.

Does anyone from the list happen to have an .iso around which boots on
such an AMD machine and demonstrates the performance of Windows (any
version will do) running in KVM-L4?
Alternatively, I would be grateful for any recipe how to adapt a demo CD
or Fisco.OC/L4Re build environment so that it allows to start a Windows
image in QEMU/KVM on L4.

So far, I have managed to install and to run Windows 7 Pro in a QEMU/KVM
image on my Linux host. As this image is over 4 GByte by itself, plus
QEMU with its dependencies, there is no way of just extending the
ramdisk image in order to load and run it in L4Linux.

After searching this list, I so far found two possible ways to proceed:

a) Extended the ramdisk so that it mounts a disk partition /dev/hdaX,
and then chroot to that mounted partition. Then try to launch the QEMU
image fro

Questions about Vcon.

Juwon.Song — 2012-04-09T06:48:37

Hello l4-hackers,

I will try to use the Vcon of Fiasco. But I don't know about the usage of
Vcon.
I want to know more information about Vcon.
If you have the more information and usage of Vcon, give me the data or
examples.

Thank you.

Song.
_______________________________________________
l4-hackers mailing list
l4-hackers< at >os.inf.tu-dresden.de
http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers

FPU state management in L4Fiasco.OC program

Mai, Haohui — 2012-04-08T22:22:21

Hi,

I'm writing a new OS kernel atop of L4Fiasco.OC. I'm having some
difficulties to let my OS support user-level processes that uses
floating-point instruction.

So far, My OS closely follows L4Linux, it creates a new task for each
user-level process, and marks as all threads of the task as alien thread to
capture all page faults and exceptions.

My OS works fines with page fault and syscalls. However, I'm confused with
what I should do with floating-point exception (exception #7), which is
issued to my kernel at the first time it tries to perform floating-point
arithmetic.

I tried to return to the user-level process with an empty message (
l4_msgtag_t tag = l4_msgtag(0, 0, 0, 0) ), or an empty message with
L4_MSGTAG_TRANSFER_FPU (l4_msgtag_t tag = l4_msgtag(0, 0, 0,
L4_MSGTAG_TRANSFER_FPU) ), but I had no luck.

The user-level process immediately calls "int $0x3" and stops.

I read through L4Linux's code and it seems it's doing similar thing, except
that it did initialize the FPU state before asking L4 t

Source of KVM-L4 ?

Rolf Sommerhalder — 2012-04-08T08:51:29

Hello list,

Is there any source code available of "KVM-L4", e.g. KVM which has been
ported to L4Linux?

There are some publications from TU Dresden which report about this
successful port as KVM-L4. Is its source code available at all, or is it
just hiding from search engines in some public repository or archive?

Thanks,
Rolf

Can't get sender from l4_ipc_wait()

Mai, Haohui — 2012-04-05T22:35:13

Hi,

It seems that l4_ipc_wait() will always set the sender to zero. I tested it
in example at /pkg/examples/sys/ipc/ipc_example.c, in the l4re-2011081207
snapshot.

Here is the patch I applied to the file (to print out label):

--- a/ipc_example.c     2011-08-12 00:20:36.000000000 -0500
+++ b/ipc_example.c       2012-04-05 17:29:24.844608359 -0500
< at >< at > -84,6 +84,7 < at >< at >
           continue;
         }

+      printf ("IPC from %lx, %d\n", label, label == 0);
       /* So, the IPC was ok, now take the value out of message register 0
        * of the UTCB and store the square of it back to it. */
       l4_utcb_mr()->mr[0] = l4_utcb_mr()->mr[0] * l4_utcb_mr()->mr[0];

And here is the result I got:

...
vandroid| Sending:  4
vandroid| IPC from 0, 1
vandroid| Received: 16
...

So it seems that l4_ipc_wait() doesn't return the sender.

I'm writing an OS on top of Fiasco.OC. This information is important for
pager because it'll need it to figure out which page it'll map in.

Do you have any ideas to fix it, or any ide

Tracing only write page-faults

Ivan Bludov — 2012-04-05T12:32:22

Hello.
I want to trace all write page-faults from an application. I use the
pager that wait for page-fault and maps the fpage to thread calling
l4_ipc_send_and_wait setting L4_ITEM_MAP. For tracing only write
page-faults I map fpage as L4_FPAGE_RO if it was read-pf and then I
map the same fpage with L4_FPAGE_RW if the next write-pf occurs. (I
mean I map the same fpage with the different flags twice). But an
application doesn't continue run. Also I have tried to
l4_task_unmap(L4_FP_OTHER_SPACES) this fpage before mapping it as
L4_FPAGE_RW. It doesn't work. What should I use to change fpage's
rights to L4_FPAGE_RW for fpage that is already mapped as L4_FPAGE_RO
for an application?

Ivan Bludov

support for multi-core in Fiasco.OC

K M — 2012-04-05T01:05:35

I am using Fiasco.OC with VirtualBox and have successfully booted and run some demos. However, I am unable to get the kernel to use more than one core on my quad-core machine. I have enabled all 4 processors within the VirtualBox L4 machine, but when I run the "thread_migrate" example, only one CPU is ever recognized and used. What am I doing wrong?

Thanks,
Kevin
_______________________________________________
l4-hackers mailing list
l4-hackers< at >os.inf.tu-dresden.de
http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers

libgendep on Ubuntu 11.10

Christian Helmuth — 2012-04-02T11:20:08

Hi,

with current SVN (r38) I get the following error:

  gcc -fPIC -Wall -pedantic -g -m64 -c /plain/krishna/src/genode/genode.git/base-foc/contrib/l4/tool/gendep/deptrack.c -o /plain/krishna/build/genode.foc_x86_32/l4/tool/gendep/deptrack.64.o
  gcc -fPIC -Wall -pedantic -g -m64 -c /plain/krishna/src/genode/genode.git/base-foc/contrib/l4/tool/gendep/syscall.c -o /plain/krishna/build/genode.foc_x86_32/l4/tool/gendep/syscall.64.o
  mkdir -p /plain/krishna/build/genode.foc_x86_32/l4/tool/gendep/64
  gcc -m64 -shared -Wl,-soname,/plain/krishna/build/genode.foc_x86_32/l4/tool/gendep/64/libgendep.so -ldl -o /plain/krishna/build/genode.foc_x86_32/l4/tool/gendep/64/libgendep.so /plain/krishna/build/genode.foc_x86_32/l4/tool/gendep/deptrack.64.o /plain/krishna/build/genode.foc_x86_32/l4/tool/gendep/syscall.64.o
  /usr/local/genode-gcc/bin/genode-x86-gcc: symbol lookup error: /plain/krishna/build/genode.foc_x86_32/l4/tool/gendep/64/libgendep.so: undefined symbol: dlsym

The attached patch fixed the issue for me and