From mboxrd@z Thu Jan 1 00:00:00 1970 Received: with ECARTIS (v1.0.0; list linux-mips); Tue, 08 Oct 2013 14:55:32 +0200 (CEST) Received: from localhost.localdomain ([127.0.0.1]:39370 "EHLO linux-mips.org" rhost-flags-OK-OK-OK-FAIL) by eddie.linux-mips.org with ESMTP id S6832660Ab3JHMzaco1jk (ORCPT ); Tue, 8 Oct 2013 14:55:30 +0200 Received: from scotty.linux-mips.net (localhost.localdomain [127.0.0.1]) by scotty.linux-mips.net (8.14.7/8.14.4) with ESMTP id r98CtTCk030714; Tue, 8 Oct 2013 14:55:29 +0200 Received: (from ralf@localhost) by scotty.linux-mips.net (8.14.7/8.14.7/Submit) id r98CtTHu030713; Tue, 8 Oct 2013 14:55:29 +0200 Date: Tue, 8 Oct 2013 14:55:29 +0200 From: Ralf Baechle To: Markos Chandras Cc: linux-mips@linux-mips.org, Leonid Yegoshin Subject: Re: [PATCH] MIPS: Print correct PC in trace dump after NMI exception Message-ID: <20131008125529.GK3098@linux-mips.org> References: <1381232371-25017-1-git-send-email-markos.chandras@imgtec.com> <20131008121546.GI1615@linux-mips.org> <5253FB20.7050909@imgtec.com> <20131008123859.GK1615@linux-mips.org> <5253FDFC.80007@imgtec.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5253FDFC.80007@imgtec.com> User-Agent: Mutt/1.5.21 (2010-09-15) Return-Path: X-Envelope-To: <"|/home/ecartis/ecartis -s linux-mips"> (uid 0) X-Orcpt: rfc822;linux-mips@linux-mips.org Original-Recipient: rfc822;linux-mips@linux-mips.org X-archive-position: 38271 X-ecartis-version: Ecartis v1.0.0 Sender: linux-mips-bounce@linux-mips.org Errors-to: linux-mips-bounce@linux-mips.org X-original-sender: ralf@linux-mips.org Precedence: bulk List-help: List-unsubscribe: List-software: Ecartis version 1.0.0 List-Id: linux-mips X-List-ID: linux-mips List-subscribe: List-owner: List-post: List-archive: X-list: linux-mips On Tue, Oct 08, 2013 at 01:43:40PM +0100, Markos Chandras wrote: > markos > > On 10/08/13 13:38, Ralf Baechle wrote: > >On Tue, Oct 08, 2013 at 01:31:28PM +0100, Markos Chandras wrote: > > > >>>If you were afraid gas might use $1 expanding this macro instruction - no, > >>>it won't. A belt & suspenders approach might be to drop in a ".set noat"; > >>>it would make the assembler throw an error if should ever see the need to > >>>use $1. > >>> > >>yeah i don't think the assembler would pick $1 in this case but we > >>could add ".set noat" just to be safe i suppose. > >> > >>Thanks for the review. Could you fix these problems for me or should > >>i submit a new patch? > > > >It's trivial enough so I'm going to do it. > > > >The NMI handler btw. was already wrapped with .set push; .set noat; ... > >.set pop. > > > > Ralf > > > yeah i just noticed. Thank you! Signature at the top, content at the bottom? Sigh ... :-) I've pushed a fresh upstream-sfr with this patch applied. This will be the last change for the day as I want to concentrate on other code. Ralf