From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <107b9d3b4608bd0f2e8f14efe7139e1e@plan9.bell-labs.com> From: David Presotto To: 9fans@cse.psu.edu Subject: Re: [9fans] lock loop messages (anything particular I should do?) In-Reply-To: <200304042251.h34Mpb502659@zamenhof.cs.utwente.nl> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="upas-aigdruywfvkokzerzbdwpkyblr" Date: Fri, 4 Apr 2003 21:00:56 -0500 Topicbox-Message-UUID: 8b3450da-eacb-11e9-9e20-41e7f4b1d025 This is a multi-part message in MIME format. --upas-aigdruywfvkokzerzbdwpkyblr Content-Disposition: inline Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Looks to me like lock(&mmukmaplock) should really be an ilock since mmukmapsync() gets called by trap (i.e. in an interrupt) and by mmukmap() called in upamalloc() (not necessarily in an interrupt). I'll change it and update. Thanks for the report. --upas-aigdruywfvkokzerzbdwpkyblr Content-Type: message/rfc822 Content-Disposition: inline Received: from plan9.cs.bell-labs.com ([135.104.9.2]) by plan9; Fri Apr 4 17:52:19 EST 2003 Received: from mail.cse.psu.edu ([130.203.4.6]) by plan9; Fri Apr 4 17:52:17 EST 2003 Received: from psuvax1.cse.psu.edu (psuvax1.cse.psu.edu [130.203.30.6]) by mail.cse.psu.edu (CSE Mail Server) with ESMTP id B0EC119BC3; Fri, 4 Apr 2003 17:52:06 -0500 (EST) Delivered-To: 9fans@cse.psu.edu Received: from utrhcs.cs.utwente.nl (utrhcs.cs.utwente.nl [130.89.10.247]) by mail.cse.psu.edu (CSE Mail Server) with ESMTP id 2DF2E19BC1 for <9fans@cse.psu.edu>; Fri, 4 Apr 2003 17:51:41 -0500 (EST) Received: from zeus.cs.utwente.nl (zeus.cs.utwente.nl [130.89.10.12]) by utrhcs.cs.utwente.nl (8.12.9/8.12.9) with ESMTP id h34MpdYp004059 for <9fans@cse.psu.edu>; Sat, 5 Apr 2003 00:51:39 +0200 (MET DST) Received: from zamenhof.cs.utwente.nl (zamenhof [130.89.13.77]) by zeus.cs.utwente.nl (8.12.9/8.12.9) with ESMTP id h34MpbCr026449 for <9fans@cse.psu.edu>; Sat, 5 Apr 2003 00:51:38 +0200 (MEST) Received: from localhost (belinfan@localhost) by zamenhof.cs.utwente.nl (8.11.6+Sun/8.10.2) with SMTP id h34Mpb502659 for <9fans@cse.psu.edu>; Sat, 5 Apr 2003 00:51:37 +0200 (MEST) Message-Id: <200304042251.h34Mpb502659@zamenhof.cs.utwente.nl> X-Authentication-Warning: zamenhof.cs.utwente.nl: belinfan@localhost didn't use HELO protocol To: 9fans@cse.psu.edu Subject: Re: [9fans] lock loop messages (anything particular I should do?) In-reply-to: Your message of "Fri, 04 Apr 2003 17:12:27 -0500." References: From: Axel Belinfante X-Organisation: University of Twente, Department of Computer Science, Formal Methods and Tools Group, PO Box 217, NL-7500 AE Enschede, The Netherlands X-Phone: +31 53 4893774 X-Telefax: +31 53 4893247 X-Face: 3YGZY^_!}k]>-k'9$LK?8GXbi?vs=2v*ut,/8z,z!(QNBk_>~:~"MJ_%i`sLLqGN,DGbkT@ N\jhX/jNLTz2hO_R"*RF(%bRvk+M,iU7SvVJtC*\B6Ud<7~`MGMp7rCI6LVp=%k=HE?-UCV?[p\$R? mI\n2/!#3/wZZsa[m7d;PKWiuH6'~ X-Virus-Scanned: by AMaViS-perl11-milter (http://amavis.org/) Sender: 9fans-admin@cse.psu.edu Errors-To: 9fans-admin@cse.psu.edu X-BeenThere: 9fans@cse.psu.edu X-Mailman-Version: 2.0.11 Precedence: bulk Reply-To: 9fans@cse.psu.edu List-Id: Fans of the OS Plan 9 from Bell Labs <9fans.cse.psu.edu> List-Archive: Date: Sat, 05 Apr 2003 00:51:36 +0200 > > 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. --upas-aigdruywfvkokzerzbdwpkyblr--