users

users@lists.genode.org

6 participants
2306 discussions

measure execution time
by lzSun 16 Oct '18

16 Oct '18

Hello all, I have implemented a service in genode os which is based on tz_vmm demo on i.mx53-qsb board. Now I want to measure the execution time of the service. I measure the execution time both in linux and genode,but find a incredible result: 1. In linux, I record the start time t1 and end time t2 ,then I use t2-t1 to measure the execution time. 2. In genode, I get a timer use : Timer::Connection _timer(_env), and use _timer.elapsed_ms() to get the start and the end of the service time and use end-start to calculate the execution time. However, the result of the two world are far from each other. In linux, it's about 45 seconds, but in genode it's only about 11 seconds. I know, in linux side, it will first open the help module in kernel space and issue smc to switch to secure world and switch back when service is done. But I think it won't take such a long time.And actually, I think the execution is about 45 seconds which I observed from the start and end message. So I doubt there's problem with my measurement in genode. My settings: 1. In tz_vmm.run: add targets {drivers/timer} add <start name="timer"> <resource name="RAM" quantum="1M"/> <provides><service name="Timer"/></provides> </start> add boot_modules {timer} 2. In service file , server.cc: add #include <trace/timestamp.h> in funcion add: Timer::Connection _timer(_env); start=_timer.elapsed_ms(); Any help will be grateful, thanks! ------------------ Best wishes

1 0

FOSDEM 2019 - Microkernels developer room - CfP
by Sebastian Sumpf 11 Oct '18

11 Oct '18

FOSDEM 2019 - Microkernels and Component-based OSes devroom CALL FOR PARTICIPATION The developers of several free and open-source microkernel-based operating systems will meet at FOSDEM 2019 [1] in Brussels, Belgium and will share a developer room on Sunday February 03, 2019 [2]. The devroom is currently looking for content in the form of talks and activities related to the area of microkernel-, unikernel-, and componenent-based operating systems. Possible topics include, but are not limited to: * introduction of a specific OS or framework * design of subsystems and the general architecture of an OS * enabling support for hardware (architectures, device drivers) * used languages and tools * maintenance and testing * security and robustness * trends and challenges * use cases, experiences, lessons learned and demos Please use the Pentabarf [3] system to submit your proposals. You do not need to create a new account if you already have one. When in doubt, please use the devroom mailing list [4]. If you do not want to give a talk yourself, you may still send suggestions for what else you would like to see, or do in the devroom. Please send your suggestions to the mailing list. The deadline for your proposal is on December the 1st 2018. Make sure to include the following in your proposal: * title of your talk (will be printed in the FOSDEM booklet) * your full name (will be printed in the FOSDEM booklet) * a short abstract (one or two paragraphs) * duration of your talk (please, at least 25 and no longer than 55 min) The official devroom schedule (along with the accepted talks) will be announced on December the 15th on the devroom's mailing list and the speakers will be notified via e-mail. The schedule will also be published on the FOSDEM website. About FOSDEM FOSDEM is a two-day event organised by volunteers to promote the widespread use of free and open source software. Taking place in the beautiful city of Brussels (Belgium), FOSDEM is widely recognised as the best such conference in Europe. FOSDEM covers a wide spectrum of free and open source software projects, and offers a platform for people to collaborate. To this end, FOSDEM has set up developer rooms (devrooms) with network/internet connectivity and projectors where teams can meet and showcase their projects. Devrooms are a place for teams to discuss, hack and publicly present latest directions, lightning talks, news and discussions. Besides developer rooms, FOSDEM also offers main tracks, lightning talks, certification exams and project stands. Every year, FOSDEM hosts more than 5000 developers at the ULB Solbosch campus. Participation and attendance is totally free, though the organisers gratefully accept donations and sponsorship. No registration necessary. About the devroom Since the first Microkernel devroom in 2012 this devroom has been part of each following FOSDEM. By now it has become a somewhat institutionalized tradition for the micro kernel community to meet there; to this date over a dozen projects have participated in one way or another. Each of the projects face similar challenges but come up with partially different solutions. Therefore, the goal of the Microkernel devroom is to bring the various projects together, let them exchange ideas, cross-pollinate and socialize. Social events It also has become a habit that the microkernel projects dine together somewhere in Brussels. The year 2019 will not be any different, so there is going to be a microkernel family dinner on Saturday night. We try place a reservation, so we will inform you about the exact location and time later. Consult the FOSDEM web and other projects for additional social events such as the famous FOSDEM-organized Friday Beer Event and the FOSDEM-arranged free sightseeing tours for spouses. Important dates recap * 01.12.2018: Deadline for submissions * 15.12.2018: Schedule published and speakers notified of acceptance * 03.02.2019: The devroom takes places Links [1] http://fosdem.org [2] https://fosdem.org/2019/practical/transportation [3] https://penta.fosdem.org/submission/FOSDEM19 [4] https://lists.fosdem.org/listinfo/microkernel-devroom See you all at FOSDEM!

1 0

VirtualBox Guest Additions
by John J. Karcher 04 Oct '18

04 Oct '18

