l4linux build failure, and a few questions
adam at os.inf.tu-dresden.de
Sun Jun 24 23:36:55 CEST 2012
On Fri Jun 22, 2012 at 07:19:32 -0700, Ryan Brown wrote:
> I tried building l4linux for x86 and got this error:
> MODPOST vmlinux.o
> WARNING: modpost: Found 1 section mismatch(es).
> To see full details build your kernel with:
> 'make CONFIG_DEBUG_SECTION_MISMATCH=y'
> GEN .version
> CHK include/generated/compile.h
> UPD include/generated/compile.h
> CC init/version.o
> LD init/built-in.o
> LD .tmp_vmlinux1
> drivers/built-in.o: In function `pnp_register_irq_resource':
> /home/ribrdb/fiasco/src/l4linux/drivers/pnp/resource.c:70: undefined
> reference to `pcibios_penalize_isa_irq'
> make: *** [.tmp_vmlinux1] Error 1
> make: *** [sub-make] Error 2
> Has anyone seen this before?
Hmm, enabled PCI? Could you share your .config?
> Also I had a few questions about configuring l4linux:
> I see that the paravirtualization options are not supported. Is there a
> specific reason for this? I'd like to be able to use virtio devices from
> l4linux when running in a VM.
The paravirtualization abstraction inside Linux has been introduced long
after L4Linux already existed. Also this abstraction is really only an
abstraction for privileged instructions, rather than a bit more higher
level. Anyway, I would not think it has anything to do with virtio devs.
> Neither x86_64 or highmem is supported. Is there any way to run an l4 linux
> with more than 1G of memory?
L4Linux can use as much memory as an L4 user level application can use,
i.e. about 3GB.
> Can 32 bit l4linux run on a 64 bit fiasco kernel?
> Does 32 bit fiasco support more than 1G of physical memory?
> What would be involved if I wanted to port l4linux to x86_64?
Adding all the missing pieces to L4Linux. It's quite a bit of work I'd
Adam adam at os.inf.tu-dresden.de
More information about the l4-hackers