From owner-freebsd-mips@FreeBSD.ORG Sun Oct 23 17:18:54 2011 Return-Path: Delivered-To: freebsd-mips@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DBC91106566C for ; Sun, 23 Oct 2011 17:18:53 +0000 (UTC) (envelope-from gonzo@hq.bluezbox.com) Received: from hq.bluezbox.com (hq.bluezbox.com [70.38.37.145]) by mx1.freebsd.org (Postfix) with ESMTP id 970048FC15 for ; Sun, 23 Oct 2011 17:18:53 +0000 (UTC) Received: from [24.87.53.93] (helo=[192.168.1.116]) by hq.bluezbox.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.73 (FreeBSD)) (envelope-from ) id 1RI1D4-0008OP-Ht; Sun, 23 Oct 2011 09:47:43 -0700 Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: text/plain; charset=us-ascii From: Oleksandr Tymoshenko In-Reply-To: Date: Sun, 23 Oct 2011 09:47:49 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: <072342B7-4DED-4F0B-ADAE-BCCA8A4A63D4@bluezbox.com> References: To: Juli Mallett X-Mailer: Apple Mail (2.1084) Sender: gonzo@hq.bluezbox.com X-Spam-Level: ---- X-Spam-Report: Spam detection software, running on the system "hq.bluezbox.com", has identified this incoming email as possible spam. The original message has been attached to this so you can view it (if it isn't spam) or label similar future email. If you have any questions, see The administrator of that system for details. Content preview: On 2011-10-21, at 3:27 PM, Juli Mallett wrote: > On Fri, Oct 21, 2011 at 14:56, Rohit J wrote: >> the big picture story is that >> as a partial fix to using octeon specific very large mult instructions >> in our freebsd kernel >> (for crypto related ops), we had initially disabled >> interrupts=>context switches > > Assuming you're using the stuff in-tree, that's my fault :) > >> Need to see if there is a better way to do it. >> am now trying to see if it makes sense to save those registers and >> remove the disable interrupt constraint for running these large multiplication >> instructions. >> will be adapting the (multiplication context save/restore) >> in the octeon HRM and will revert if i have any further questions. > > gonzo@ has incomplete patches, you may want to ask him. Alternately, > look at how FPU context is lazily switched on other architectures. > [...] Content analysis details: (-4.5 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -1.8 ALL_TRUSTED Passed through trusted hosts only via SMTP -2.6 BAYES_00 BODY: Bayesian spam probability is 0 to 1% [score: 0.0000] -0.1 AWL AWL: From: address is in the auto white-list Cc: freebsd-mips Subject: Re: Assembler complains about use of $at after ".set noat" on sd instr X-BeenThere: freebsd-mips@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to MIPS List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Oct 2011 17:18:54 -0000 On 2011-10-21, at 3:27 PM, Juli Mallett wrote: > On Fri, Oct 21, 2011 at 14:56, Rohit J wrote: >> the big picture story is that >> as a partial fix to using octeon specific very large mult = instructions >> in our freebsd kernel >> (for crypto related ops), we had initially disabled >> interrupts=3D>context switches >=20 > Assuming you're using the stuff in-tree, that's my fault :) >=20 >> Need to see if there is a better way to do it. >> am now trying to see if it makes sense to save those registers and >> remove the disable interrupt constraint for running these large = multiplication >> instructions. >> will be adapting the (multiplication context save/restore) >> in the octeon HRM and will revert if i have any further questions. >=20 > gonzo@ has incomplete patches, you may want to ask him. Alternately, > look at how FPU context is lazily switched on other architectures. >=20 Here is the latest version of my patch: http://people.freebsd.org/~gonzo/patches/cop2.diff context is saved for kernel threads only, usage of crypto stuff from = userland is not supported.=