users

users@lists.genode.org

2285 discussions

Support variable length blobs in RPC
by Daniel Waddington 27 Apr '13

27 Apr '13

Hi, What's the best way to create RPC types for variable length data (assuming a maximum size of that will fit in the UTCB). I looked at Rpc_in_buffer, but this seems to only support strings, and using as an out param seems awkward. For the moment I am using a statically sized structure, but I fear there is needless copying going on. BTW, this RPC is for one-off control - of course shared memory is better for streaming. Daniel

2 1

debug nic_drv
by Keqin Sun 26 Apr '13

26 Apr '13

Hi, I want to debug nic_drv on a real machine using gdb_monitor. But gdb showed this: (gdb) target remote /dev/ttyS0 Remote debugging using /dev/ttyS0 Ignoring packet error, continuing... warning: unrecognized item "timeout" in "qSupported" response Ignoring packet error, continuing... Ignoring packet error, continuing... Ignoring packet error, continuing... and my run srcript is: # # Build # build { core init drivers/timer drivers/pci app/gdb_monitor drivers/uart drivers/nic } create_boot_directory # # Generate config # install_config { <config verbose="yes"> <parent-provides> <service name="ROM"/> <service name="RAM"/> <service name="IRQ"/> <service name="IO_MEM"/> <service name="IO_PORT"/> <service name="CAP"/> <service name="PD"/> <service name="RM"/> <service name="CPU"/> <service name="LOG"/> <service name="SIGNAL"/> </parent-provides> <default-route> <any-service> <parent/> <any-child/> </any-service> </default-route> <start name="timer"> <resource name="RAM" quantum="1M"/> <provides> <service name="Timer"/> </provides> </start> <start name="uart_drv"> <resource name="RAM" quantum="2M"/> <provides> <service name="Terminal"/> </provides> #is that service name "Terminal" should be "/dev/ttyS0" ? <config> <policy label="gdb_monitor" uart="1"/> </config> </start> <start name="pci_drv"> <resource name="RAM" quantum="2M"/> <provides><service name="PCI"/></provides> </start> <start name="gdb_monitor"> <resource name="RAM" quantum="5M"/> <provides><service name="Nic" /></provides> <config> <target name="nic_drv"/> <preserve name="RAM" quantum="2M"/> </config> </start> </config>} # # Boot image # build_boot_image { core init timer ld.lib.so libc.lib.so libc_log.lib.so libc_lock_pipe.lib.so libc_terminal.lib.so uart_drv pci_drv gdb_monitor nic_drv } set local_port 5555 #append qemu_args " -nographic " append qemu_args " -m 128 -nographic " # connect comport 0 to stdio append qemu_args " -net nic,model=e1000 -net user " append qemu_args " -serial mon:stdio " # connect comport 1 with TCP port $local_port append qemu_args " -serial chardev:uart " append qemu_args " -chardev socket,id=uart,port=$local_port,host=localhost,server,nowait " #run_genode_until forever run_genode_until {.*Remote debugging using /dev/ttyS0.*} 30 #run_genode_until {.*Remote debugging using /dev/terminal.*} 30 #exec [terminal] -e "[gdb] bin/nic_drv -ex \"target remote localhost:$local_port\" " & #exec [terminal] -e "[gdb] bin/nic_drv -ex \"target remote localhost:$local_port\" " & interact Is that correct? Maybe the serial was occupied by the system output? keqin

3 12

"Could not allocate metadata" error msg
by Jilong Kuang - SISA 23 Apr '13

23 Apr '13

Hi all, Can anyone give me a hint on how to get rid of the "Could not allocate metadata" error msg? Or, how can I effectively increase the quota for that? I already gave sufficiently large (way more than the process needs) RAM quota in the run script (config file). I also tried putting a line like this at the beginning of the main() function "Genode::env()->parent()->upgrade(Genode::env()->ram_session_cap(), "ram_quota=64M");" But it doesn't help much. Thank you for your help! Best regards, Jilong

2 3

Re: debug nic_drv
by Keqin Sun 22 Apr '13

