- l4-hackers - example.com Site

some questions about l4bd.c in l4linux
by yadong.li 20 Feb '19

20 Feb '19

Hi Adam， I am studying how to support emmc storage in L4Re. I have read the file l4linux/drivers/block/l4bd.c. I have some questions 1、 In “l4linux/drivers/block/l4bd.c”, I can’t find the function implementation of “l4fdxc_request_write” and some with prefix l4fdxc in l4linx or l4， is there some demos? 2、 If it is implemented by ourselves, where is more reasonable to place “l4fdxc_request_write” , in l4 or l4linux ? 3、 If in l4, Which implementation is more reasonable , lib or server? Thank you very much

2 1

Communication between L4Linux tasks and L4re tasks
by Canberk Demirsoy 17 Feb '19

17 Feb '19

Dear Developers, I have a simple question regarding the communication of L4Linux and L4re. I have already read previous entries but could not solve my problem. I am able to establish a communication between the tasks in L4re, but what I need is communication between a task that is running on L4Linux and a task that is running on L4re. How can I do this in simplest way? Any suggestions? Best Regards *Canberk*

2 1

Poll for Separation Kernel (microkernel) CC Protection Profile
by Holger Blasum 20 Jan '19

20 Jan '19

Hello l4-hackers, microkernel-based systems can be used as separation kernels[*] for security. At the moment there is a poll on input for a Common Criteria for Information Technology Security (CC) separation kernel protection profile draft, organized by a certMILS.eu colleague from Rostock Univ, at https://evasys.uni-rostock.de/evasys/online.php?p=ccuf-sk-wg The idea is to have a base protection profile (PP) that all players can agree with and to specify additional functionality as add-ons to the PP (e.g., in the form of PP modules). The questionnaire is an opportunity to provide early feedback. Note that there are no mandatory questions, i.e. you can freely move around / you can leave any question unanswered - the only condition for your feedback be submitted to the collection system is that you go to the last page and use the submit button there. We invite feedback via that poll by end of this week. If, beyond the questionnaire, you want to join the Common Criteria User's Forum separation kernel working group, or anyone would like to have more time, just let me know by answering to this email. [*] https://en.wikipedia.org/wiki/Multiple_Independent_Levels_of_Security Best, -- Holger Blasum, SYSGO

1 1

QEMU advent calendar
by Matthias Lange 21 Dec '18

21 Dec '18

Hi, today we have another small treat for those interested in L4Re. You should check door 21 [1] of the QEMU advent calendar for a peek on what you can build with our newly released #L4Re projects. Happy holidays! Matthias. [1] https://www.qemu-advent-calendar.org/2018/#day-21 -- Matthias Lange, matthias.lange(a)kernkonzept.com, +49-351-41 888 614 Kernkonzept GmbH. Sitz: Dresden. Amtsgericht Dresden, HRB 31129. Geschäftsführer: Dr.-Ing. Michael Hohmuth

1 0

New L4Re projects released
by Matthias Lange 20 Dec '18

20 Dec '18

Dear L4 folks, as the year is slowly coming to an end we want to take the opportunity to announce the release of new L4Re projects to our github [1]. This release includes the development version of our small virtual machine monitor uvmm [2]. It is capable of running Linux on all three of L4Re's supported architectures. Another noteworthy project is io [3] which is our IO device multiplexing and virtualizing component. To get you started we added a new tutorial [4] on how to setup and run a Linux VM on L4Re. We hope you enjoy the new release and we love to hear what you think. Happy holidays! Matthias. [1] https://github.com/kernkonzept [2] https://github.com/kernkonzept/uvmm [3] https://github.com/kernkonzept/io [4] https://github.com/kernkonzept/manifest/wiki/LinuxVM -- Matthias Lange, matthias.lange(a)kernkonzept.com, +49-351-41 888 614 Kernkonzept GmbH. Sitz: Dresden. Amtsgericht Dresden, HRB 31129. Geschäftsführer: Dr.-Ing. Michael Hohmuth

1 0

UEFI L4 image?
by Peter Wiehe 26 Nov '18

26 Nov '18

Hello, can you give me a link to an UEFI flat PE image of L4Re? If that's not available, then perhaps a link to instructions how to produce one myself? Kind regards Peter

2 4

UEFI
by Peter Wiehe 23 Nov '18

23 Nov '18

Hi everybody! Is it possible to run L4 on UEFI? Kind regards Peter Wiehe

2 1

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

12 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!

2 1

Information on implementing L4
by John 05 Oct '18

05 Oct '18

Hi all. I've been looking at Google and Wikipedia for information about L4, and it's fairly thin. I've come up with that L4 has read and write registers and performs IPC by fixed-length registers, with all actions synchronous (I guess that means you send a message and block until the target thread reads the message). Is there a more concrete document anywhere about implementing an L4 microkernel and what makes it L4? I'm surveying the field at the moment and looking at all the advances made in computer software—security, managed language runtimes, hypervisors, real-time OS—and trying to project the possibilities for a next-generation operating system. There's enough divergence that a rewrite from scratch might make sense; and besides, I've drawn up a method for getting a self-hosting CLR running with only anonymous memory allocation and VFS file page mapping, along with a method of getting the CLR to self-host and getting it up and running before an actual OS kernel. In other words: it's readily-achievable to write a CLR in C#, get it running on itself before the kernel comes up, then load a kernel, VMM, VFS, ABI, scheduler, and so forth—all written in C#, compiled to CIL, and totally independent of the hardware architecture underneath—and then throw away the loader and bring up init. The kernel would need to use an abstract factory model to do common tasks which require hardware-specific code, and the CLR would need to load an assembly with a concrete factory for the particular hardware and a few built-in native assembly calls; but it's doable. This is all theoretical at the moment, and I want to explore the particular edges a little to see what I find out.

7 32

OS/Microkernel Engineers Wanted!
by Osman Ismael 02 Oct '18

02 Oct '18

[Apology for the shameless ad, but might be of interest to some] BedRock Systems is a stealth startup with a global team. Our platform is based upon cutting-edge technology, including the latest generation of L4 microkernel, and leverages the next level of development methodologies and tools. We were founded by industry veterans who built large successful companies from scratch. Our top-notch team is a mixture of the best from industry and academia. Come transform the computing landscape. Join us at www.bedrocksystems.com <http://www.bedrocksystems.com/>. BedRock Systems Engineering team.

