l4-hackers

l4-hackers@os.inf.tu-dresden.de

2827 discussions

Re: L4Env
by Ian Duggan 11 Mar '02

11 Mar '02

What is the latest status on the L4ENV stuff? --Ian > > Ian Duggan <ian(a)ianduggan.net> writes: > > > Where can I find out more information about the L4Env project? I'm > [...] > > presentation can be foud at > > http://os.inf.tu-dresden.de/~reuther/helmuth.pdf > > http://os.inf.tu-dresden.de/~reuther/helmuth_slides.pdf > > There is also a small webpage at > http://wwwos.inf.tu-dresden.de/~ch12/diplom/diplom.xml > > I will put more up-to-date documentation (doxygen) about my implementation on > it as far as I cleaned up the sources. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Ian Duggan ian(a)ianduggan.net http://www.ianduggan.net

2 1

(no subject)
by tinker1 french 12 Feb '02

12 Feb '02

still looking for way to find pharmacys directory for overseas. _________________________________________________________________ Send and receive Hotmail on your mobile device: http://mobile.msn.com

1 0

L4 Version X.2 announcement
by Uwe Dannowski 28 Jan '02

28 Jan '02

The L4Ka Team is happy to announce the availability of the L4 microkernel API specification, Version X.2. The specification can be downloaded in PDF format from the L4Ka web-site (http://l4ka.org/). It should be noted that the Version X.2 specification is experimental. Future revisions may contain modifications and introduce incompatibilities with the current revision. It is nevertheless our intention that the amount of changes to the specification should be small, and that the X.2 specification should deviate as little as possible from the forthcoming Version 4 specification. The L4Ka Team is currently working on providing a reference implementation for the specification. No release date has been chosen. - The L4Ka Team

1 0

L4/Alpha palcodes
by Goswin Brederlow 25 Jan '02

25 Jan '02

Hi, I hope this is the right place, havent read anything here for ages. I was wondering whether the palcodes used by L4 on Alpha are disjunct to the ones used by OSF / BSD / Linux. If not could they be made disjunct? The idea I have in mind is to make a module for linux that catches the L4 syscalls and throws them back into user-space. That way a L4 environment could be setup within linux. It would be much like user-space-linux and would save a lot of reboots just to test out a few bytes of code. On the other hand, inside L4 you could do the same with OSF / BSD / Linux syscalls and thus run their binaries under L4. (You want to run Netscape under L4? Or Mathematica? Or something as simple as xemacs and gcc?) A l4-linux for alpha would also need those changes (if any) I believe. MfG Goswin

4 5

RE: L4/Alpha palcodes
by Sebastian Schoenberg 22 Jan '02

22 Jan '02

Yes, they were set to numbers which do not conflict with OSF/Linux/WinNT. A PALcall instuction is coded as cmd (6 bits) = 0, number (26 bits). There are two ways of calling PALcode: A direct way, where a certain address is called, or an indirect way, which must examine the calling instruction to jump to the right place. All L4Alpha PALcalls are located at the end of direct-callable PALcalls, hence they are fast and do not conflict with any other system Seb > -----Original Message----- > From: Daniel Potts [mailto:danielp@cse.unsw.edu.au] > Sent: Dienstag, 22. Januar 2002 09:50 > To: Goswin Brederlow > Cc: l4-hackers(a)os.inf.tu-dresden.de > Subject: Re: L4/Alpha palcodes > > > On 22 Jan 2002, Goswin Brederlow wrote: > > > Hi, > > > > I hope this is the right place, havent read anything here for ages. > > > > > > I was wondering whether the palcodes used by L4 on Alpha > are disjunct > > to the ones used by OSF / BSD / Linux. > > yes they are. An exception is l4_whoami which is an > experimental syscall anyway. I think it maps directly to the > OSF whoami call. > > > > > If not could they be made disjunct? > > > > > > The idea I have in mind is to make a module for linux that > catches the > > L4 syscalls and throws them back into user-space. That way a L4 > > environment could be setup within linux. It would be much like > > user-space-linux and would save a lot of reboots just to test out a > > few bytes of code. > > heh :) That would be an interesting project. I'd be > interested to know how (if) you will deal with device > drivers, memory etc. > > > On the other hand, inside L4 you could do the same with OSF / BSD / > > Linux syscalls and thus run their binaries under L4. (You > want to run > > Netscape under L4? Or Mathematica? Or something as simple as xemacs > > and gcc?) > > > > > > A l4-linux for alpha would also need those changes (if any) > I believe. > > Yes that is how we would run unmodified Linux/Alpha binaries on L4.. > > Cheers, > Daniel > > _______________________________________________ > l4-hackers mailing list > l4-hackers(a)os.inf.tu-dresden.de > http://os.inf.tu-> dresden.de/mailman/listinfo/l4-hackers >

