users

users@lists.genode.org

7 participants
2332 discussions

Defence of "Microkernelization of Linux"
by Johannes Kliemann 13 May '18

13 May '18

Hello Genode folks, I want to invite you to the defence of my student thesis "Microkernelization of Linux" (and enabling native Genode driver support on base-linux). It will take place in the Andreas-Pfitzmann-Bau room 3105 at 11:00. Regards, Johannes Kliemann

2 4

*****SPAM***** sculpt: sned ACPI power off to guest machine
by Duss Pirmin 11 May '18

11 May '18

Spam detection software, running on the system "obelix.duss.local", has identified this incoming email as possible spam. The original message has been attached to this so you can view it or label similar future email. If you have any questions, see root@...233... for details. Content preview: Hello Is there a way to send an ACPI power off event to a running guest to shut it down? I searched the issues and wasn't able to find anything about it. Content analysis details: (8.7 points, 5.5 required) pts rule name description ---- ---------------------- -------------------------------------------------- 2.9 HELO_DYNAMIC_SPLIT_IP Relay HELO'd using suspicious hostname (Split IP) 0.2 CK_HELO_GENERIC Relay used name indicative of a Dynamic Pool or Generic rPTR 0.0 RCVD_IN_SORBS_DUL RBL: SORBS: sent directly from dynamic IP address [83.77.14.147 listed in dnsbl.sorbs.net] 3.6 RCVD_IN_PBL RBL: Received via a relay in Spamhaus PBL [83.77.14.147 listed in zen.spamhaus.org] 1.6 RCVD_IN_BRBL_LASTEXT RBL: No description available. [83.77.14.147 listed in bb.barracudacentral.org] 0.4 RDNS_DYNAMIC Delivered to internal network by host with dynamic-looking rDNS

1 0

interrupts on AMD hardware
by Nobody III 06 May '18

06 May '18

Has anyone gotten any Genode drivers to work on computers with AMD processors? The only one that I've gotten to work was fb_drv, which doesn't need to receive interrupts. The other 2 drivers that I've tried recently, usb_drv and ahci_drv, both hang. Has anyone had better compatibility here?

5 16

remaining issues
by Nobody III 06 May '18

06 May '18

There are some remaining issues that should be fixed before the 18.05 release, but aren't receiving much attention: init requires double quotas when running under sequence #2755 <https://github.com/genodelabs/genode/issues/2755> (init should request quota upgrades when needed) nit_fb: add optional transparency #2728 <https://github.com/genodelabs/genode/issues/2728> (less important, but just needs to be merged) Framebuffer has_alpha() function #2723 <https://github.com/genodelabs/genode/issues/2723> Noux: rmdir dir/ (trailing slash) does not work #2686 <https://github.com/genodelabs/genode/issues/2686> Multiple rump-backed file-systems not supported by VFS library #2681 <https://github.com/genodelabs/genode/issues/2681> Additional pixel format support #2045 <https://github.com/genodelabs/genode/issues/2045> (important for a library i'm writing; just needs to be merged) All of these should be fairly easy fixes, and at least 2 already have patches that just need to be merged.

2 1

Closing laptop lid disables nitpicker focus/input functions
by Boris Mulder 04 May '18

04 May '18

Hi all, I experienced an issue while closing the laptop lid on some hp840 machines. I know you have not tested these laptops, but the behaviour is really curious, so maybe you know better what might be going on. * I am running the sculpt scenario from staging. Everything works fine, until I close and open the lid of the laptop. * When I reopen it, the current focused window still does its job. However, when I switch the focus, for example by triggering the leitzentrale on and off by pressing F12, nothing happens. * I tried setting the report_rom to verbose. It shows the global_keys_handler -> leitzentrale report is not updated by pressing F12. However, in my leitzentrale window which is still active I can type things, execute programs and view the log. * This happened when the leitzentrale was on before I put the lid down and up. * When I put the leitzentrale off and focus my runtime (which is just the fs runtime with a noux shell) before closing and opening the lid, it also cannot change the focus and only the client that was focused before closing the lid (the noux shell) receives input. F12 again does nothing. * In fact I tried it with more complicated runtimes and all the time only the component which had focus (in this case the leitzentrale) still works, the other components cannot get focus or input events. * Report_rom does not give me a focus-, hover-, or any other report when I press a global key, hover over or click on any component, including the focused component. For example, when I have leitzentrale active, the log does not show any report updates when I click or move the mouse. Starting and stopping a runtime works fine, and the runtime gives a nice focus report (if I had focused that runtime before). But pressing F12 does not disable the leitzentrale_enabled flag (or gives any useful output). * It happens both with the intel_fb_drv and the vesa driver. It does not happen on a lenovo x250. Somehow it seems that nitpicker fails to detect any input events (whether from a USB device or the embedded ps2 pad+keyboard), though it forwards those events that belong to the focused client correctly. What could cause this? What happens in the Genode components in the GUI stack when the lid is opened or closed? When I run linux on that laptop I can close and open it just fine. -- Met vriendelijke groet / kind regards, Boris Mulder Cyber Security Labs B.V. | Gooimeer 6-31 | 1411 DD Naarden | The Netherlands +31 35 631 3253 (office)

1 0

acpica issues
by Boris Mulder 25 Apr '18

25 Apr '18

