From mboxrd@z Thu Jan  1 00:00:00 1970
From: erik quanstrom <quanstro@quanstro.net>
Date: Mon, 30 Dec 2013 23:40:36 -0500
To: 9fans@9fans.net
Message-ID: <a904a257f1455cbd4fab9cf6ae3d19e4@brasstown.quanstro.net>
In-Reply-To: <20131231012446.GB10407@dinah>
References: <3377fb7342a3ff404eae1ba724f11130@mikro>
	<20131231010617.GA10407@dinah> <20131231012446.GB10407@dinah>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Subject: Re: [9fans] 9front sleep interrupted in kproc?
Topicbox-Message-UUID: aa0546ec-ead8-11e9-9d60-3106f5b1d025

On Mon Dec 30 20:26:47 EST 2013, ality@pbrane.org wrote:
> Anthony Martin <ality@pbrane.org> once said:
> > erik quanstrom <quanstro@quanstro.net> once said:
> > > since kprocs don't get notes (it's an error to write to the note file),
> > > sleep in a kproc can't get interrupted.  this code will never fire.
> >
> > It looks like they can on 9front.
>
> Actually, this isn't just 9front. All of the network
> medium receive kprocs (e.g., etherread4) can be sent
> notes (only by the kernel, of course).

there are no calls to procalarm() outside of sysalarm (the alarm
system call) in either the official sources or 9atom (either the 64bit
or regular kernels).

if i've pulled correctly, 9front has one procalarm, and it's in the vesa code
with a waserror at the ready.

this patch addresses a problem that doesn't exist.  it seems to imply
that notes can come to kprocs out of the blue.  and i believe this is
not correct.

- erik