From owner-freebsd-hackers@FreeBSD.ORG  Sun Nov 25 18:20:45 2012
Return-Path: <owner-freebsd-hackers@FreeBSD.ORG>
Delivered-To: freebsd-hackers@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52])
 by hub.freebsd.org (Postfix) with ESMTP id 1E9A1C4B;
 Sun, 25 Nov 2012 18:20:45 +0000 (UTC) (envelope-from avg@FreeBSD.org)
Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140])
 by mx1.freebsd.org (Postfix) with ESMTP id 32ACC8FC16;
 Sun, 25 Nov 2012 18:20:43 +0000 (UTC)
Received: from porto.starpoint.kiev.ua (porto-e.starpoint.kiev.ua
 [212.40.38.100])
 by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id UAA20654;
 Sun, 25 Nov 2012 20:20:42 +0200 (EET) (envelope-from avg@FreeBSD.org)
Received: from localhost ([127.0.0.1])
 by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD))
 id 1Tcgos-000L7U-Lc; Sun, 25 Nov 2012 20:20:42 +0200
Message-ID: <50B26179.4040205@FreeBSD.org>
Date: Sun, 25 Nov 2012 20:20:41 +0200
From: Andriy Gapon <avg@FreeBSD.org>
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64;
 rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: attilio@FreeBSD.org
Subject: Re: stop_cpus_hard when multiple CPUs are panicking from an NMI
References: <CAFMmRNwb_rxYXHGtXgtcyVUJnFDx5PSeMmA_crBbeV_rtzL9Cg@mail.gmail.com>
 <50A5F12C.1050902@FreeBSD.org>
 <CAJ-FndAB+7KRAE91L9634eXgzqgrizwtwCBC7AAg+0EX89TEBQ@mail.gmail.com>
 <50A63D1D.9090500@FreeBSD.org>
 <CAJ-FndDC1QCytXDJqVkism_5VoLNo_OzZxNEQ9NHx63HC=GTNg@mail.gmail.com>
 <50A65208.4050804@FreeBSD.org>
 <CAJ-FndADxJtYPX2-cQnqJoLhzYtJMidG1DPPY+6Dtf4rVw_zrw@mail.gmail.com>
 <50B21545.5060807@FreeBSD.org>
 <CAJ-FndDVt8VRA4kQipT5Lm+o2KRRum9NKWorfeAucwR=hJ0uDw@mail.gmail.com>
 <50B22DA0.9080207@FreeBSD.org>
 <CAJ-FndA5SfW7EXLX8DQezYPxBeavv0ET+fTMj+PhsQhnKK=X9g@mail.gmail.com>
In-Reply-To: <CAJ-FndA5SfW7EXLX8DQezYPxBeavv0ET+fTMj+PhsQhnKK=X9g@mail.gmail.com>
X-Enigmail-Version: 1.4.6
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: freebsd-hackers@FreeBSD.org, Ryan Stone <rysto32@gmail.com>
X-BeenThere: freebsd-hackers@freebsd.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: Technical Discussions relating to FreeBSD
 <freebsd-hackers.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-hackers>, 
 <mailto:freebsd-hackers-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-hackers>
List-Post: <mailto:freebsd-hackers@freebsd.org>
List-Help: <mailto:freebsd-hackers-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>,
 <mailto:freebsd-hackers-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 25 Nov 2012 18:20:45 -0000

on 25/11/2012 20:05 Attilio Rao said the following:
> If you really want to do something like that please rename
> s/generic_stop_cpus/generic_stop_butself() or similar convention and I
> may be not opposed to it.

As we discussed before, anything else besides "all but self" does not make
sense.  So I am not sure what's the point of being that verbose in the naming.

-- 
Andriy Gapon