Hi all, I tried diving into the acpica utility to check if I can make the state reports work on some of our machines. Currently I am testing it on the lenovo x250 and the hp 840 laptops. However, I am not sure how and if to proceed here. The current behaviour is as following: When the machine starts up, it produces the reports of acpi_ac and acpi_battery correctly. When I disconnect the power outlet, these reports do not get updated. instead, I do get acpi_ec report updates on some of the different events, such as connecting and disconnecting the laptop to AC. These events have different values on the different laptops. The ec report acpica produces on the hp840: [init -> acpi_report_rom] report 'acpica -> acpi_ec' [init -> acpi_report_rom] <acpi_ec> [init -> acpi_report_rom] <ec> [init -> acpi_report_rom] <data value="8" count="36">triggered</data> <-- this is added on a charge up event (it seems to trigger periodically when the battery is not full and AC is connected [init -> acpi_report_rom] <data value="9" count="53"/> <-- this is added on a charge down event (it seems to trigger periodically when the battery is not full) [init -> acpi_report_rom] <data value="6" count="2"/> <-- AC connect/disconnect event (this triggers once when disconnecting and once when connecting) [init -> acpi_report_rom] </ec> [init -> acpi_report_rom] </acpi_ec> on the x250: [init -> acpi_report_rom] report 'acpica -> acpi_ec' [init -> acpi_report_rom] <acpi_ec> [init -> acpi_report_rom] <ec> [init -> acpi_report_rom] <data value="38" count="1">triggered</data> <-- AC disconnect event (this triggers once when disconnecting) [init -> acpi_report_rom] <data value="77" count="1"/> <-- AC connect event (this triggers once when connecting) [init -> acpi_report_rom] <data value="39" count="1"/> <-- AC connect event (this also triggers once when connecting) [init -> acpi_report_rom] </ec> [init -> acpi_report_rom] </acpi_ec> Some observations: * The charge/discharge events do not work on the x250. * On the hp840 connecting and deconnecting share the same data value. * On both laptops, disconnecting and reconnecting the AC outlet only triggers the ec report once, and doing it again does not produce a report. Reconnecting AC a second time also seems to cause the charge events to stop being reported on the hp840. * The lid report only works on the hp840. * The power button works on the hp840 and only works on the x250 if you press it for a longer time (but not so long as to turn off the device). * Ideally, for some device, such as one of the above, we would like all of these reports to be updated correctly. I have some questions about this: * You mentioned in your issue about sculpt EA that the reports not getting updated are a known issue. Do you have any plans of fixing this in the future? * Do you think solutions to this issue are going to be device specific? Which parts are generally the same for different laptops? * Is the difference in handling of the events on these machines caused by the acpica C code not supporting these machines, or by the Genode code not supporting them? or both? * A workaround could be installing a timer and generating the initial reports periodically. Do you think this would be worth implementing or would fixing the problem be easier? * For device specific parts: suppose it works on your test setup, how should we proceed to make it work on other hardware? -- Met vriendelijke groet / kind regards, Boris Mulder Cyber Security Labs B.V. | Gooimeer 6-31 | 1411 DD Naarden | The Netherlands +31 35 631 3253 (office)

2 1

SMC Calls in Trustzone VMM Scenario
by Mauricio Gutierrez 23 Apr '18

23 Apr '18

Hello, I have been doing some work with the Genode Trustzone VMM scenario on my i.MX53 development board and I am having a bit of trouble understanding how the SMC calls work between the normal and secure world. Online you talk about how you implemented 6 calls in the modified normal world linux kernel but in the main for the tz_vmm I only found 4 different cases in the _handle_smc() function. In any case, I wanted to add my own call and was able to add it and check that the required arguments are passed correctly and everything so that part I think I understand. However, I need to do some of the handling in Monitor Mode and my understanding was that an SMC would throw your into monitor mode but it seems the handler operates in user mode? Since it is not privileged then I am not able to call a "cps #22" to switch to monitor mode. In an earlier thread I know you refer to the section "World switch between non-secure world and secure > world" in http://genode.org/documentation/articles/trustzone. But I am still uncertain as to how I could get my case in _handle_smc() to enter monitor mode so that I can play around with the NS bit without leaving secure world. I have been studying what happens when I call an smc, say "smc #4" from normal world. But I have not been able to exactly pin point, where is the entry point for such an exception in the Genode secure world call? What exactly happens once I make that call to secure world and where I can I find/follow the code? Is this covered somewhere in your book? I know about the mode_transitions.s file as well as the exception_vector.s and vm.cc files in repos/base-hw/src/core/spec/arm_v7/trustzone, it seems this is the entry point? But where does it go after we call the nonsecure_to_secure transition? Most importantly, I need to understand where is the code operating in monitor mode? Where does it end and where does it start? How can I tell? If I needed to write at least some part of my smc handler in monitor mode before it switches out, what is the best approach to doing that? I apologize for all the questions and would appreciate any help and guidance you can provide. Thank you, Mauricio

2 5

waiting for RPC method to be called
by Nobody III 22 Apr '18

22 Apr '18

How do I get a component to wait for an RPC method to be called? Can I use a semaphore, or will that block RPC calls? Do I need a thread dedicated to handling RPC? If so, should I create a new Rpc_entrypoint and tell it to manage the Rpc_object?

2 2

Genode::Slave::Policy::resolve_session_request() should be virtual
by Nobody III 20 Apr '18

20 Apr '18

Currently, Genode's Slave API is designed to create child components and request services from them. However, it does not allow the parent component to provide services to the child. Making Genode::Slave::Policy::resolve_session_request() virtual would fix this.

1 0

block device
by Duss Pirmin 20 Apr '18

20 Apr '18

Hello all I have a notebook with two relatively small SSDs. To use the sculpt scenario on it, I would like to use the two as one in a RAID 0 configuration. Is there already a possibility to do this, or should I implement a block device merger component that can be configured to join up multiple block sessions in to one? Best regards Pirmin

2 1

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

users