Date: Sat, 13 Jun 2015 10:01:32 -0400 From: "O'Connor, Daniel" <darius@dons.net.au> To: Julian Elischer <julian@freebsd.org> Cc: Maksim Yevmenkin <maksim.yevmenkin@gmail.com>, Andriy Gapon <avg@freebsd.org>, "current@freebsd.org" <current@freebsd.org> Subject: Re: obtaining a minidump from panic() called from NMI handler Message-ID: <3FCB93E6-40AA-4673-99F1-14CD145FFFAA@dons.net.au> In-Reply-To: <557C2D5F.4080005@freebsd.org> References: <CAFPOs6qsFZKMVzLEDL5X77H6s5LoTjsc4SkMWgR0D_P8RQG4YQ@mail.gmail.com> <557B1905.80307@FreeBSD.org> <CAFPOs6p5yTvdbJXPOKXuagZxj%2Bu-pE3kt5fsCWCpPVj4vktO%2Bg@mail.gmail.com> <557C2D5F.4080005@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> On 13 Jun 2015, at 09:17, Julian Elischer <julian@freebsd.org> wrote: >=20 >>> could it be that more than one CPUs get the NMI at the same time? >> i guess, its possible. is there an easy way to check for that? > hard code checks in the code so that all except the first do something = different. > (even only as a debug check).. like write to some location and loop... How about just something to the effect of.. if (curcpu !=3D cpu0) while (1) ; -- Daniel O'Connor "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3FCB93E6-40AA-4673-99F1-14CD145FFFAA>