From owner-freebsd-threads@FreeBSD.ORG Tue Jun 8 01:10:23 2004 Return-Path: Delivered-To: freebsd-threads@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BD2EB16A4CE; Tue, 8 Jun 2004 01:10:23 +0000 (GMT) Received: from daintree.corp.yahoo.com (daintree.corp.yahoo.com [216.145.52.172]) by mx1.FreeBSD.org (Postfix) with ESMTP id 81DF743D4C; Tue, 8 Jun 2004 01:10:23 +0000 (GMT) (envelope-from peter@yahoo-inc.com) Received: by daintree.corp.yahoo.com (Postfix, from userid 2154) id 7012D8826; Mon, 7 Jun 2004 18:10:23 -0700 (PDT) From: Peter Wemm To: freebsd-amd64@freebsd.org Date: Mon, 7 Jun 2004 18:10:22 -0700 User-Agent: KMail/1.6.1 References: <20040607215054.GA41798@cat.robbins.dropbear.id.au> <40C51203.8050508@freebsd.org> In-Reply-To: <40C51203.8050508@freebsd.org> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200406071810.23069.peter@wemm.org> cc: David Xu cc: freebsd-threads@freebsd.org Subject: Re: [tjr@FreeBSD.org: cvs commit:src/lib/libpthread/arch/amd64/amd64 context.S] X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Jun 2004 01:10:23 -0000 On Monday 07 June 2004 06:10 pm, David Xu wrote: > Is there any reason to use memory indirect jump ? did you > have benchmarked context switch speed before and after this commit ? > I won't use such indirect jump in speed sensitive case, it is > not CPU branch trace cache friendly, it is better to use > ret to match call in up level. Because the return address is already on the higher level stack frame, and copying it (read/write/ret) is more awkward than the read+indirect jump. Unfortunately, we can't indirectly access the flags register. > David Xu > > Tim Robbins wrote: > > Anyone who has resorted to using libc_r instead of libpthread on > > amd64 should update their sources (ensuring they get context.S > > revision 1.6), rebuild and reinstall libpthread (or world), then > > give it another try. The bug I just fixed looks to have been > > responsible for the mysterious crashes I was seeing in > > Mozilla/Firefox, XMMS and GNOME. > > > > > > Tim > > > > ----- Forwarded message from "Tim J. Robbins" > > ----- > > > > From: "Tim J. Robbins" > > Date: Mon, 7 Jun 2004 21:25:17 +0000 (UTC) > > To: src-committers@FreeBSD.org, cvs-src@FreeBSD.org, > > cvs-all@FreeBSD.org > > Subject: cvs commit: src/lib/libpthread/arch/amd64/amd64 context.S > > X-FreeBSD-CVS-Branch: HEAD > > Precedence: bulk > > X-Loop: FreeBSD.ORG > > X-Bogosity: No, tests=bogofilter, spamicity=0.000000, > > version=0.15.7 > > > > tjr 2004-06-07 21:25:16 UTC > > > > FreeBSD src repository > > > > Modified files: > > lib/libpthread/arch/amd64/amd64 context.S > > Log: > > Avoid clobbering the red zone when running on the new context's > > stack in _amd64_restore_context(). > > > > Revision Changes Path > > 1.6 +5 -0 > > src/lib/libpthread/arch/amd64/amd64/context.S > > > > ----- End forwarded message ----- > > _______________________________________________ > > freebsd-threads@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-threads > > To unsubscribe, send any mail to > > "freebsd-threads-unsubscribe@freebsd.org" > > _______________________________________________ > freebsd-amd64@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 > To unsubscribe, send any mail to > "freebsd-amd64-unsubscribe@freebsd.org" -- Peter Wemm - peter@wemm.org; peter@FreeBSD.org; peter@yahoo-inc.com "All of this is for nothing if we don't go to the stars" - JMS/B5