l4-hackers

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

2 participants
2880 discussions

New Fiasco snapshot
by Michael Hohmuth 10 May '99

10 May '99

Hackers, I've made available a new Fiasco source code snapshot (990428), nicknamed version 0.6. It contains numerous bug fixes and two new features: - Long-message IPC has been implemented (but hasn't yet been tested extensively). - Jean Wolter has contributed a new stand-alone kernel debugger. It allows you to see critical kernel state on your text console. I've also released new snapshots for the L4 runtime support (required) and for our version of the OSKit, as well as a new patch for L4Linux. Please find the stuff here: ftp://ftp.inf.tu-dresden.de/pub/os/L4/fiasco/fiasco-l4-990428.tar.gz ftp://ftp.inf.tu-dresden.de/pub/os/L4/devel/l4-990428.tar.gz ftp://ftp.inf.tu-dresden.de/pub/os/L4/devel/oskit-l4-990428.tar.gz ftp://ftp.inf.tu-dresden.de/pub/os/L4/devel/linux-l4-981207.patch-02.gz Our admins are busy figuring out how to allow CVS access from the outside world. In the future this will allow you to access up-to-date source code without waiting for a new snapshot. Please visit <URL:http://os.inf.tu-dresden.de/fiasco/use.html> for updated build instructions. Have fun! Michael -- hohmuth(a)innocent.com, hohmuth(a)inf.tu-dresden.de http://home.pages.de/~hohmuth/

2 1

Re: Patch for Fiasco 0.6
by Michael Hohmuth 04 May '99

04 May '99

kermit the frog <kermit(a)tower.com.ar> writes: > Well, what i saw is that the WHOLE directory structure changed ... and the > Makefile has a -I/home/drops (or something) which doesnt seems to be > needed since Fiasco compiles anyway ... These changes allow people working on only part of the source tree to check out (or unpack) only what they're working on and otherwise use what's been installed in /home/drops (DROPS_STDDIR in l4/Makeconf). > It would be nice to have the old dir. structure back ... (; It will get even better (read: more confusing ;) in the next snapshot: We've moved all include files to package-specific subdirectories to reduce clutter in <l4/*.h>, requiring changes to many source files (e.g., <l4/ipc.h> becomes <l4/sys/ipc.h>). We thought that indroducing some software-development guidelines now would hurt less than introducing them later. Michael -- hohmuth(a)innocent.com, hohmuth(a)sax.de http://www.sax.de/~hohmuth/

1 0

Patch for Fiasco 0.6
by Michael Hohmuth 04 May '99

04 May '99

It looks like the Fiasco-0.6 snapshot has been sewed together with too hot a needle (thanks to Hoi-sun lee for reporting this problem). Please apply the patch appended below to make it compile. (This patch will also appear on the Fiasco ftp site as fiasco-l4-990428.patch-01.gz.) Michael -- hohmuth(a)innocent.com, hohmuth(a)inf.tu-dresden.de http://home.pages.de/~hohmuth/

2 1

deceit operations for clans+chiefs.
by Daniel Potts 01 May '99

01 May '99

Assume task A is the chief of task B, which is the chief of task C, which is the chief of task D. ;-) * Now, D does an ipc call to A. A successfully receives the message from D via the chiefs (C and B). * Now when A replies to this, the message first gets intercepted by B. * B sends a deceiting ipc to D with A as the virtual sender. This gets intercepted by C. * C sends a deceiting ipc to D with A as the virtual sender. This step fails (?!) due to direction preservation not holding. That is when C checks nchief on A it returns L4_NC_OUTER_CLAN, and nchief on D returns L4_NC_SAME_CLAN, which is not equal, and therefore not direction preserving. Have I got this scenario correct? Assuming that each cheif can obtain the virtual sender as part of it's ipc api. Cheers, Daniel

2 2

Re: Still missing something ...
by Michael Hohmuth 28 Apr '99

28 Apr '99

