From: Anthony Martin <ality@pbrane.org>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] 9front sleep interrupted in kproc?
Date: Mon, 30 Dec 2013 17:06:17 -0800 [thread overview]
Message-ID: <20131231010617.GA10407@dinah> (raw)
In-Reply-To: <3377fb7342a3ff404eae1ba724f11130@mikro>
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.
The following is from pc/vgavesa.c:/^vesaproc
/*
* dont wait forever here. some BIOS get stuck
* in i/o poll loop after blank/unblank for some
* reason. (Thinkpad A22p)
*/
procalarm(10000);
Cheers,
Anthony
next prev parent reply other threads:[~2013-12-31 1:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-30 17:43 erik quanstrom
2013-12-31 1:06 ` Anthony Martin [this message]
2013-12-31 1:24 ` Anthony Martin
2013-12-31 4:40 ` erik quanstrom
2013-12-31 13:17 ` cinap_lenrek
2013-12-31 14:38 ` erik quanstrom
2013-12-31 10:55 ` Charles Forsyth
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20131231010617.GA10407@dinah \
--to=ality@pbrane.org \
--cc=9fans@9fans.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).