1 0

L4\UltraSPARCIIi?
by Crusher 20 Jan '02

20 Jan '02

I'm a graduate student at CSUS (California State University Sacramento). I was looking around the Internet for a Master's Project. I decided that since no one has ported L4 to the UltraSPARCIIi I would attempt it (as this is my first kernel, I'm not expecting too much), especially since the school has plenty of Sun machines around. I do already have a Sun Ultra 5 workstation and the development environment just about setup. Before I really started in on my project, I just wanted to make sure that a L4 port to the UltraSPARC isn't in the works or has been completed. Otherwise, I was hoping someone has done system work with the UltraSPARC and would be willing answer some of my UltraSPARC specific technical questions that I know will come up. Scott Tanaka

1 0

OSKit-Problems with newer glibc
by imi＠inf.tu-dresden.de 17 Jan '02

17 Jan '02

Hi Are there any reported solutions for compiling the oskit1.0 that comes with l4 with installed glibc 2.2.4 or newer? On my machine (Debian "sid", gcc 2.95.4) it throw a linker error while linking unix/linux/sbrk-hack.o together with libc.a because duplicate symbol __libc_multiple_libcs. The sbrk-hack's only purpose seems to be defining these global variable (as an int). Maybe this was an error in libc and got fixed in 2.2.4? However when I compiled under glibc 2.1.3-10 (and gcc 2.95.2) it works... -- Immanuel Scholz, PGP: (Work 0x9216F1E7, Home 0x3B5DC02D)

3 3

OSKit-Problems with newer glibc
by imi＠wh9.tu-dresden.de 16 Jan '02

16 Jan '02

1 0

2nd release of L4Ka/Hazelnut
by Uwe Dannowski 14 Dec '01

14 Dec '01

Hi L4 hackers and users, after a long wait it's again time to announce a new release of L4Ka/Hazelnut. L4Ka/Hazelnut still implements the L4 Version X.0 API on x86 and ARM processors. This time around, however, it outperforms Jochen's x86 assembly kernel. Parts of the kernel have also been redesigned for better portability. Among the goodies added since the last release are: o Small Address Spaces o IPC FastPath(tm) o FPU virtualization o Enhanced kernel debugger (e.g., embedded disassembler and profiling support) o Pentium4 support o One year's worth of bugfixes For more information please visit http://l4ka.org/.

1 0

RE: l4 for 386
by Sebastian Schoenberg 08 Nov '01

08 Nov '01

Well, sort of or not. You have a mirrored region for kernel- accessed read-only memory regions where the kernel potentially might write to. You don't need a mirrored region for all writable pages. Seb > -----Original Message----- > From: Espen Skoglund [mailto:esk@ira.uka.de] > Sent: Mittwoch, 7. November 2001 13:31 > To: Sebastian Schoenberg > Cc: jhuntnz(a)users.sourceforge.net; l4-hackers(a)os.inf.tu-dresden.de > Subject: RE: l4 for 386 > > > [Sebastian Schoenberg] > > This can be done by using different regions for read and write > > access. For tasks where the write-protection is neccesary, a page > > is mapped only to the writeable area if the page is writable in the > > page-table. > > I'm not sure I know what you mean here. Are you suggesting that we > divide the user-accessible virtual memory into two equally sized > mirrored regions; one for read-only and one for read-write? > > eSk >

1 0

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

1998

l4-hackers