kermit the frog <kermit(a)tower.com.ar> writes: > Hello, thanks for always answering (im such a pain in the ... (-: > > Well, this time, after following Michael's instructions (heres a piece of > the code) : > th = l4_myself(); > printf("rmgr_init()\n"); > rmgr_init(); > printf("Hello, task: %d, thread: %d\n", th.id.task, th.id.lthread); > > sigma0.id.task = 2; > sigma0.id.lthread = 0; > > recv.id.task = rmgr_get_task(6); > recv.id.chief = th.id.task ; > recv.id.lthread = 0; > recv = l4_task_new(recv, 5, (dword_t) task+(4096*2), (dword_t)task, > sigma0); > > All i get is : 'sys_id_nearest' > > What is that ?? Argh, the library code snippet I sent you uses l4_nchief(), a binding for the sys_id_nearest system call, a call which has only been fixed recently. I really should release a new code snapshot... I'll try to do this later today (and I'll try to make the source code more accessible in order to avoid such problems in the future). For now, you can try the Fiasco patch below, or you can modify the librmgr.c file I sent you to find out its Rmgr server by querying its pager using l4_thread_ex_regs() instead of using l4_nchief() -- just change the "#if 0" in rmgr_init() to "#if 1". Sorry, Michael -- hohmuth(a)innocent.com, hohmuth(a)inf.tu-dresden.de http://home.pages.de/~hohmuth/

1 0

Still missing something ...
by kermit the frog 28 Apr '99

28 Apr '99

Hello, thanks for always answering (im such a pain in the ... (-: Well, this time, after following Michael's instructions (heres a piece of the code) : th = l4_myself(); printf("rmgr_init()\n"); rmgr_init(); printf("Hello, task: %d, thread: %d\n", th.id.task, th.id.lthread); sigma0.id.task = 2; sigma0.id.lthread = 0; recv.id.task = rmgr_get_task(6); recv.id.chief = th.id.task ; recv.id.lthread = 0; recv = l4_task_new(recv, 5, (dword_t) task+(4096*2), (dword_t)task, sigma0); All i get is : 'sys_id_nearest' What is that ?? Cheers. Cervi~no Ulises <kermit(a)tower.com.ar> <c-3087-2(a)unrctu.edu.ar> ...............................................................................

1 0

Re: Am i missing something here ?
by Michael Hohmuth 27 Apr '99

27 Apr '99

kermit the frog <kermit(a)tower.com.ar> writes: > First of all, thanks for replying. I happen to have another problem. If i > try to create a new task, no matter what i do i always get the message > > 'KDB: task new: not chief' > > the line im using to create a task is as follows: > recv = l4_task_new(recv, 6, (dword_t) task+(4096*2), (dword_t)task, > L4_NIL_ID); > Where task is a function defined void task(void); Im asuming here that the > stack will begin , lets say to pages from the code page (task + (4096*2)). > > Am i missing something here ?? (-: Yes: In order to be allowed to create or delete a task, you must be the task's ``chief.'' When the system boots, Rmgr (task 4) is the chief of all other tasks, and thus is the only task which may create new tasks. Your task (probably task 5) initially cannot create any task. The current owner of a chief right to nonexistent tasks can transfer the right using the l4_task_new() system call. There is an Rmgr protocol message which allows tasks to request chief rights to specific tasks from Rmgr. I'll append below a library which wraps the Rmgr protocol into C bindings. With it it you can request a new chief right using the sequence: rmgr_init(); error = rmgr_get_task(number); (The library also contains functions called rmgr_task_new() and rmgr_task_new_with_prio() which lets Rmgr create a new task, but these currently don't work with Fiasco because they require long-message IPC. Long-message IPC has only been implemented recently, and I'm currently testing it; it will be included in the next release.) Michael -- hohmuth(a)innocent.com, hohmuth(a)inf.tu-dresden.de http://home.pages.de/~hohmuth/

1 0

Re: Am i missing something here ?
by kermit the frog 27 Apr '99

27 Apr '99

Yeah, that could be a solution (the loop) but, ass soon as i try to create the new task it dumps the register contents and then asks me if i want to reboot ... i guess ill have to recompile it with a different # and boot to try every new configuration ... Cervi~no Ulises <kermit(a)tower.com.ar> <c-3087-2(a)unrctu.edu.ar> ............................................................................... On Tue, 27 Apr 1999, Gernot Heiser wrote: > >>>>> "ktf" == kermit the frog <kermit(a)tower.com.ar> writes: > > ktf> Well, ive attached the source code of my program. To anser to your > ktf> question, recv is initialized to task=6; ltherad=0; i know that my program > ktf> starts with task=5 so im using the next task available. > > That doesn't guarantee that this task isn't in use (e.g. for a device > driver). I'm not sure how fiasco allocates initial tasks. You'd be > better off running a loop trying all task ids. > > Gernot > -- > Gernot Heiser ,--_|\ School of Computer Sci. & Engin. > Phone: +61 2 9385 5156 / \ The University of NSW > Fax: +61 2 9385 5995 \_,--._* Sydney, Australia 2052 > E-mail: G.Heiser(a)unsw.edu.au v http://www.cse.unsw.edu.au/~gernot > PGP fingerprint: 94 1E B8 28 25 FD 7C 94 20 10 92 E5 0B FF 39 8F >

1 0

Re: Am i missing something here ?
by kermit the frog 27 Apr '99

27 Apr '99

Well, ive attached the source code of my program. To anser to your question, recv is initialized to task=6; ltherad=0; i know that my program starts with task=5 so im using the next task available. Cervi~no Ulises <kermit(a)tower.com.ar> <c-3087-2(a)unrctu.edu.ar> ...............................................................................

1 0

Re: Am i missing something here ?
by Michael Hohmuth 27 Apr '99

27 Apr '99

kermit the frog <kermit(a)tower.com.ar> writes: > Heres the thing, whenever I start 2 or more task/threads that contain some > sort of a 'pause' in the for l4_i386_ipc_receive(L4_NIL_ID ... it seems to > be that all tasks/threads block forever, eventhough they have a TIMEOUT of > 4 secs, sometimes even less. I think you are seeing a bug in the timeout code which I happened to fix last week. Please try the patch appended below. I'll probably also release a new Fiasco snapshot soon. BTW, does anyone think a public CVS repository for Fiasco would be helpful? If so, please email me privately. Michael -- hohmuth(a)innocent.com, hohmuth(a)inf.tu-dresden.de http://home.pages.de/~hohmuth/

2 1

Jump to page:

2025

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