1 0

Call from 8-bytes aligned stack to functions that require 16-bytes stack alignment
by Yuxuan Shui 25 Sep '18

25 Sep '18

Hi, L4Linux is compiled with -mpreferred-stack-boundary=3, but the "external functions" it calls are usually compiled without this option, so defaults to 16 bytes alignment. This causes potential unaligned memory access if the compiler choose to generate instructions like movdqa. QEMU without kvm seems to just let this pass, but with kvm enabled, this could generate a GP. -- Regards Yuxuan Shui

1 0

RE: Issues about server multi-threading on L4Re
by 李鼎基 21 Sep '18

21 Sep '18

Oh yes! Actually I used the version without arguments. Now I think I can try to fix this problem with the constructor with arguments. Thank you very much! From: Jakub Jermar<mailto:jakub.jermar@kernkonzept.com> Sent: Friday, September 21, 2018 23:12 To: 李鼎基<mailto:lidingji1997@hotmail.com> Subject: Re: Issues about server multi-threading on L4Re On 09/21/2018 05:02 PM, 李鼎基 wrote: > Actually, I’ve tried to run the server loop in only one thread (a new > thread created by “pthread_create”, NOT the main thread) on server. > > Theoretically, it should perform the same as running the server loop in > the main thread, but the server still gets stuck. How did you create your Object_registry / Registry_server - there is a version for the main thread which has constructor without arguments [0] and uses the main thread - and then there is a version with a constructor that takes arguments [1], among which is a server thread. You need to use the second version to tell it about your new thread. Can it be that you are using the version without arguments? [0] https://l4re.org/doc/classL4Re_1_1Util_1_1Registry__server.html#a694a009623… [1] https://l4re.org/doc/classL4Re_1_1Util_1_1Registry__server.html#ad88c4355e6… HTH, Jakub > > ------------------------------------------------------------------------ > *发件人:* l4-hackers <l4-hackers-bounces(a)os.inf.tu-dresden.de> 代表 > Jakub Jermar <jakub.jermar(a)kernkonzept.com> > *发送时间:* Friday, September 21, 2018 10:26:12 PM > *收件人:* l4-hackers(a)os.inf.tu-dresden.de > *主题:* Re: Issues about server multi-threading on L4Re > > Hi there! > > On 09/21/2018 02:10 PM, 李鼎基 wrote: >> I’m trying to implement some multi-threading IPC benchmarks on L4Re. >> Following the /“shared_ds”**/demo, firstly, I create 8 threads to send >> IPC on client and receive them all on server’s main thread. >> >> The server loops, waits for the requests and handles them in the >> “dispatch” function. This single-thread server works well. >> >> >> >> Then I want to create 8 threads in server (so that it can serve the >> client thread-to-thread). >> >> I wrap the “server.loop();” in a “thread_fn” and use “pthread_create” to >> create more threads, however, the server will get stuck. >> >> There are some printings after entering thread_fn so that I can make >> sure new threads are created and executed except the server.loop part. > > I guess the problem is in that you are trying to use the same server > loop for all your threads. The server loop is associated with a single > server thread that executes the server objects. In other words, all but > the thread which is associated with your server loop just block there > and don't receive any IPC calls. > >> In order to serve different requests concurrently, is there any way to >> create a multi-threading server? > > In theory (never tried that myself), you can try giving a separate > server loop to each of your threads. You will then need to register your > server object at each of them. The end result should be that your client > threads are each connected to a different IPC gate which has its own > bound server thread. All of these gates carry the label of the same > server object which will be invoked when an IPC call arrives at any of them. > > HTH, > Jakub > > -- > Kernkonzept GmbH at Dresden, Germany, HRB 31129, CEO Dr.-Ing. Michael > Hohmuth > > _______________________________________________ > l4-hackers mailing list > l4-hackers(a)os.inf.tu-dresden.de > http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers -- Kernkonzept GmbH at Dresden, Germany, HRB 31129, CEO Dr.-Ing. Michael Hohmuth

1 0

Issues about server multi-threading on L4Re
by 李鼎基 21 Sep '18

21 Sep '18

Hi, I’m trying to implement some multi-threading IPC benchmarks on L4Re. Following the “shared_ds” demo, firstly, I create 8 threads to send IPC on client and receive them all on server’s main thread. The server loops, waits for the requests and handles them in the “dispatch” function. This single-thread server works well. Then I want to create 8 threads in server (so that it can serve the client thread-to-thread). I wrap the “server.loop();” in a “thread_fn” and use “pthread_create” to create more threads, however, the server will get stuck. There are some printings after entering thread_fn so that I can make sure new threads are created and executed except the server.loop part. In order to serve different requests concurrently, is there any way to create a multi-threading server? -- Thanks

2 1

High 32 bits of SFMASK is reserved
by Yuxuan Shui 20 Sep '18

20 Sep '18

Hi, In cpu-64.cpp, in function Cpu::setup_sysenter, Fiasco try to set IA32_FMASK (called MSR_SFMASK in the code) to ~0ULL. However, only the lower 32bit of FMASK should be written to. This cause problems on some platforms. -- Regards Yuxuan Shui

3 2

cost (cycles + cache) of setup and use of IPC mechanisms
by Zenaan Harkness 17 Sep '18

17 Sep '18

Establishing any IPC communication channel has setup costs and per message or per "message batch" usage costs: (CPU cycles + context switches) / channel setup (CPU cycles + context switches) / msg[-batch] Further, as recent Linux kernel network stack work has discovered, cache effects strongly proscribe batch processing rather than per-msg (or per packet) processing (seems obvious, I guess "in hindsight") to make 10G and above network links work well: Batch processing of network packets https://lwn.net/Articles/763056/ and see also: User-space networking with Snabb https://lwn.net/Articles/713918/ Is there a paper quantifying and comparing various IPC mechanism costs? Specifically and separately, is there a paper quantifying the setup and use costs of shared memory IPC (possibly in comparison with any other IPC mechanism)? TIA,

1 1

L4linux booting problem on IMX.6 based board
by diming.zhang＠gmail.com 04 Sep '18

