users

users@lists.genode.org

4 participants
2327 discussions

Illegal session request to service CPU
by Markus Partheymueller 17 Aug '12

17 Aug '12

Hi, with the latest code in staging I get the following error when starting the PCI driver through ACPI: [init -> acpi -> pci_drv] PCI driver started [init -> acpi] pci_drv: illegal session request of service "CPU" Later, the PCI driver fails because of this. The config portion looks as follows: <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> ... <start name="acpi"> <resource name="RAM" quantum="32M"/> <binary name="acpi_drv"/> <provides> <service name="PCI"/> <service name="IRQ"/> <service name="CPU"/> </provides> <parent-provides> <service name="CPU"/> </parent-provides> <route> <service name="PCI"> <any-child/> </service> <any-service><parent/><any-child/></any-service> </route> </start> The parent-provides entry and the service name="CPU" in <provides> were not present in my last setup, but didn't change anything. Am I missing something or is there a problem with the most recent changes regarding the CPU session or NOVA-specific code? Cheers, Markus

2 1

Fwd: Re: openrisc
by Martin Stein 09 Aug '12

09 Aug '12

-------- Original Message -------- Subject: Re: openrisc Date: Thu, 09 Aug 2012 11:08:04 +0200 From: Martin Stein <martin.stein@...1...> To: Nick Betteridge <nick.betteridge@...2...> Hi Nick, I'm pleased to hear that you've found the time to proceed. ... You're right concerning the directory 'src/platform'. Due to the fact that 'base-hw' solely targets ARM systems for now, the separation of generic and platform specific code is not proven very well. I've annotated this issue, thank you! Moreover i'm not sure if i've understood you right regarding 'mode_transition.s'. The file does not really handle or control any type of exception. It's purpose is on the one hand to only catch exceptions, wich occur in userland, save the interrupted user execution-state and exception information, and get back to the kernel enviroment to re-run 'kernel()'. On the other hand it offers also the opposite direction, that is resuming a given user execution-context in userland once 'kernel()' returns. This way the handling of the concrete exception, whether it is an interrupt, a page fault or a syscall, resides completely in 'kernel()'. If you were looking for the resolution of page faults, even 'kernel()' is not the final destination. When kernel detects the presence of a page fault, the function 'handle_pagefault()' only checks if the fault was caused by a translation miss. If this is the case a pager might resolve the problem by expanding the according page table. Thus kernel composes an appropriate IPC message to the pager that is identified by the thread object of the faulter. The pager normally is a thread in Genodes 'core' process, wich itself asks the so called "Region Manager" of the faulter for a region mapping that covers the fault. If a mapping is found the pager modifies the page table accordingly. The only process that doesn't need pagers is 'core'. Because 'core' is the first process in Genode, gets initialized by 'kernel()' and must be trusted anyway, its page table gets filled with static 1:1 translations initially by kernel. Once this is done, kernel itself joins this process, so userland threads in 'core' and the kernel "thread" share the same address space. Long story short, the configuration of virtual/effective addresses depends, except of 'core' on the region managers, wich themselves are instructed through the RM-sessions (base/include/rm-session/rm_session.h) they provide to their RPC-clients. I hope this gives you a rough picture of Genodes virtual-address management, even it is a somewhat far-reaching explanation. Cheers, Martin On 08/08/2012 06:24 PM, Nick Betteridge wrote: > Hi Martin, > > ... > > I have been slowly reading through your arm assembler, trying to > understand how genode works. > > Just one thing - you have partitioned both arm processors and platforms > into named directories, except for base_hw/src/platform, which contains > arm assembler. Do you intend to refactor this into something like > base_hw/src/platform/arm? > > Just one more thing, am I right in thinking > > 'base-hw/src/core/arm_v7a/mode_transition.s' > > is just for interrupt control? I can't find anything for configuring > virtual/effective addresses - perhaps this is done in 'c' (I haven't > read the c yet) - in openrisc this is handled in the supervisor mode. > > Cheers > Nick > > > >

2 1

[genode] [feature request] Lock and RW lock function for Genode Thread support.
by 김은석 07 Aug '12

07 Aug '12

3 2

Fwd: Re: openrisc
by Martin Stein 03 Aug '12