Hello Everyone, One of the top items on my personal Genode wish list is the VirtualBox Guest Additions. I have never ported a serious software project across platforms (and am not a Genode expert - yet), so I am not the best person for the job. But it is a personal "itch", so I will dig in and do my best if no one else is already working on it. Below I will briefly share what I have discovered in my limited research. Any advice or insight would be greatly appreciated. To make a long story short, I have only found 3 useful sources of information about porting the Guest Additions: 1. The source code from the VirtualBox project itself [1] 2. A page on the OSDev wiki [2] 3. An e-mail on the VBox-Dev mailing list [3] If anyone is aware of any more info, please let me know. To make a long story short, the interface to the VirtualBox host is through a virtual PCI device (using IRQ and MMIO). Once this interface is in place, the various pieces (e.g. time sync, shared folders, etc.) can be added individually. There are several ports of the Guest Additions in the VirtualBox source tree, and they share a lot of common code, but there doesn't seem to be a common skeleton among the OS-specific parts of the code. On the other hand, the OSDev page takes a minimalist, low-level approach. This is probably the general path I will follow, at least to start. [1] https://www.virtualbox.org/browser/vbox/trunk/src/VBox/Additions [2] https://wiki.osdev.org/VirtualBox_Guest_Additions [3] https://www.virtualbox.org/pipermail/vbox-dev/2007-July/005860.html Wish me luck! -- John J. Karcher devuser(a)alternateapproach.com

1 0

Sculpt VC Depot Configuration
by John J. Karcher 02 Oct '18

02 Oct '18

Hello Everyone, I may be missing something obvious, but I can't find where to add a new depot to a Sculpt VC instance (for run-time installation). Can this be configured at run-time? Thanks! -- John J. Karcher devuser(a)alternateapproach.com

3 4

NOVA spinner and trace
by Nobody III 01 Oct '18

01 Oct '18

I've tried replacing novga with spinner in the NOVA command line (in tool/run/boot_dir/nova), but nothing happens. What do i have to do to enable IRQ spinners? Also, when I enable TRACE_APIC or TRACE_ACPI in stdio.hpp in the NOVA contrib source, the kernel crashes and QEMU gets stuck in a boot loop. How can I add this trace information to the serial log and/or log_core?

2 1

timestamp value too big
by lzSun 28 Sep '18

28 Sep '18

Hello, I have implemented a service in Genode OS based on tz_vmm demo on i.mx53-qsb. And I want to measure the performance of my service. I have included the "timer driver" in my Genode OS and added the 'perf_counter' to specs.conf file. Because my service implementation include some C language files, so I use 'gettimeofday()' function to get time in .c files. However, when the system running, it prints "Warning: timestamp value too big" many times. And the results is incorrect: I measure several period of the service, some of the period is quite long(about 30 seconds I observe from the print message, I know this is inaccuracy but I think it will not far from the actual execution time ) but the calculate time interval is about 9 seconds. Also, I use elapsed_time() function at the beginning(t1) and the ending(t2) of the service respectively, and t2-t1 is about 19193 ms, while I use time command to measure in linux is about 1m19s. At the side of linux, I just open my help module to use SMC to request my service in Genode OS and get back while the service is done, so I think the linux measure time will not far from the service excution time. So my question is, how can I measure quite long time period in the Genode ? It seems the method I used above to measure time is inaccurate. ------------------ Best wishes

1 0

Re: Increase VM memory size
by lzSun 27 Sep '18

27 Sep '18

>Hi, >it crossed my mind, if you do not need more than half of the memory >(512 MiB) inside Linux, you can easily assign the second memory bank >to the non-secure guest without further adaptions. Here is a patch: >diff --git a/repos/base-hw/include/spec/imx53/drivers/trustzone.h >b/repos/base-hw/include/spec/imx53/drivers/trustzone.h >index 8a65fea02..0f8d51b4c 100644 >--- a/repos/base-hw/include/spec/imx53/drivers/trustzone.h >+++ b/repos/base-hw/include/spec/imx53/drivers/trustzone.h >@@ -28,8 +28,8 @@ namespace Trustzone >*/ > SECURE_RAM_BASE = Imx53::RAM_BANK_0_BASE, >SECURE_RAM_SIZE = 256 * 1024 * 1024, >- 256NONSECURE_RAM_BASE = Imx53::RAM_BANK_0_BASE + SECURE_RAM_SIZE, >- RAM_BANK_0_BASENONSECURE_RAM_SIZE = 256 * 1024 * 1024, >+ 256NONSECURE_RAM_BASE = Imx53::RAM_BANK_1_BASE, >+ Imx53NONSECURE_RAM_SIZE = 512 * 1024 * 1024, > }; > } >Please keep in mind to *not* increase the secure ram area. It needs to >be protected by the M4IF TrustZone aware IP core, which is somehow >limited in its configuration of secure address ranges. >Regards >Stefan Hi, Thank you Stefan, It works for me now!

1 0

Increase VM memory size
by lzSun 27 Sep '18

27 Sep '18