04 Sep '18

Hi, I'm working on building L4linux for my imx.6 arm-board. But the booting stopped before the l4linux console coming out. The logs is as follows: U-Boot 2015.04-imx_v2015.04_3.14.52_1.1.0_ga+g6cf684a (Sep 01 2018 - 05:09:24) CPU: Freescale i.MX6Q rev1.5 at 792 MHz CPU: Temperature 33 C Reset cause: POR Board: MX6-SabreSD I2C: ready DRAM: 1 GiB MMC: FSL_SDHC: 0, FSL_SDHC: 1, FSL_SDHC: 2 *** Warning - bad CRC, using default environment No panel detected: default to Hannstar-XGA Display: Hannstar-XGA (1024x768) In: serial Out: serial Err: serial switch to partitions #0, OK mmc2(part 0) is current device Net: FEC [PRIME] Error: FEC address not set. Normal Boot Hit any key to stop autoboot: 1 0 reading l4linux.uimage 10982764 bytes read in 291 ms (36 MiB/s) ## Booting kernel from Legacy Image at 11000000 ... Image Name: L4 Image #51 Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 10982700 Bytes = 10.5 MiB Load Address: 11000000 Entry Point: 11000000 Verifying Checksum ... OK Loading Kernel Image ... OK Starting kernel ... L4 Bootstrapper Build: #51 Mon Sep 3 02:20:50 CST 2018, 7.3.1 20180425 [linaro-7.3-2018.05 revision d29120a424ecfbc167ef90065c0eeb7f91977701] Scanning up to 1024 MB RAM, starting at offset 32MB Memory size is 1024MB (10000000 - 4fffffff) RAM: 0000000010000000 - 000000004fffffff: 1048576kB Total RAM: 1024MB Scanning fiasco Scanning sigma0 Scanning moe Moving up to 12 modules behind 11100000 moving module 02 { 11a45000-11a7952b } -> { 11b36000-11b6a52b } [214316] moving module 01 { 11a3a000-11a443b7 } -> { 11b2b000-11b353b7 } [41912] moving module 00 { 1197f000-11a399d7 } -> { 11a70000-11b2a9d7 } [764376] moving module 11 { 1167f000-1197efff } -> { 11770000-11a6ffff } [3145728] moving module 10 { 11673000-1167e766 } -> { 11764000-1176f766 } [46951] moving module 09 { 1124b000-116724cf } -> { 1133c000-117634cf } [4355280] moving module 08 { 1124a000-1124a0ee } -> { 1133b000-1133b0ee } [239] moving module 07 { 11248000-1124992f } -> { 11339000-1133a92f } [6448] moving module 06 { 11247000-112473b3 } -> { 11338000-113383b3 } [948] moving module 05 { 11087000-11246a87 } -> { 11178000-11337a87 } [1833608] moving module 04 { 11025000-1108676b } -> { 11116000-1117776b } [399212] moving module 03 { 1100f000-110244ef } -> { 11100000-111154ef } [87280] Loading fiasco Loading sigma0 Loading moe find kernel info page... found kernel info page (via ELF) at 10002000 Regions of list 'regions' [ 10000000, 100001bf] { 1c0} Root mbi_rt [ 10001000, 10001a3f] { a40} Kern fiasco [ 10002000, 100cbfff] { ca000} Kern fiasco [ 10100000, 10109c5f] { 9c60} Sigma0 sigma0 [ 10119fcc, 1011e177] { 41ac} Sigma0 sigma0 [ 10140000, 10173d0b] { 33d0c} Root moe [ 10183f70, 1018f4b3] { b544} Root moe [ 11000000, 1100e5bb] { e5bc} Boot bootstrap [ 11100000, 11a6ffff] { 970000} Root Module found kernel options (via ELF) at 10003000 Sigma0 config ip:101003f4 sp:00000000 Roottask config ip:10141590 sp:00000000 Starting kernel fiasco at 10001230 Hello from Startup::stage2 Number of IRQs available at this GIC: 160 FPU: Initialize FPU0: Subarch: 3, Part: 30, Rev: 4, Var: 9, Impl: 41 L2: ID=410000c7 Type=9e340340 Aux=32070000 WMask=ffff S=0 L2: Type L2C-310 Size = 1024kB Ways=16 Waysize=64 SERIAL ESC: allocated IRQ 61 for serial uart Not using serial hack in slow timer handler. Welcome to L4/Fiasco.OC! L4/Fiasco.OC microkernel on arm Rev: unknown compiled with gcc 7.3.1 20180425 [linaro-7.3-2018.05 revision d29120a424ecfbc167ef90065c0eeb7f91977701] for i.MX6 [] Build: #1 Sat Sep 1 02:19:56 CST 2018 Calibrating timer loop... done. MDB: use page size: 20 MDB: use page size: 12 SIGMA0: Hello! KIP @ 10002000 allocated 4KB for maintenance structures SIGMA0: Dump of all resource maps RAM:------------------------ [4:10000000;10000fff] [0:100cc000;100fffff] [0:1010a000;10118fff] [0:1011f000;1013ffff] [4:10140000;10173fff] [0:10174000;10182fff] [4:10183000;1018ffff] [0:10190000;110fffff] [4:11100000;11a6ffff] [0:11a70000;4effffff] IOMEM:---------------------- [0FPU1: Subarch: 3, Part: 30, Rev: 4, Var: 9, Impl: 41 :Cache config: ON 0ID_PFR[01]: 00001231 00000011; ID_[DA]FR0: 00010444 00000000 fID_MMFR[04]: 00100103 20000000 01230000 00102111 ffffff] [0:50000000;ffffffff] MOE: Hello world MOE: found 1021396 KByte free memory MOE: found RAM from 10000000 to 4f000000 MOE: allocated 1008 KByte for the page array @0x10190000 MOE: virtual user address space [0-bfffffff] MOE: rom name space cap -> [C:103000] MOE: rwfs name space cap -> [C:105000] BOOTFS: [11100000-111154fFPU2: Subarch: 3, Part: 30, Rev: 4, Var: 9, Impl: 41 0Cache config: ON ]ID_PFR[01]: 00001231 00000011 ID_[DA]FR0: 00010444 00000000 [ID_MMFR[04]: 00100103 20000000 01230000 00102111 C:107000] l4re BOOTFS: [11116000-1117776c] [C:109000] ned BOOTFS: [11178000-11337a88] [C:10b000] io BOOTFS: [11338000-113383b4] [C:10d000] l4lx_imx6.cfg BOOTFS: [11339000-1133a930] [C:10f000] imx6_hw_devices.devs BOOTFS: [1133b000-1133b0ef] [C:111000] l4lx-imx6.io BOOTFS: [1133c000-117634d0] [C:113000] vmlinuz BOOTFS: [11764000-1176f767] [C:115000] imx6FPU3: Subarch: 3, Part: 30, Rev: 4, Var: 9, Impl: 41 qCache config: ON _ID_PFR[01]: 00001231 00000011s ID_[DA]FR0: 00010444 00000000 aID_MMFR[04]: 00100103 20000000 01230000 00102111 bresd.dtb BOOTFS: [11770000-11a70000] [C:117000] ramdisk-arm.rd MOE: cmdline: moe rom/l4lx_imx6.cfg MOE: Starting: rom/ned rom/l4lx_imx6.cfg MOE: loading 'rom/ned' Ned says: Hi World! Ned: loading file: 'rom/l4lx_imx6.cfg' l4linux-IO| Io service l4linux-IO| Verboseness level: 4 l4linux-IO| unused physical memory space: l4linux-IO| [00000000000000-0000000fffffff] l4linux-IO| [00000050000000-000000ffffffff] l4linux-IO| no 'iommu' capability found, using CPU-phys for DMA l4linux-IO| Loading: config 'rom/imx6_hw_devices.devs' l4linux-IO| warning: inconsistent fixed resource @ device: /System Bus/ l4linux-IO| : hid= l4linux-IO| compatible= { "fsl,imx6q-fec" } l4linux-IO| DMADOM [00000000000000-00000000000000 1] non-pref (32bit) (align=0 flags=6) l4linux-IO| Loading: config 'rom/l4lx-imx6.io' l4linux-IO| Real Hardware ----------------------------------- l4linux-IO| System Bus: hid= l4linux-IO| Resources: ==== start ==== l4linux-IO| DMADOM [00000000000000-00000000000000 1] non-pref (32bit) (align=0 flags=6) l4linux-IO| Resources: ===== end ===== l4linux-IO| ethernet: hid= l4linux-IO| compatible= { "fsl,imx6q-fec" } l4linux-IO| Clients: ===== start ==== l4linux-IO| ethernet: [N2Vi9Proxy_devE] l4linux-IO| Clients: ===== end ==== l4linux-IO| Resources: ==== start ==== l4linux-IO| IOMEM [00000002188000-0000000218bfff 4000] non-pref (32bit) (align=3fff flags=2) l4linux-IO| IRQ [00000000000096-00000000000096 1] level high (32bit) (align=0 flags=300001) l4linux-IO| IRQ [00000000000097-00000000000097 1] level high (32bit) (align=0 flags=300001) l4linux-IO| DMADOM [00000000000000-00000000000000 1] non-pref (32bit) (align=0 flags=6) l4linux-IO| Resources: ===== end ===== l4linux-IO| warning: could not register control interface at cap 'platform_ctl' l4linux-IO| Ready. Waiting for request. l4linux | PH 0 offs=00010000 flags=rwx PH-type=0x1 l4linux | virt=03000000 evirt=0348e000 l4linux | phys=03000000 ephys=0348e000 l4linux | f_sz=004071fc memsz=0048e000 l4linux | PH 1 offs=003c099c flags=r-- PH-type=0x4 l4linux | virt=033b099c evirt=033b09c0 l4linux | phys=033b099c ephys=033b09c0 l4linux | f_sz=00000024 memsz=00000024 l4linux | PH 2 offs=00000000 flags=rwx PH-type=0x6474e551 l4linux | virt=00000000 evirt=00000000 l4linux | phys=00000000 ephys=00000000 l4linux | f_sz=00000000 memsz=00000000 l4linux | Starting binary at 0x3000260, argc=5 argv=0xafff4f94 *argv=0xb1007ff4 argv0=rom/vmlinuz l4linux | External resolver is at 0xa8000b48 l4linux | ======> L4Linux starting... <======== l4linux | Linux version 4.17.0-l4 (zhangdiming@ubuntu) (gcc version 7.3.1 20180425 [linaro-7.3-2018.05 revision d29120a424ecfbc167ef90065c0eeb7f91977701] (Linaro GCC 7.3-2018.05)) #7 Mon Sep 3 02:20:06 CST 2018 l4linux | Binary name: rom/vmlinuz l4linux | This is an AEABI build. l4linux | Linux kernel command line (4 args): mem=64M console=ttyLv0l4x_rd=rom/ramdisk-arm.rd root=1:0 ramdisk_size=4000 l4linux | CPU mapping (l:p)[1]: 0:0 l4linux | Image: 03000000 - 03600000 [6144 KiB]. l4linux | Areas: Text: 03000000 - 032f5000 [3028kB] l4linux | RO-Data: 032f5000 - 0339b000 [664kB] l4linux | Data: 033d6000 - 034071fc [196kB] l4linux | Init: 033b1000 - 033d6000 [148kB] l4linux | BSS: 034071fc - 0348e000 [539kB] l4linux | Device scan: l4linux | Device: L4ICU l4linux | Device: ethernet l4linux | MEM: 02188000 - 0218bfff l4linux | IRQ: 00000096 - 00000096 l4linux | IRQ: 00000097 - 00000097 l4linux | DMAD: 00000000 - 00000000 l4linux | Device scan done. l4linux | l4lx_thread_create: Created thread 41d (cpu0) (u:b3000e00, v:b3000c00, sp:033d7fa4) l4linux | main thread will be 41d l4linux | L4x: section-with-init(-data): Virt: 0x3000000 to 0x348dfff [4664 KiB] l4linux | section-with-init(-data): Phys: 0x10719fff00000000 to 0x123800000000, [8 KiB] l4linux | L4x: section-with-init-text: Virt: 0x3000000 to 0x348dfff [4664 KiB] l4linux | error: failed to get physical address for 3000000. l4linux | L4x: data: Virt: 0x3000000 to 0x348dfff [4664 KiB] l4linux | error: failed to get physical address for 3000000. l4linux | L4x: Main thread running, waiting... l4linux | L4x: Memory size: 64MB l4linux | L4x: Setting superpages for main memory l4linux | L4x: Adjusted memory start: 03000000 l4linux | L4x: Main memory: Virt: 0x3600000 to 0x75fffff [65536 KiB] l4linux | Main memory: Phys: 0x11c00000 to 0x15bfffff, [65536 KiB] l4linux | L4x: vmalloc area: 07600000 - 0f600000 l4linux | L4x: text: Virt: 0x3000000 to 0x348dfff [4664 KiB] l4linux | error: failed to get physical address for 3000000. l4linux | Loading: rom/ramdisk-arm.rd l4linux | INITRD: Size of RAMdisk is 3072KiB l4linux | RAMdisk from 00002000 to 00302000 [3072KiB] l4linux | l4lx_thread_create: Created thread 422 (timer0) (u:b3000a00, v:00000000, sp:0342ffa0) l4linux | Booting Linux on physical CPU 0x0 l4linux | Linux version 4.17.0-l4 (zhangdiming@ubuntu) (gcc version 7.3.1 20180425 [linaro-7.3-2018.05 revision d29120a424ecfbc167ef90065c0eeb7f91977701] (Linaro GCC 7.3-2018.05)) #7 Mon Sep 3 02:20:06 CST 2018 l4linux | CPU: Fiasco [412fc09a] revision 10 (ARMv7), cr=00400000 l4linux | CPU: PIPT / VIPT nonaliasing data cache, VIPT nonaliasing instruction cache l4linux | Machine: L4 l4linux | Ignoring unrecognised tag 0x00000000 l4linux | Memory policy: Data cache writealloc l4linux | CPU: All CPU(s) started in SVC mode. l4linux | INITRD: 00002000 - 00302000 l4linux | random: get_random_bytes called from start_kernel+0x9c/0x3c0 with crng_init=0 l4linux | Built 1 zonelists, mobility grouping on. Total pages: 17685 l4linux | Kernel command line: mem=64M console=ttyLv0l4x_rd=rom/ramdisk-arm.rd root=1:0 ramdisk_size=4000 l4linux | Dentry cache hash table entries: 16384 (order: 4, 65536 bytes) l4linux | Inode-cache hash table entries: 8192 (order: 3, 32768 bytes) l4linux | Memory: 64776K/71684K available (3028K kernel code, 196K rwdata, 664K rodata, 148K init, 539K bss, 6908K reserved, 0K cma-reserved) l4linux | Virtual kernel memory layout: l4linux | vector : 0xffff0000 - 0xffff1000 ( 4 kB) l4linux | fixmap : 0xffc00000 - 0xfff00000 (3072 kB) l4linux | vmalloc : 0x07600000 - 0x0f600000 ( 128 MB) l4linux | lowmem : 0x00000000 - 0x07600000 ( 118 MB) l4linux | modules : 0x02010000 - 0x03000000 ( 15 MB) l4linux | .text : 0x(ptrval) - 0x(ptrval) (3028 kB) l4linux | .init : 0x(ptrval) - 0x(ptrval) ( 148 kB) l4linux | .data : 0x(ptrval) - 0x(ptrval) ( 197 kB) l4linux | .bss : 0x(ptrval) - 0x(ptrval) ( 540 kB) l4linux | NR_IRQS: 282 l4linux | clocksource: l4kipclk: mask: 0xffffffffffffffff max_cycles: 0x1d854df40, max_idle_ns: 3526361616960 ns l4linux | l4timer: Using IRQ210 l4linux | sched_clock: 64 bits at 1000kHz, resolution 1000ns, wraps every 2199023255500ns l4linux | Console: colour dummy device 80x30 l4linux | console [ttyLv0] enabled l4linux | Calibrating delay loop... 1581.05 BogoMIPS (lpj=7905280) l4linux | pid_max: default: 32768 minimum: 301 l4linux | Mount-cache hash table entries: 1024 (order: 0, 4096 bytes) l4linux | Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes) l4linux | CPU: Testing write buffer coherency: ok l4linux | Setting up static identity map for 0x3000000 - 0x3000000 l4linux | VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4 l4linux | clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns l4linux | futex hash table entries: 256 (order: -1, 3072 bytes) l4linux | NET: Registered protocol family 16 l4linux | DMA: preallocated 256 KiB pool for atomic coherent allocations l4linux | Failed to create "l4x" debugfs directory: -19 l4linux | clocksource: Switched to clocksource l4kipclk l4linux | NET: Registered protocol family 2 l4linux | tcp_listen_portaddr_hash hash table entries: 512 (order: 0, 4096 bytes) l4linux | TCP established hash table entries: 1024 (order: 0, 4096 bytes) l4linux | TCP bind hash table entries: 1024 (order: 0, 4096 bytes) l4linux | TCP: Hash tables configured (established 1024 bind 1024) l4linux | UDP hash table entries: 256 (order: 0, 4096 bytes) l4linux | UDP-Lite hash table entries: 256 (order: 0, 4096 bytes) l4linux | NET: Registered protocol family 1 l4linux | Trying to unpack rootfs image as initramfs... l4linux | rootfs image is not initramfs (junk in compressed archive); looks like an initrd l4linux | INITRD: Freeing memory. l4linux | l4x: Checks passed. l4linux | NetWinder Floating Point Emulator V0.97 (double precision) l4linux | workingset: timestamp_bits=30 max_order=14 bucket_order=0 l4linux | io scheduler noop registered l4linux | io scheduler deadline registered l4linux | io scheduler cfq registered (default) l4linux | io scheduler mq-deadline registered l4linux | io scheduler kyber registered l4linux | L4 serial driver l4linux | serial-ttyLv.0: ttyLv0 at MMIO 0x1 (irq = 0, base_baud = 230400) is a L4-vcon l4linux | l4ser_shm: L4 shared mem serial driver l4linux | l4cdds: No name given, not starting. l4linux | brd: module loaded l4linux | l4bdds: No name given, not starting. l4linux | NET: Registered protocol family 17 l4linux | RAMDISK: ext2 filesystem found at block 0 l4linux | RAMDISK: Loading 3072KiB [1 disk] into ram disk... | / - \ | / - \ | / - \ | / - \ | / - \ | / - \ | / - \ | / - \ | / - \ | / - \ | / - \ | / - \ | / - \ | / - \ | / - \ | / - \ | / - \ | / - \ | / - \ | / - \ | / - \ | / - \ | / - \ | / - \ | / - \ | / - \ | / - \ | / - \ | / - \ | / - \ | / - \ | / - \ | / - \ | / - \ | / - \ | / - \ | / - \ | / - \ | / - \ | / - \ | / - \ | / - \ | / - \ | / - \ | / - \ | / - \ | / - \ | / - \ done. l4linux | EXT4-fs (ram0): mounting ext2 file system using the ext4 subsystem l4linux | EXT4-fs (ram0): mounted filesystem without journal. Opts: (null) l4linux | VFS: Mounted root (ext2 filesystem) readonly on device 1:0. l4linux | Freeing unused kernel memory: 148K l4linux | This architecture does not have kernel memory protection. l4linux | The booting stopped at here, and there is no sentance as "Please press Enter to activate this console." displayed. ============================== module.list ------------------------------------- modaddr 0x01100000 default-kernel fiasco -serial_esc default-bootstrap bootstrap entry imx6-arm roottask moe rom/l4lx_imx6.cfg module l4re module ned module io module l4lx_imx6.cfg module imx6_hw_devices.devs module l4lx-imx6.io module vmlinuz module[perl] "ramdisk-$ENV{ARCH}.rd" ============================== At this point I have no idea what to do any help will be much appreciated! Thank you very much! Regards Jason

