From: David Howells <dhowells@redhat.com>
To: Heiko Carstens <heiko.carstens@de.ibm.com>
Cc: dhowells@redhat.com, David VomLehn <dvomlehn@cisco.com>,
to@dvomlehn-lnx2.corp.sa.net,
"linux-arch@vger.kernel.org"@cisco.comlinux-arch@vger.kernel.org,
akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
maint_arch@dvomlehn-lnx2.corp.sa.net
Subject: Re: [PATCH 1/23] Make register values available to panic notifiers
Date: Mon, 12 Apr 2010 13:20:02 +0100 [thread overview]
Message-ID: <24979.1271074802@redhat.com> (raw)
In-Reply-To: <20100412120330.GA2566@osiris.boeblingen.de.ibm.com>
Heiko Carstens <heiko.carstens@de.ibm.com> wrote:
> Wouldn't it be much easier to implement panic with an illegal op and let
> the exception handler set up the pt regs structure instead? Just like some
> architectures do that already for warnings.
No, not necessarily. panic() is varargs.
David
WARNING: multiple messages have this Message-ID (diff)
From: David Howells <dhowells@redhat.com>
To: Heiko Carstens <heiko.carstens@de.ibm.com>
Cc: dhowells@redhat.com, David VomLehn <dvomlehn@cisco.com>,
to@dvomlehn-lnx2.corp.sa.net,
"linux-arch@vger.kernel.org"@cisco.com,
linux-arch@vger.kernel.org, akpm@linux-foundation.org,
linux-kernel@vger.kernel.org,
maint_arch@dvomlehn-lnx2.corp.sa.net
Subject: Re: [PATCH 1/23] Make register values available to panic notifiers
Date: Mon, 12 Apr 2010 13:20:02 +0100 [thread overview]
Message-ID: <24979.1271074802@redhat.com> (raw)
In-Reply-To: <20100412120330.GA2566@osiris.boeblingen.de.ibm.com>
Heiko Carstens <heiko.carstens@de.ibm.com> wrote:
> Wouldn't it be much easier to implement panic with an illegal op and let
> the exception handler set up the pt regs structure instead? Just like some
> architectures do that already for warnings.
No, not necessarily. panic() is varargs.
David
next prev parent reply other threads:[~2010-04-12 12:20 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-12 6:06 [PATCH 1/23] Make register values available to panic notifiers David VomLehn
2010-04-12 6:06 ` David VomLehn
2010-04-12 6:24 ` Mike Frysinger
2010-04-12 6:24 ` Mike Frysinger
2010-04-12 11:16 ` David Howells
2010-04-12 11:16 ` David Howells
2010-04-14 20:41 ` David VomLehn
2010-04-14 23:52 ` David Howells
2010-04-14 23:58 ` David Miller
2010-04-14 20:42 ` David VomLehn
2010-04-12 12:03 ` Heiko Carstens
2010-04-12 12:03 ` Heiko Carstens
2010-04-12 12:20 ` David Howells [this message]
2010-04-12 12:20 ` David Howells
2010-04-12 12:24 ` Russell King
2010-04-12 12:24 ` Russell King
2010-04-14 20:47 ` David VomLehn
2010-04-12 12:27 ` Russell King
2010-04-12 12:27 ` Russell King
2010-04-12 12:45 ` David Howells
2010-04-14 21:04 ` David VomLehn
2010-04-12 13:35 ` Martin Schwidefsky
2010-04-12 13:35 ` Martin Schwidefsky
2010-04-14 21:09 ` David VomLehn
2010-04-14 21:00 ` David VomLehn
2010-04-15 2:54 ` Paul Mundt
-- strict thread matches above, loose matches on Subject: below --
2010-04-12 6:03 David VomLehn
2010-04-12 21:57 ` Andrew Morton
2010-04-14 22:02 ` David VomLehn
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=24979.1271074802@redhat.com \
--to=dhowells@redhat.com \
--cc="linux-arch@vger.kernel.org"@cisco.comlinux-arch \
--cc=dvomlehn@cisco.com \
--cc=heiko.carstens@de.ibm.com \
--cc=to@dvomlehn-lnx2.corp.sa.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.