hello, I have written an email about to increase the tz_vmm demo's memory size before, but haven't get any answer yet. The thing is, I want to increase the memory size that linux in the normal world can use. During these days, I found the related file which is at " /genode/repos/base-hw/include/spec/imx53/drivers/trustzone.h " . In this file I found the NONSECURE_MEMORY_SIZE = 256*1024*1024. So I increase this size to 512*1024*1024, however, when the system booting, it print the error message like: [init -> tz_vmm] Start virtual machine ... [init -> tz_vmm] Error: failed to handle data abort [init -> tz_vmm] Cpu state: [init -> tz_vmm] Register Virt Phys [init -> tz_vmm] ------------------------------------ [init -> tz_vmm] r0 = 0xc0888294 0x80888294 [init -> tz_vmm] r1 = 0x00000000 0x00000000 [init -> tz_vmm] r2 = 0x00000020 0x00000000 [init -> tz_vmm] r3 = 0xd5001000 0x95001000 [init -> tz_vmm] r4 = 0xc0c28000 0x80c28000 [init -> tz_vmm] r5 = 0xd50000c0 0x950000c0 [init -> tz_vmm] r6 = 0xc0888294 0x80888294 [init -> tz_vmm] r7 = 0xd50000a0 0x950000a0 [init -> tz_vmm] r8 = 0xd5000000 0x95000000 [init -> tz_vmm] r9 = 0x00000000 0x00000000 [init -> tz_vmm] r10 = 0x00000000 0x00000000 [init -> tz_vmm] r11 = 0xffffffff 0x00000000 [init -> tz_vmm] r12 = 0x00000001 0x00000000 [init -> tz_vmm] sp = 0x00000000 0x00000000 [init -> tz_vmm] lr = 0x00000000 0x00000000 [init -> tz_vmm] ip = 0xc00cde10 0x800cde10 [init -> tz_vmm] cpsr = 0x60000093 0x00000000 [init -> tz_vmm] sp _und = 0xc08e59d8 0x808e59d8 [init -> tz_vmm] lr _und = 0xc08e59d8 0x808e59d8 [init -> tz_vmm] spsr _und = 0x00000000 0x00000000 [init -> tz_vmm] sp _svc = 0xc0887f30 0x80887f30 [init -> tz_vmm] lr _svc = 0xc00cddf0 0x800cddf0 [init -> tz_vmm] spsr _svc = 0x00000000 0x00000000 [init -> tz_vmm] sp _abt = 0xc08e59cc 0x808e59cc [init -> tz_vmm] lr _abt = 0xc08e59cc 0x808e59cc [init -> tz_vmm] spsr _abt = 0x00000000 0x00000000 [init -> tz_vmm] sp _irq = 0xc08e59c0 0x808e59c0 [init -> tz_vmm] lr _irq = 0xc08e59c0 0x808e59c0 [init -> tz_vmm] spsr _irq = 0x00000000 0x00000000 [init -> tz_vmm] sp _fiq = 0x00000000 0x00000000 [init -> tz_vmm] lr _fiq = 0x00000000 0x00000000 [init -> tz_vmm] spsr _fiq = 0x00000000 0x00000000 [init -> tz_vmm] ttbr0 = 0x80004019 [init -> tz_vmm] ttbr1 = 0x80004019 [init -> tz_vmm] ttbrc = 0x00000000 [init -> tz_vmm] dfar = 0xc088829c 0x8088829c [init -> tz_vmm] exception = data_abort Did I missed something ? Any help will be grateful, thanks a lot! ------------------ Best wishes

2 2

Sculpt OS with Visual Composition (VC)
by Norman Feske 26 Sep '18

26 Sep '18

Hello everyone, we just published the third official version of Sculpt OS: https://genode.org/download/sculpt This version - called Sculpt with Visual Composition (VC) - introduces a novel graphical user interface for the interactive deployment of subsystems. For the first time, Sculpt can be explored without editing any text files. Furthermore, the new version increases the compatibility with modern hardware thanks to the vast device-driver improvements of Genode 18.08. Sculpt VC is available as ready-to-use disk image and is accompanied with updated documentation: https://genode.org/documentation/articles/sculpt-vc I wish you a lot of fun with exploring the new version! Cheers Norman -- Dr.-Ing. Norman Feske Genode Labs https://www.genode-labs.com · https://genode.org Genode Labs GmbH · Amtsgericht Dresden · HRB 28424 · Sitz Dresden Geschäftsführer: Dr.-Ing. Norman Feske, Christian Helmuth

4 4

Questions about genode os from a prospective user (moving from Qubes)
by Mr Oxide 24 Sep '18

24 Sep '18

I am a former qubes user. Currently on Linux MInt. Thinking of moving to Genode. Questions are (and this is for the Nova kernel with VirtualBox): 1. Can you assign PCI device hardware to virtual machines? 2. Can VMs be networked to each other? My idea with qubes was to setup an HVM with a dedicated HBA card and then install freenas within it. I would then use this as a nas for all of my vms to share. Is this possible with genode? 3. Is there anything that is not compatible (compared to qubes os)? 4. How is net security in dom0? In qubes os there is no dom0 networking.

2 1

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

users