2 1

Genode 18.08 brings modern hardware support
by Stefan Kalkowski 30 Aug '18

30 Aug '18

Dear l4-hackers, the community and team around the Genode OS framework proudly presents release 18.08, which is at the same time the 10th anniversary of our project. With this release we follow our ambition to sculpt a general-purpose OS using the Genode framework. It adds support for a lot of different recent hardware, the ability to apply Intel microcode updates in a kernel agnostic fashion, and extends the interactive usability of the system. Readers of this mailing list might be especially interested in the update of the NOVA and Fiasco.OC kernels used by the framework to recent versions. The highlights of Genode 18.08 are: - Sculpt OS with live runtime view - Device drivers - Linux device-driver environment based on kernel 4.16.3 - Updated and enhanced Intel framebuffer and wireless drivers - De-componentized USB stack, support for isochronous devices - Improved device compatibility of NIC and PS/2 drivers - Experimental runtime for Zircon-based drivers - Base framework and OS-level infrastructure - NIC-router support for multiple uplinks - New VFS plugin for using LwIP as TCP/IP stack - Cached file-system-based ROM service - VFS plugin for importing initial content - Enhanced Ada language support - Libraries and applications - Python 3 - VirtualBox 5.1.38 - Platforms - New Intel Microcode update mechanism - Multiprocessor support for our custom kernel on x86 - Updated NOVA and Fiasco.OC kernels All of these and more improvements can be read in detail in the release documentation: https://genode.org/documentation/release-notes/18.08 We are looking forward for your feedback. Happy hacking! -- Stefan Kalkowski Genode labs https://github.com.skalk | https://genode.org