22 Apr '13

Hi Norman, Thanks for your reply, and it is really helpful. I was totally lost in that issue and you pulled me out. I will give it a try following your guide. Regards Keqin On ÐÇÆÚÁù, ËÄÔÂ 20, 2013 6:39 pm, Norman Feske wrote: ----------------------------------------------------------------------------------- Hi Keqin, I suspect that you are mixing up the UART interfaces. The run script relies on two UARTs to be present. UART 0 is used for printing Genode's LOG messages and the kernel messages. The GDB monitor requires a separate channel of communication to the remote GDB. The run script uses UART 1 via the 'uart_drv' for that. UART 1 is then translated by qemu to a TCP connection. When executing the script on real hardware, you need two UARTs as well. I suspect that you have connected only a single one. Connecting GDB to the UART 0 of the Genode system makes no sense because this one is unrelated to the GDB monitor. > <start name="uart_drv"> > <resource name="RAM" quantum="2M"/> > <provides> <service name="Terminal"/> </provides> > #is that service name "Terminal" should be "/dev/ttyS0" ? The service name denotes the type of the session. The UART driver provides sessions of type "Terminal" and "Uart". (the "Uart" type is a specialized kind of "Terminal", not important here) In the Genode world "/dev/ttyS0" has no meaning. > <config> > <policy label="gdb_monitor" uart="1"/> > </config> > </start> This configuration tells the UART driver to hand out the second UART (UART 1) to the gdb_monitor client. The numbering starts at 0. UART 0 is typically used by the kernel and Genode's core. > Is that correct? Does the run script works as intended on Qemu? > Maybe the serial was occupied by the system output? I guess, you are putting your finger exactly on the issue. Do you have a way to connect a second UART to your PC? If you consider using a PCI card with additional comports, you will need to make sure that the UART driver uses the I/O ports of the card. (by modifying the function 'io_port_base' in 'os/src/drivers/uart/i8250/main.cc'. You may determine the right values by booting Linux once and executing 'lspci'. I admit, that sounds a bit awkward and complicated. Normally, you could use the TCP terminal ('gems/src/server/tcp_terminal') as an alternative to an UART interface when using GDB monitor. So there would be no need for multiple UART interfaces. (the TCP terminal provides the "Terminal" interface but works over TCP) Unfortunately, that's not possible when debugging the NIC driver because TCP terminal requires a NIC driver to work. Cheers Norman -- Dr.-Ing. Norman Feske Genode Labs http://www.genode-labs.com � http://genode.org Genode Labs GmbH � Amtsgericht Dresden � HRB 28424 � Sitz Dresden Geschäftsführer: Dr.-Ing. Norman Feske, Christian Helmuth ------------------------------------------------------------------------------ Precog is a next-generation analytics platform capable of advanced analytics on semi-structured data. The platform includes APIs for building apps and a phenomenal toolset for data science. Developers can use our toolset for easy data analysis & visualization. Get a free account! http://www2.precog.com/precogplatform/slashdotnewsletter _______________________________________________ Genode-main mailing list Genode-main(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/genode-main -----------------------------------------------------------------------------------

1 0

how to solve issue#593
by yuqing wang 19 Apr '13

19 Apr '13

Hi, I want to run l4linux on real machine ,but there is someting wrong. [init -> nic_drv] number of devices: 1 [init -> nic_drv] --- init rx_callbacks [init -> nic_drv] --- get MAC address [init -> nic_drv] 00:0e:04:00:03:16 [init -> nic_drv] mmemory allocation failed in alloc_memblock (size=2048, align=800, offset=0) [init -> nic_drv] mmemory allocation failed in alloc_memblock (size=2048, align=800, offset=0) [init -> nic_drv] mmemory allocation failed in alloc_memblock (size=2048, align=800, offset=0) PC hardware motherboard : DELL OptiPlex 330 CPU : Intel Pentium dual e2180 @ 2.00GHz Ethernet : intel 82541pi RAM : 2G the log is attached as log1 . I know it is discussed before as issue#593, https://github.com/genodelabs/genode/issues/593 , and I find chelmuth tried to solve this issue .Later,I find a branch about issue#593 https://github.com/chelmuth/genode/tree/issue593. I download the branch,find l4linux.run script have error running in qemu. [init -> nic_drv] snprintf not implemented [init -> nic_drv] void {anonymous}::Backing_store::_grow(): size=0 + chunk=8000 [init -> nic_drv] memory allocation failed in alloc_memblock (size=256, align=100, offset=0) [init -> nic_drv] dde_ipxe_nic_init(): opening device 00:03.0 failed [init -> nic_drv] number of devices: 0 [init -> nic_drv] --- init rx_callbacks I also tried issue593.run script ,have the same error. the log is attached as log2. Any help is appreciated. Regards. Yuqing Wang

3 6

how to install Genode on PC machine
by Jian Liu 15 Apr '13

15 Apr '13

Hi Norman, With your help, I have now some experiences on Genode, such as building and demo it in Qemu. I have also learned about the whole structure of source code and some calling relastionship in the system. Now I try to install Genode in my PC (the physical machine) and boot it from hard drivers. So I can see avaliablity and response time from applications such as Arora, which is really some slow in Qemu. But I don't know to do it. Could you give me some directions? Thanks. I have found some guy sent similar question in the mail list last year as, http://sourceforge.net/mailarchive/forum.php?thread_name=4FB142EF.2080407%4… But there is no detail explainations and steps how to do it. I wonder if there is any document on how to install Genode in a PC. Which hardwares does it support now? and how to config drivers code for network card, usb etc? Best, Jian

4 22

Help on running the Hello code in Genode.
by Pramod Herath 08 Apr '13

08 Apr '13

Hello, I'm trying to run the hello tutorial provided with Genode on my system and am having trouble understanding it's output. When I run ./core all I get is: int main(): --- create local services --- int main(): --- start init --- int main(): transferred 17592186044415 MB to init int main(): --- init created, waiting for exit condition --- Quota exceeded! amount=4096, size=4096, consumed=4096 [init] upgrading quota donation for SIGNAL session [init] Could not open file "config" [init] Could not obtain config file [init] C++ runtime: Genode::Config::Invalid [init] void* abort(): abort called and the system seems to be waiting indefinitely. Is there anything wrong I've done? Am I missing anything? Thanks in advance for helping the beginners. - Pramod

3 4

l4linux run on PC, nic_drv issue
by yuqing wang 07 Apr '13

07 Apr '13

Hi, I want to run l4inux on my PC, I copied the files needed in the harddisk and modified the GRUB menu.lst .But I got a issue when the system started. int main(): [33m--- create local services --- [0m int main(): [33m--- start init --- [0m int main(): [33mtransferred 1718 MB to init [0m int main(): [33m--- init created, waiting for exit condition --- [0m [init] [31mCould not open file "ld.lib.so" [0m [init -> l4linux] [32mBooting L4Linux ... [0m [init -> l4linux] [34;1m======> L4Linux starting... <======== [0m [init -> l4linux] Linux version 3.5.0-l4+ (wangyuqing@...186...) (gcc version 4.7.2 (GCC) ) #36 SMP Wed Apr 3 10:54:04 CST 2013 [init -> l4linux] Binary name: vmlinux [init -> nic_drv] --- iPXE NIC driver started --- [init -> l4linux] Linux kernel command line (5 args): mem=64M console=ttyS0 l4x_rd=initrd.gz l4x_cpus=2 l4x_cpus_map=0,1 [init -> l4linux] CPU mapping (l:p)[2]: 0:0, 1:1 [init -> l4linux] Image: 00401000 - 00839000 [4320 KiB]. [init -> l4linux] Areas: Text: 00401000 - 00742000 [3332kB] (a bit longer) [init -> l4linux] Data: 00742000 - 00764ea4 [139kB] [init -> pci_drv] PCI driver started [init -> l4linux] Initdata: 0077b000 - 007a2000 [156kB] [init -> uart_drv] --- i8250 UART driver started --- [init -> l4linux] BSS: 007a2000 - 00829000 [540kB] [init -> l4linux] [34ml4util_cpu_capabilities: Not implemented yet! [0m [init -> l4linux] gs=43 fs=43 [init -> l4linux] [34ml4io_get_root_device: Not implemented yet! [0m [init -> l4linux] Device scan: [init -> l4linux] [34ml4io_iterate_devices: Not implemented yet! [0m [init -> l4linux] Device scan done. [init -> l4linux] l4x_fiasco_gdt_entry_offset = 9 [init -> vesa_drv] int Framebuffer_drv::map_io_mem(Genode::addr_t, Genode::size_t, bool, void**, Genode::addr_t, Genode::Dataspace_capability*): [33mfb mapped to 1092000 [0m [init] [31muart_drv: illegal announcement of service "Uart" [0m [init -> ps2_drv] Using keyboard with scan code set 2. [init -> pci_drv] [31mCould not open file "pci_device_pd" [0m [init -> pci_drv] [34mPCI device protection domain for IOMMU support is not available [0m [init -> timer] [33margs='label="l4linux", ram_quota=4096' [0m [init -> pci_drv] [31mCould not open file "config" [0m [init -> pci_drv] [31mCould not obtain config file [0m [init -> pci_drv] [31mPCI config space data could not be parsed. [0m [init -> l4linux] main thread will be f [init -> l4linux] l4x_register_pointer_section: addr = 00400000 size = 4427776 [init -> l4linux] section-with-init: virt: 400000 to 838fff [4324 KiB] [init -> l4linux] [34mCannot determine physical address for dataspace Binary! [0m [init -> l4linux] error: failed to get physical address for 400000. [init -> l4linux] Main thread running, waiting... [init -> l4linux] thread=f000 cpu=0 [init -> l4linux] WARNING: Unknown wrmsr: 0000008b at 616221 [init -> l4linux] l4x_setup_memory: Forcing superpages for main memory [init -> l4linux] l4re_global_env: 0 [init -> l4linux] Main memory size: 64MB [34munmapping of managed dataspaces not yet supported [0m [init -> l4linux] Main memory: virt: 50000000 to 53ffffff [65536 KiB] [init -> l4linux] Main memory: Phys: 0x50000000 to 0x54000000, Size: 67108864 [init -> l4linux] Filling lower ptabs... [init -> l4linux] Done (0 entries). [init -> l4linux] l4x_register_pointer_section: addr = 00400000 size = 4427776 [init -> l4linux] text: virt: 400000 to 838fff [4324 KiB] [init -> l4linux] [34mCannot determine physical address for dataspace Binary! [0m [init -> l4linux] error: failed to get physical address for 400000. [init -> l4linux] l4x_rd_path: initrd.gz [init -> l4linux] Loading: initrd.gz [init -> l4linux] INITRD: Size of RAMdisk is 3608KiB [init -> l4linux] RAMdisk from 00a00000 to 00d86000 [3608KiB] [init -> uart_drv] [32mBaudrate is not defined. Use default 115200 [0m [init -> l4linux] l4timer: Using IRQ65 [init -> timer] [33margs='label="l4linux", ram_quota=4096' [0m [init -> l4linux] WARNING: Unknown wrmsr: 0000008b at 616221 [init -> l4linux] WARNING: Unknown rdmsr: 00000345 at 781629 [init -> l4linux] WARNING: Unknown rdmsr: 00000186 at 7809ef [init -> l4linux] WARNING: Unknown rdmsr: 00000187 at 7809ef [init -> l4linux] WARNING: Unknown wrmsr: 000000c1 at 780a70 [init -> l4linux] Launching cpu1 on pcpu 1 at 6145be [init -> timer] [33margs='label="l4linux", ram_quota=4096' [0m [34mQuota exceeded! amount=4096, size=4096, consumed=4096 [0m [init -> l4linux] [32mupgrading quota donation for SIGNAL session [0m [init -> l4linux] l4x_cpu_threads[1] = 44000a00 [init -> l4linux] thread=18000 cpu=1 [init -> l4linux] WARNING: Unknown wrmsr: 0000008b at 616221 [init -> vesa_drv] [31mCould not open file "config" [0m [init -> vesa_drv] [31mCould not obtain config file [0m [init -> vesa_drv] [34munexpected configuration address 0x54 [0m [init -> vesa_drv] [34munexpected configuration address 0x54 [0m [init -> vesa_drv] [34mrequested PCI resource 0x1 invalid [0m [init -> vesa_drv] [34munexpected configuration address 0x54 [0m [init -> vesa_drv] [34mrequested PCI resource 0x1 invalid [0m [init -> vesa_drv] [34munexpected configuration address 0x54 [0m [init -> vesa_drv] [34mrequested PCI resource 0x1 invalid [0m [init -> vesa_drv] [34munexpected configuration address 0x54 [0m [init -> vesa_drv] [34mrequested PCI resource 0x1 invalid [0m [init -> vesa_drv] [34munexpected configuration address 0x54 [0m [init -> vesa_drv] [34mrequested PCI resource 0x1 invalid [0m [init -> vesa_drv] [34munexpected configuration address 0x54 [0m [init -> vesa_drv] [34mrequested PCI resource 0x1 invalid [0m [init -> vesa_drv] [34munexpected configuration address 0x54 [0m [init -> vesa_drv] [34mrequested PCI resource 0x1 invalid [0m [init -> vesa_drv] [34munexpected configuration address 0x54 [0m [init -> vesa_drv] [34mrequested PCI resource 0x1 invalid [0m [init -> vesa_drv] [34munexpected configuration address 0x54 [0m [init -> vesa_drv] [34mrequested PCI resource 0x1 invalid [0m [init -> vesa_drv] Found: VESA BIOS version 3.0 [init -> vesa_drv] OEM: ATI ATOMBIOS [init -> vesa_drv] [34munexpected configuration address 0x54 [0m [init -> vesa_drv] [34mrequested PCI resource 0x1 invalid [0m [init -> vesa_drv] [34munexpected configuration address 0x54 [0m [init -> vesa_drv] [34munexpected configuration address 0x54 [0m [init -> vesa_drv] [34mrequested PCI resource 0x1 invalid [0m [init -> vesa_drv] Found: physical frame buffer at 0xc0000000 size: 0x01000000 [init -> vesa_drv] int Framebuffer_drv::map_io_mem(Genode::addr_t, Genode::size_t, bool, void**, Genode::addr_t, Genode::Dataspace_capability*): [33mfb mapped to 1400000 [0m [34mQuota exceeded! amount=4096, size=4096, consumed=4096 [0m [init -> nic_drv] [32mupgrading quota donation for SIGNAL session [0m [init -> nic_drv] [32m--- init iPXE NIC [0m [init -> timer] [33margs='label="nic_drv", ram_quota=4096' [0m [init -> nic_drv] scan_pci(): [36mFound: 02:00.0 14e4:169b (rev 02) IRQ 0b [0m [init -> nic_drv] probe_pci_device(): [36mno driver found [0m [init -> nic_drv] scan_pci(): [36mFound: 03:01.0 8086:107c (rev 05) IRQ 05 [0m [init -> nic_drv] probe_pci_device(): [36musing driver 82541pi [0m [init -> nic_drv] ioremap(): [36mbus_addr = dfac0000 len = 20000 [0m [init -> nic_drv] [35msnprintf not implemented [0m [init -> nic_drv] [32m number of devices: 1 [0m [init -> nic_drv] [32m--- init rx_callbacks [0m [init -> nic_drv] [32m--- get MAC address [0m [init -> nic_drv] [32m 00:0e:04:00:03:16 [0m [init -> nic_drv] [31mmemory allocation failed in alloc_memblock (size=2048, align=800, offset=0) [0m [init -> nic_drv] [31mmemory allocation failed in alloc_memblock (size=2048, align=800, offset=0) [0m [init -> nic_drv] [31mmemory allocation failed in alloc_memblock (size=2048, align=800, offset=0) [0m [init -> nic_drv] [31mmemory allocation failed in alloc_memblock (size=2048, align=800, offset=0) [0m [init -> nic_drv] [31mmemory allocation failed in alloc_memblock (size=2048, align=800, offset=0) [0m The board of my PC is DELL OptiPlex 330. It has a broadcom Enthernet Card on board and a another intel 82541 Enthernet Card.

1 0

Interrupts in L4Linux
by Alexander Tarasikov 05 Apr '13

05 Apr '13

Hello, Genode Hackers! I'm currently implementing an X86 PCI bus driver for L4Linux as a temporary solution for getting USB support in L4Linux. Current genode-side code is presented below. The l4linux patch is not ready, but I've submitted the relevant part of the diff to pastebin (it's only makefile and kconfig anyway) https://github.com/Ksys-labs/genode/blob/pci_wip/ports-foc/src/drivers/geno… https://github.com/Ksys-labs/genode/blob/pci_wip/ports-foc/src/lib/l4lx/gen… https://github.com/Ksys-labs/genode/blob/pci_wip/ports-foc/src/lib/l4lx/l4_… http://pastebin.com/9c37tuJR I have implemented the linux driver which calls the Genode pci service routines. I have also extended the l4lx io library to allow mapping pci memory space. With this patches, the ehci and ohci drivers probe in linux, but fail to work because interrupts are not triggered. I have implemented the fake irq thread which kicks the irq handler every millisecond and with that usb works. This indicates that the pci subsystem and memory mapping are I've got some questions regarding interrupt handling in L4Linux and Genode in general. 1. Why are NR_IRQS_HW interrupts reserved on X86 in l4linux? The EHCI controller wants the interrupt number 11 which is lower than NR_IRQS_HW. Ok, I worked around that by editing the constant and removing the "BUG_ON(NR_REQUESTABLE < 1)" in arch/l4/kernel/irq.c init_array function 2. How are capabilities actually assigned? it would seem to me that l4x_register_irq allocates the capabilitiies in the first available slot, but l4x_have_irqcap looks it up by index. I've worked around it by explicitely allocating 12 capabilities via l4x_cap_alloc, but still got error -2004 on irq attach. Now, I've had success in attaching irq after I allocated the capability via the following code in l4lx: Genode::Foc_cpu_session_client cpu(Genode::env()->cpu_session_cap()); p->irq_cap = cpu.alloc_irq().dst(); 3. what's the purpose of multiplying the irq number by four in l4_msgtag_t ret = l4_irq_attach(p->irq_cap, data->irq << 2, l4x_cpu_thread_get_cap(p->cpu));? As far as I can see, in the base-foc irq implementation, irq number is never multiplied 4. non-genode question, probably. Do EHCI/PCI interrupts need a special kick to work? I've tried using Genode::Irq_session for irq11, but wait_for_irq never returns. On the other hand, I've tried the regular linux iso on the same machine (which is actually qemu) and the ehci interrupt is indeed 11 and it works fine there. So, the question is, why is interrupt handling broken and the only working interrupt in l4linux is timer which actually uses L4 timer ipc instead of irq and how this should be fixed. Also, what do you think of making a "genode" arch for linux and getting rid of l4linux which uses the Fiasco.OC API bypassing Genode interfaces? -- Regards, Alexander

6 12

about crypto service in Genode
by Jian Liu 05 Apr '13

05 Apr '13

Hi all, When I read "Road Map for 2013", I find there is furture release 13.05 (should be publised in May this year according to the Road Map) which support Cryptography functions in Genode. And moreover, I also find current topics related to crypto serivce as follow. https://github.com/genodelabs/genode/issues/55 But it has not been updated for serval monthes. I wonder if there is a detailed planning about crypto development in Genode. I am interested in it. I can join this work follow your planning. Best, Jian LIU ---- email to: gjk.liu@...9...

3 6

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

users