03 Aug '12

-------- Original Message -------- Subject: Re: openrisc Date: Fri, 03 Aug 2012 08:08:18 +0100 From: Nick Betteridge <nick.betteridge@...2...> To: Martin Stein <martin.stein@...1...> Hi Martin, Thanks for getting back to me - no problem on delayed reply as I'm looking after my two boys whilst trying to do some work. It's chaos. No problem also on using the genode lists. I may initially ask some very dumb questions as I haven't touched assembler work and processors since the early 80's. I have quickly scanned through your base_hw. Thank you so much for really documenting the code so well - at a first glance it looks as though a port should be straight forward. For the next two weeks I have to manage a 9 year old and a twelve year old and will attempt a port on my own if and when I get a chance. (I can't believe I was so badly behaved at those ages). After that we're on holiday in France until the beginning of September. From September onwards I hope to devote one day a week to this. Thanks again for being supportive and offering your help. Cheers, Nick On 03/08/12 00:14, Martin Stein wrote: > Hi Nick, > > First of all please excuse the delayed reply. > > For me its no problem that you've targeted me directly, > but i would propose to move this discussion to the > main list of Genode Labs for two reasons. > On the one hand it might be that other readers can > complete my comments in order that you can succeed > as soon as possible. On the other hand the results could > help other peoples as well. > > To bring it back to your questions, i'm very pleased to > hear about your intentions concerning OpenRISC, > not least because for now i don't know anybody who > addresses oneself to this task. > > Nevertheless i would recommend you to have a look > to my branch 'base_hw': > https://github.com/m-stein/genode/tree/base_hw > > It offers the direct port of Genode to several CortexA9 > systems through the 'base-hw' repository and thereby > pursues goals similar to 'base-mb'. Thus it can be seen > as the latest state of running Genode directly on RISC. > Furthermore 'base-mb' can't hide that it was my first > try to create a microkernel and it is an aspiration to > provide Microblaze support with the means of 'base_mb' > someday. > > Certainly this branch will be merged to the official 'master' > branch soon, we only just merged it into staging to let our > build bot give it a last check. > > So if you have further questions dont't hesitate to ask. > > Cheers, > Martin > > > On 08/01/2012 07:25 PM, Nick Betteridge wrote: >> Hi Martin, >> >> I hope you don't mind me writing directly to you. >> >> I am just about to do a port of your microblaze base of genode to >> openrisc. After spending sometime reading through the OR1K >> architecture manual and additional documentation I'm hoping that it >> should be quite straight forward. >> >> However, it suddenly struck me that somebody might have already done >> this. Do you know if anybody has done an Openrisc port? >> >> Just one more question - do you have any idea when you will be adding >> capability-based delegation of communication rights to the base-mb tree? >> >> Finally, I may have a few questions about the microblaze >> implementation whilst doing the port - would you mind if I contacted you? >> >> Cheers and best regards, >> >> Nick

1 1

Question about using heap
by 정복득 02 Aug '12

02 Aug '12

Hi, My program runs two kinds of RPC server in a single process. Do I need to get sliced heap for each RPC server or can I just share one sliced heap object between the rpc server? For example, Sliced_heap sliced_heap1(env()->ram_session(), env()->rm_session()); Sliced_heap sliced_heap2(env()->ram_session(), env()->rm_session()); ... Server1_root_component server1_root(&server1_ep, &sliced_heap1, ....); Server2_root_component server1_root(&server2_ep, &sliced_heap2, ....); OR Sliced_heap sliced_heap(env()->ram_session(), env()->rm_session()); ... Server1_root_component server1_root(&server1_ep, &sliced_heap, ....); Server2_root_component server1_root(&server2_ep, &sliced_heap, ....); My another question is : Do I need to use Synchronized_allocator to allocate a memory from heap (for object creation) when running multiple thread? Or is it ok to call (env()->heap()) for object creation in heap? Thank you. Bokdeuk Jeong

2 1

Trouble with QEMU when running run/demo on branch 12.05
by Сергей Грехов 01 Aug '12

01 Aug '12

Hello to all! I have switched on commit daf4300 and tried to run demo with command "make run/demo". The output gives no error, but for some reason qemu shows only black screen. I tried to use qemu provided by Ubuntu (0.15.1) and tried to compile version 0.14.1 with SDL support - the result is the same - black screen. The emulated system is foc_pbxa9. Command "make run/demo" works fine on tag 12.05. So I guess that the problem is in some commit between b54bdea and daf4300. -- Best regards, Sergey S. Grekhov

2 1

NOVA: Capability selectors cause call of invalid portal
by Markus Partheymueller 31 Jul '12

31 Jul '12

Hi, I am quite stuck with a problem I encountered when using a timer connection in Vancouver. As soon as the unique IDs of the capabilities for RPC reach numbers >= 0x100000, RPC calls fail because of calls to invalid portal numbers. In my particular case, there are 4 portals created: [ 0] EC:0xc0019f00 SYS_CREATE PT:0x1a06 EC:0xa7 EIP:0x139950 [ 0] EC:0xc0019f00 SYS_CREATE PT:0x1a07 EC:0xa7 EIP:0x1398d0 [ 0] EC:0xc0019f00 SYS_CREATE PT:0x1a08 EC:0xa7 EIP:0x139950 [ 0] EC:0xc0019f00 SYS_CREATE PT:0x1a09 EC:0xa7 EIP:0x1398d0 In base/include/base/rpc_client.h, I inserted a debug statement showing that the "internal" portal being called is 0x82260. I think this is due to the translation between global capability selectors and NOVA portals, is that correct? When the internal IDs hit 0x100000, what happens is this: [ 0] EC:0xc0019f00 SYS_CREATE PT:0x30e6 EC:0xa7 EIP:0x139950 [ 0] EC:0xc0019f00 SYS_CREATE PT:0x30e7 EC:0xa7 EIP:0x1398d0 [ 0] EC:0xc0019f00 SYS_CREATE PT:0x30e8 EC:0xa7 EIP:0x139950 [ 0] EC:0xc0019f00 SYS_CREATE PT:0x30e9 EC:0xa7 EIP:0x1398d0 But the next event in NOVA is a call to portal number 0x100018, which doesn't exist because it was not created beforehand. It seems to me that from this point in time, the internal IDs are being used as NOVA portals somehow. But all I found was this unmarshalling method in base-nova/include/base/ipc.h: inline void Genode::Ipc_istream::_unmarshal_capability(Genode::Native_capability &cap) { long unique_id = 0; _read_from_buf(unique_id); int pt_sel = unique_id != ~0L ? _rcv_msg->rcv_pt_sel() : 0; cap = Native_capability(pt_sel, unique_id); } I put another debug instruction there and found out that rcv_pt_base was 0x100018, when the call failed. Right now I'm quite lost in all that RPC and Capability wrangling. Maybe someone can shed some light on this? How is that translation between internal IDs and NOVA portals done, anyway? Cheers Markus

2 5

I/O Memory Mapping failed
by Markus Partheymueller 30 Jul '12

30 Jul '12

Hi, I tried to boot a basic setup to test the USB driver with acpi on top of NOVA. But now at boot time, I get the following error: int main(): --- create local services --- int main(): --- start init --- int main(): transferred 3002 MB to init int main(): --- init created, waiting for exit condition --- start new pager object with EIP=0x1024ec4, ESP=0x6001000 start new pager object with EIP=0x1027444, ESP=0x6001000 start new pager object with EIP=0x101f0a4, ESP=0x6001000 start new pager object with EIP=0x1066044, ESP=0x6001000 start new pager object with EIP=0x1039584, ESP=0x6001000 [init -> vesa_drv] int Framebuffer_drv::map_io_mem(Genode::addr_t, Genode::size_t, bool, v0 start new pager object with EIP=0x102a704, ESP=0x6001000 start new pager object with EIP=0x1038ee4, ESP=0x6001000 start new pager object with EIP=0x1022714, ESP=0x6001000 [init -> launchpad] Could not open file "config" [init -> launchpad] Could not obtain config file [init -> acpi -> pci_drv] PCI driver started I/O memory [bf7fe000,bf800000) not available Local MMIO mapping failed! [init -> acpi] C++ runtime: Genode::Parent::Service_denied [init -> acpi] void* abort(): abort called The memory map looks as follows: Hypervisor info page contains 35 memory descriptors: Memory descriptor 1: 0 - 8f000 Memory descriptor 2: 8f000 - 90000 Memory descriptor 3: 90000 - 9d000 Memory descriptor 4: 9d000 - a0000 Memory descriptor 5: e0000 - 100000 Memory descriptor 6: 100000 - bf4bd000 Memory descriptor 7: bf4bd000 - bf4bf000 Memory descriptor 8: bf4bf000 - bf5c7000 Memory descriptor 9: bf5c7000 - bf7bf000 Memory descriptor 10: bf7bf000 - bf7df000 Memory descriptor 11: bf7df000 - bf7ff000 Memory descriptor 12: bf7ff000 - bf800000 Memory descriptor 13: bf800000 - c0000000 Memory descriptor 14: f8000000 - fc000000 Memory descriptor 15: fc000000 - fd000000 Memory descriptor 16: ffe00000 - 100000000 Memory descriptor 17: 4000000 - 43a0b95 Memory descriptor 18: 43a1000 - 4580547 Memory descriptor 19: 4581000 - 474c944 Memory descriptor 20: 474d000 - 4a55ab5 Memory descriptor 21: 4a56000 - 4a5cd2d Memory descriptor 22: 4a5d000 - 4a5d5ac Memory descriptor 23: 4a5e000 - 4bd06b6 Memory descriptor 24: 4bd1000 - 4de03d2 Memory descriptor 25: 4de1000 - 4f6bd5f Memory descriptor 26: 4f6c000 - 541c9e5 Memory descriptor 27: 541d000 - 55ae046 Memory descriptor 28: 55af000 - 57bfa8c Memory descriptor 29: 57c0000 - 5b575aa Memory descriptor 30: 5b58000 - 5d324e1 Memory descriptor 31: 5d33000 - 5f8763c Memory descriptor 32: 5f88000 - 6125c86 Memory descriptor 33: 6126000 - 627e07d Memory descriptor 34: 627f000 - 6742b89 Memory descriptor 35: 400000 - 1800000 What seems odd is that the range requested by the PCI driver (at least that would be my guess) lies partly in descriptor 11 (which is marked as not available in the HIP) and partly in descriptor 12 (which is available physical memory). Any ideas what could be the problem here? Cheers Markus

3 9

NOVA: remote revoke
by Alexander Boettcher 25 Jul '12

25 Jul '12

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello Udo, do you see any issues to extend the revoke syscall by a protection domain (pd) parameter ? Currently implicitly the current protection domain of the caller is used. With the extension the caller would have to specify explicitly the pd where the revoke operation should apply to. Genode core currently revokes all memory of the client pd subject to destruction. However core has no means to make sure that references to kernel objects are freed which creation has been issued by the client pd directly using the kernel syscalls. Additionally core can't make sure to revoke any mappings of memory, i/o ports and object capabilities which the client received via other channels (services/sessions provided not by core). The same issue also applies to NUL[0], where sigma0 can't clean up the object space of the vancouvers subject to destruction. With the remote revoke core and sigma0 in NUL would be able to make sure that all user level references inside a pd subject to destruction can be freed. Cheers, Alex. [0] http://os.inf.tu-dresden.de/nul -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAlAJCrAACgkQqjRK9KYzJbMfugCfTPyE5Y1Su9satcMLnP3erSVM L70AnjInjRnNJnGmCz3d2OjHRf7QnLgD =M4+6 -----END PGP SIGNATURE-----

3 12

VMware / VirtualBox demo?
by Mike Warot 23 Jul '12

23 Jul '12

I've reached the end of my Linux skill set trying to get the Build environment working in a Ubuntu 11.04 environment. (In a VM) on my Windows 7 box. I really, REALLY want to get up to speed on Genode (as I see it as the ONLY effective stop for all this silly "cyberwar" stuff, thanks to it's native support of capability based security). Is there somewhere I can download a VMware or VirtualBox image of it installed? -- Mike Warot Manager, Information Systems Live Marketing Office: (312) 237-3511 Cell: (219) 801-9272 Email: m.warot@...120...

3 4

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

users