1 0

L4Re Build Failure on i386 (Revision 80)
by Paul Boddie 12 Aug '18

12 Aug '18

Hello, I thought I'd try and get L4Re and the UX variant of Fiasco.OC working again. Various errors with the actual compiler - not typical compilation errors - have previously occurred, but system updates come along every so often and I saw that new revisions of L4Re/Fiasco.OC have also arrived fairly recently. Unfortunately, the L4Re build fails with complaints about the linking process. Here is the verbose build output at the point of failure: [fb-drv] ==> Linking fb-drv LD_PRELOAD=libgendep.so LD_LIBRARY_PATH=:/home/paulb/L4/UX/src/l4/mybuild/tool/gendep/32:/home/paulb/L4/UX/src/l4/mybuild/tool/gendep GENDEP_TARGET=fb-drv GENDEP_BINARY=ld GENDEP_BINARY_ALT1=ld /home/paulb/L4/UX/src/l4/tool/bin/l4-bender -t ld - Dl4obj=/home/paulb/L4/UX/src/l4/mybuild -Dl4dir=/home/paulb/L4/UX/src/l4 - Dgcclibdir="/usr/lib/gcc/i686-linux-gnu/7/ /usr/lib/gcc/i686-linux- gnu/7/../../../../i686-linux-gnu/lib/i686-linux-gnu/7/ /usr/lib/gcc/i686- linux-gnu/7/../../../../i686-linux-gnu/lib/i386-linux-gnu/ /usr/lib/gcc/i686- linux-gnu/7/../../../../i686-linux-gnu/lib/../lib/ /usr/lib/gcc/i686-linux- gnu/7/../../../i686-linux-gnu/7/ /usr/lib/gcc/i686-linux-gnu/7/../../../i386- linux-gnu/ /usr/lib/gcc/i686-linux-gnu/7/../../../../lib/ /lib/i686-linux- gnu/7/ /lib/i386-linux-gnu/ /lib/../lib/ /usr/lib/i686-linux-gnu/7/ /usr/lib/i386-linux-gnu/ /usr/lib/../lib/ /usr/lib/gcc/i686-linux- gnu/7/../../../../i686-linux-gnu/lib/ /usr/lib/gcc/i686-linux-gnu/7/../../../ /lib/ /usr/lib/" -Dl4system=x86_gen -Dl4api=l4f -Dlinker="ld -m elf_i386" -- spec=/home/paulb/L4/UX/src/l4/mk/bid-bender.spec -- -o fb-drv -MD -MF ./.fb- drv.pcs.d -PClibc_support_misc -PClibio-vbus -PCx86emu_int10 -PCx86emu_int10 - PCstdlibs -static -gc-sections -Ttext-segment=0x01000000 --defsym __L4_KIP_ADDR__=0xaffff000 --defsym __L4_STACK_ADDR__=0xb0000000 -L /home/paulb/L4/UX/src/l4/mybuild/lib/x86_gen/l4f -L /home/paulb/L4/UX/src/l4/mybuild/lib/x86_gen -L /home/paulb/L4/UX/src/l4/mybuild/lib --warn-common -Ttext-segment=0x01000000 main.o dummy.o splash.o vesa.o ld: section `.note.gnu.property' assigned to non-existent phdr `interp' ld: section `.rel.dyn' assigned to non-existent phdr `interp' I know that the ldscripts have been changed, but I struggle to see how the above relates to them or whether they are even involved in this particular outcome. Might there be something obviously wrong somewhere in the recent changes? Paul

