Re: MIG documentation (was: libpager deadlock)

Thomas Schwinge, le Fri 09 Apr 2010 11:57:16 +0200, a écrit : > : > > Richard P. Draves, Michael B. Jones, Mary R. Thompson, MIG - THE MACH > INTERFACE GENERATOR. ps, doc. November 1989. Department of Computer >

MIG documentation (was: libpager deadlock)

Hello! On Fri, Apr 09, 2010 at 11:45:04AM +0200, Sergio Lopez wrote: > El Thu, 8 Apr 2010 16:15:00 +0200 > Samuel Thibault escribió: > > Sergio Lopez, le Thu 08 Apr 2010 16:07:20 +0200, a écrit : > > > In memory_object.defs, m_o_lock_request is defined as > > > simpleroutine, so a call to mach_ms

Re: libpager deadlock

El Thu, 8 Apr 2010 16:15:00 +0200 Samuel Thibault escribió: > Sergio Lopez, le Thu 08 Apr 2010 16:07:20 +0200, a écrit : > > In memory_object.defs, m_o_lock_request is defined as > > simpleroutine, so a call to mach_msg_trap should only enqueue the > > message and return immediately. > > Is this

Re: libpager deadlock

Sergio Lopez, le Thu 08 Apr 2010 16:07:20 +0200, a écrit : > Anyway, let's suppose that m_o_lock_request only returns when the > process has been completed. Then, why do we need an interface to nofity > its completion (m_o_lock_completed)? It seems I forgot to mention again that I really have a po

Re: libpager deadlock

El Thu, 8 Apr 2010 13:55:33 +0200 Samuel Thibault escribió: > Sergio Lopez, le Thu 08 Apr 2010 13:15:20 +0200, a écrit : > > > So it's really hung in the kernel. And indeed, even if from > > > the interface it would seem like it could be asynchronous, > > > the memory_object_lock_completed() call

Re: libpager deadlock

Sergio Lopez, le Thu 08 Apr 2010 13:15:20 +0200, a écrit : > > So it's really hung in the kernel. And indeed, even if from > > the interface it would seem like it could be asynchronous, > > the memory_object_lock_completed() call is done from the > > memory_object_lock_request function itself... >

Re: libpager deadlock

El Thu, 8 Apr 2010 00:53:02 +0200 Samuel Thibault escribió: > HEllo, > > Sergio Lopez, le Wed 07 Apr 2010 12:43:15 +0200, a écrit : > > El Sat, 27 Mar 2010 00:39:19 +0100 > > Samuel Thibault escribió: > > > From times to times, ext2fs deadlocks on the pager->interlock > > > mutex. This is an ex

Re: libpager deadlock

HEllo, Sergio Lopez, le Wed 07 Apr 2010 12:43:15 +0200, a écrit : > El Sat, 27 Mar 2010 00:39:19 +0100 > Samuel Thibault escribió: > > From times to times, ext2fs deadlocks on the pager->interlock mutex. > > This is an excerpt of what I could find in the process: > > > > #2 0x08106e59 in memory

Re: libpager deadlock

El Sat, 27 Mar 2010 00:39:19 +0100 Samuel Thibault escribió: > Hello, > > From times to times, ext2fs deadlocks on the pager->interlock mutex. > This is an excerpt of what I could find in the process: > > #2 0x08106e59 in memory_object_lock_request () > #3 0x0806fdeb in _pager_lock_object (p=

libpager deadlock

Hello, >From times to times, ext2fs deadlocks on the pager->interlock mutex. This is an excerpt of what I could find in the process: #2 0x08106e59 in memory_object_lock_request () #3 0x0806fdeb in _pager_lock_object (p=0x81c97b8, offset=0, size=827392, should_return=2, should_flush=0, lock