9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Axel Belinfante <Axel.Belinfante@cs.utwente.nl>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] lock loop messages (anything particular I should do?)
Date: Sat,  5 Apr 2003 00:51:36 +0200	[thread overview]
Message-ID: <200304042251.h34Mpb502659@zamenhof.cs.utwente.nl> (raw)
In-Reply-To: Your message of "Fri, 04 Apr 2003 17:12:27 -0500." <b1ab776451bd6968381861d30d65d6a8@plan9.bell-labs.com>

> > lock 0x8029bd68 loop key 0xdeaddead pc 0x80104e08 held by pc 0x80104e08 pro
> c 486
>
> The numbers are irrelevant to me.  You have to look at them through
> your kernel.

Ok. I was wondering wether it meant something that the same pc number
appeared twice in the lock line. Or is it just one number that gets
printed twice?


Acid tells me:

term% acid 9pcdisk
9pcdisk:386 plan 9 boot image

/sys/lib/acid/port
/sys/lib/acid/386
acid: src(0x80104e08)
/sys/src/9/pc/mmu.c:332
 327
 328		mach0 = MACHP(0);
 329
 330		lock(&mmukmaplock);
 331
>332		if((pte = mmuwalk(mach0->pdb, va, 1, 0)) == nil){
 333			unlock(&mmukmaplock);
 334			return 0;
 335		}
 336		if(!(*pte & PTESIZE) && mmuwalk(mach0->pdb, va, 2, 0) == nil){
 337			unlock(&mmukmaplock);
acid:

My /sys/src/9/pc/mmu.c is of Apr 11 2002.
In case it helpful: I compiled that kernel on Feb 18 2003.


Axel.



  reply	other threads:[~2003-04-04 22:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-04 21:52 Axel Belinfante
2003-04-04 22:03 ` Sape Mullender
2003-04-04 22:03 ` Axel Belinfante
2003-04-04 22:12   ` Sape Mullender
2003-04-04 22:51     ` Axel Belinfante [this message]
2003-04-05  2:00       ` David Presotto

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=200304042251.h34Mpb502659@zamenhof.cs.utwente.nl \
    --to=axel.belinfante@cs.utwente.nl \
    --cc=9fans@cse.psu.edu \
    /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).