2 7

L4Re development version available on GitHub
by Jakub Jermar 04 Jul '18

04 Jul '18

Dear L4 hackers, we in Kernkonzept are happy to announce the release of our L4Re operating system framework on GitHub. Today we release 6 new repositories: https://github.com/kernkonzept/mk https://github.com/kernkonzept/manifest https://github.com/kernkonzept/l4re-core https://github.com/kernkonzept/hello https://github.com/kernkonzept/drivers-frst https://github.com/kernkonzept/bootstrap Together with the Fiasco.OC repository released earlier this year[1], these repositories represent a frequently updated foundation for building operating systems with real-time, security, safety and virtualization requirements. The manifest repository contains a Wiki with detailed instructions on building[2] L4Re and contributing[3] to it. Happy hacking! Jakub [1] http://os.inf.tu-dresden.de/pipermail/l4-hackers/2018/008224.html [2] https://github.com/kernkonzept/manifest/wiki/BUILDING [3] https://github.com/kernkonzept/manifest/wiki/CONTRIBUTING

1 0

Building programs with MODE=shared in L4Re
by Paul Boddie 04 Jul '18

04 Jul '18

Hello, I have been busy writing libraries and programs for L4Re and recently had to think about the size of the payloads I have been deploying. It appears that in the build system, one can use MODE=shared to build dynamically-linked programs, and there is a shared version of the hello example in the examples package. However, I don't see any recipe for doing this for other programs. My impression is that the dynamic linker must have all the required libraries deployed as modules, and so I wrote a script to generate a list of such modules using readelf. In addition, it appears that libl4sys-direct.so is required (which readelf does not detect). Adding these modules to my conf/modules.list should yield success, but within my constrained debugging environment, I only see that "shared" programs fail to start. I really need to see if they start but then experience some initialisation problem, or whether they actually crash but Mag keeps their viewports around. Are there any other things that I need to consider when building and deploying such programs? I searched for guidance on this topic and only found the following: http://os.inf.tu-dresden.de/pipermail/l4-hackers/2014/007094.html http://os.inf.tu-dresden.de/pipermail/l4-hackers/2016/007830.html Both of these discussion threads only provide some details and are obviously not tutorials. Thanks for any clues you might be able to provide! Paul P.S. I guess I could also see if the CI20 produces useful console-level details, perhaps indicating an architecture-related problem. Usually, however, the problem is caused by some simple mistake I have made, so I suspect that there is merely some detail I have forgotten.

2 9

Release of Sculpt TC
by Alexander Boettcher 15 Jun '18

15 Jun '18

Hi l4-hackers, we are happy to announce the release of Sculpt TC [0], a Genode based incarnation of a microkernel based operating system. It is the second out of four Sculpt OS releases planned in 2018 [1]. Under https://genode.org/download/sculpt you find the downloadable image, which is a live system and installer all in one. Once booted you can download further packages to play around with, e.g several native Genode applications and VMs on several VMMs. Have fun. Cheers, Alex B. [0] https://lists.genode.org/pipermail/users/2018-June/006115.html [1] https://genode.org/about/road-map#2018_-_The_year_of_Sculpt -- Alexander Boettcher Genode Labs http://www.genode-labs.com - http://www.genode.org Genode Labs GmbH - Amtsgericht Dresden - HRB 28424 - Sitz Dresden Geschäftsführer: Dr.-Ing. Norman Feske, Christian Helmuth

2 3

Issues about webserver on L4Re
by 李鼎基 08 Jun '18

08 Jun '18

Hi, I’ve been trying to find or write a webserver directly on L4Re (*NO* L4Linux involved) based on snapshot “l4re-snapshot-17.12”. At first, I noticed that there was already a web server in “l4re-snapshot-17.12/src/l4/pkg/ankh”. But it was broken, even if I removed the “broken” file to make, nothing was generated under “/path/to/build/pkg/ankh” except “Makefile”. Then I intend to write a simple webserver (1st step a socket demo). Although there are socket APIs, I don’t know how to solve the NIC driver issues. The same code works well on Linux but failed on L4Re. Therefore: 1. Is there any way to revive the “ankh”? 2. If not, is there any way/demo to write a simple webserver directly on L4Re? Or how to solve the NIC driver issues? -- Thanks

2 1

Porting L4Re and Fiasco.OC to the Ben NanoNote and Letux 400
by Paul Boddie 30 May '18

30 May '18

As promised, I wrote up my experiences porting L4Re and Fiasco.OC to the Ben NanoNote: https://blogs.fsfe.org/pboddie/?p=2147 There are, in fact, nine articles describing the process, which I accept might be a bit too much reading for the casual inquirer, especially as the narrative wanders from one problem to be solved to the next. But the summary should cover the main tasks that need to be done in this kind of work. Since getting things working on the Ben, I have also persuaded the software to work on the Letux 400 notebook computer, which is a variant of the Skytone Alpha-400 product that did the rounds almost ten years ago (although I was probably completely unaware of it at that time): http://blogs.fsfe.org/pboddie/?p=2175 I hope that some of the information I have shared is useful to others and perhaps encourages someone else to port the software to a device of their choosing. Good luck to that person! Paul P.S. As noted before, the patches are here: http://www.boddie.org.uk/paul/L4Re-Fiasco.OC.html

2 5

Input driver configuration and use in L4Re
by Paul Boddie 25 May '18

25 May '18

Hello again, I have been implementing input drivers for the keypad/keyboard provided by the Ben NanoNote and Letux 400 notebook computer, and although I appear to have implemented something that works (tested using specialised example code), using the existing OMAP3 keypad code as a guide (in pkg/drivers/input), I wondered whether it is possible to connect such drivers to other components in a convenient way. I see that the input package is the thing that provides the device registry that I use when employing the arm_input_register macro, and in that package is a framework that supposedly exports input drivers as serial I/O devices using the "l4drv" driver. But I can't find anything obvious that uses the connect operation which would need to occur to probe, enable, and attach my driver to this framework. Is it possible to integrate my input drivers to things like Mag, which seems to use input events, or to fbterminal or other things? I haven't seen any documentation or code that demonstrates this, but I suppose that I may have missed something somewhere. Thanks for any help that is offered! Paul

2 4

Re: Assertion failure error in kernel vgic interrupt processing
by nico.hacker 14 May '18

14 May '18

Hi, The previous test is not enough to cause error, this error is not related to peripherals, I have removed almost all peripheral drivers In the previous test, I added a delay operation before the vm2 start, so that vm1 completely up and then start vm2, this will greatly reduce the probability of the error. Now I removed this delay, vm1 and vm2 started simultaneously, then the error will occur frequently (about 1/10 probability). The error is generated when kernel processes vtimer interrupts. Under normal circumstances, after processing a vtimer interrupt, the vcpu thread will return to uvmm and then execute prepare_guest_entry(). This operation will eventually enter the kernel through the system call to set the state of vcpu thread, but when the error occurs, I find that the vcpu thread does not execute vcpu_resume, it processes two consecutive vtimer interrupts. As a result, the assertion fails.  Is the kernel able to guarantee that the complete process of handling vgic and vtimer interrupts (including the process in uvmm) is not interrupted by a new interrupt?  Here's my configuration: ------------------------------------------------------------------------- uvmm.ned vmm.start_vm{   id=1,   mem=256,   vbus=io_busses.vm_hw,   bootargs=common_bootargs .. " ramdisk_size=9100 root=/dev/ram",   kernel="rom/Image.gz",   rd="rom/ramdisk-arm.rd",   fdt="rom/virt-board.dtb",   prio=nil, cpus=0x1 }; vmm.start_vm{   id=2,   mem=256,   vbus=io_busses.vm_nohw,   bootargs=common_bootargs .. " ramdisk_size=9100 root=/dev/ram",   kernel="rom/Image.gz",   rd="rom/ramdisk-arm.rd",   fdt="rom/virt-board.dtb",   prio=nil, cpus=0x1 }; -------------------------------------------------------------------------- io.cfg -- vi:ft=lua local Res = Io.Res local Hw = Io.Hw local add_children = Io.Dt.add_children add_children(Io.system_bus(), function()   VGIC = Hw.Device(function()     Property.hid = "arm-gicc";     Resource.reg0 = Res.mmio(0x12006000, 0x12007fff);     Property.flags = Io.Hw_device_DF_multi_vbus;   end)   VM1_DEV = Hw.Device(function()     Property.hid = "vm1_dev";     Resource.reg0 = Res.mmio(0x70100000, 0x70100FFF); --UART   end)   VM2_DEV = Hw.Device(function()     Property.hid = "vm2_dev";     Resource.reg0 = Res.mmio(0x70100000, 0x70100FFF); --UART   end) end) ---------------------------------------------------------------------------- vm_hw.vbus Io.add_vbusses {   vm_hw = Io.Vi.System_bus(function()     VGIC = wrap(Io.system_bus():match("arm-gicc"));     VM1_DEV = wrap(Io.system_bus():match("vm1_dev"));   end); } ---------------------------------------------------------------------------- vm_nohw.vbus Io.add_vbusses {   vm_nohw = Io.Vi.System_bus(function()     VGIC = wrap(Io.system_bus():match("arm-gicc"));     VM2_DEV = wrap(Io.system_bus():match("vm2_dev"));   end); }---------------------------------------------------------------------------- Nico 于 2018-04-11 05:59:58,Adam Lackorzynski<adam os="" inf="" tu-dresden="" de="">写道:</adam><blockquote style="padding-left:1ex;margin:0px 0px 0px 0.8ex;border-left:#ccc 1px solid"><pre>On Mon Apr 09, 2018 at 22:26:38 +0800, nico wrote: > Sorry, the last email did not specify this information. > I gave VM1 all the hardware resources, and it used eight cores. VM2 only has > uart resources (also timer, gic resources), using a single core. I tried to > give both VM1 and VM2 only the necessary hardware resources( uart, timer, gic), > and that error won't happen. Ok, that's interesting. So that means that some of the passed through hardware is causing this. Would you be able to find out which device is causing this, by selectively enabling/disabling devices? Adam > On 4/9/2018 06:28ï¼ Adam Lackorzynski<adam os="" inf="" tu-dresden="" de=""> wroteï¼ > > Hi Nico, > > On Fri Mar 30, 2018 at 10:15:33 +0800, nico wrote: > > Hi Adam, I'm using an eight-core Cortex-A53 processor. The vm is > running 64bit Linux. It is recommended to start two or three vms, that > will be easier to reproduce this problem. > > > So, I tried several things but cannot reproduce this issue. I assume > this are single-core VMs only? Any hardware passed through? > Just trying to narrow it down... _______________________________________________ l4-hackers mailing list l4-hackers(a)os.inf.tu-dresden.de http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers </adam></pre></blockquote><div style="height:30px;"></div><div style="height:2px;width:298px;border-bottom:solid 2px #e5e5e5"></div><div style="height:20px;"></div><a target="_blank" style="background-image:url(http://r.g.tom.com/kwap/r/app/other/suixinyou.png);bac… center;font-size:14px;background-size: 20px;height: 39px;line-height: 39px;padding-left: 25px;display:block;color:#333333;text-decoration: none;" href="http://mail.tom.com/webmail-static/welcomesxy.html" onmouseover="this.style.cssText='background-image:url(http://r.g.tom.com/kwap/r/app/other/suixinyou.png);bac… center;font-size:14px;background-size: 20px;height: 39px;line-height: 39px;padding-left: 27px;display:block;color:#4c4c4c; text-decoration:underline;'" onmouseout="this.style.cssText='background-image:url(http://r.g.tom.com/kwap/r/app/other/suixinyou.png);bac… center;font-size:14px;background-size: 20px;height: 39px;line-height: 39px;padding-left: 27px;display:block;color:#4c4c4c;text-decoration:none'">随心邮-在微信里收发邮件，及时省电又安心</a>

2 1