From: Andi Kleen <ak@linux.intel.com>
To: Vivek Goyal <vgoyal@redhat.com>
Cc: Prarit Bhargava <prarit@redhat.com>,
Jonathan Corbet <corbet@lwn.net>,
kexec@lists.infradead.org, Rusty Russell <rusty@rustcorp.com.au>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
Fabian Frederick <fabf@skynet.be>,
isimatu.yasuaki@jp.fujitsu.com, "H. Peter Anvin" <hpa@zytor.com>,
Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-api@vger.kernel.org, jason.wessel@windriver.com
Subject: Re: [PATCH V4] kernel, add bug_on_warn
Date: Tue, 28 Oct 2014 05:59:27 -0700 [thread overview]
Message-ID: <20141028125927.GG3274@tassilo.jf.intel.com> (raw)
In-Reply-To: <20141028125534.GC10632@redhat.com>
> > kdb="on, bp warn_slowpath_common sr c, go"
>
> So does it already work or proposal is to make something like this work
> with kdb?
It does not work today, the missing pieces are:
- extending kdb= to execute a list of kdb commands
- extending bp to define a list of commands to execute
>
> What about the case of enabling it post boot and using a /sys file for
> that.
This would be another patch, add a sysfs file to run a list of kdb commands.
-Andi
--
ak@linux.intel.com -- Speaking for myself only
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
WARNING: multiple messages have this Message-ID (diff)
From: Andi Kleen <ak@linux.intel.com>
To: Vivek Goyal <vgoyal@redhat.com>
Cc: Prarit Bhargava <prarit@redhat.com>,
linux-kernel@vger.kernel.org, Jonathan Corbet <corbet@lwn.net>,
Andrew Morton <akpm@linux-foundation.org>,
Rusty Russell <rusty@rustcorp.com.au>,
"H. Peter Anvin" <hpa@zytor.com>,
Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>,
Fabian Frederick <fabf@skynet.be>,
isimatu.yasuaki@jp.fujitsu.com, linux-doc@vger.kernel.org,
kexec@lists.infradead.org, linux-api@vger.kernel.org,
jason.wessel@windriver.com
Subject: Re: [PATCH V4] kernel, add bug_on_warn
Date: Tue, 28 Oct 2014 05:59:27 -0700 [thread overview]
Message-ID: <20141028125927.GG3274@tassilo.jf.intel.com> (raw)
In-Reply-To: <20141028125534.GC10632@redhat.com>
> > kdb="on, bp warn_slowpath_common sr c, go"
>
> So does it already work or proposal is to make something like this work
> with kdb?
It does not work today, the missing pieces are:
- extending kdb= to execute a list of kdb commands
- extending bp to define a list of commands to execute
>
> What about the case of enabling it post boot and using a /sys file for
> that.
This would be another patch, add a sysfs file to run a list of kdb commands.
-Andi
--
ak@linux.intel.com -- Speaking for myself only
next prev parent reply other threads:[~2014-10-28 12:59 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-24 12:53 [PATCH V4] kernel, add bug_on_warn Prarit Bhargava
2014-10-24 12:53 ` Prarit Bhargava
2014-10-27 18:05 ` Jason Baron
2014-10-27 18:05 ` Jason Baron
2014-10-27 18:05 ` Jason Baron
2014-10-27 18:15 ` Prarit Bhargava
2014-10-27 18:15 ` Prarit Bhargava
2014-10-27 18:15 ` Prarit Bhargava
2014-10-28 2:32 ` Dave Young
2014-10-28 2:32 ` Dave Young
2014-10-28 5:41 ` Masami Hiramatsu
2014-10-28 5:41 ` Masami Hiramatsu
2014-10-28 0:00 ` Yasuaki Ishimatsu
2014-10-28 0:00 ` Yasuaki Ishimatsu
2014-10-28 0:00 ` Yasuaki Ishimatsu
2014-10-28 12:16 ` Andi Kleen
2014-10-28 12:16 ` Andi Kleen
2014-10-28 12:22 ` Prarit Bhargava
2014-10-28 12:22 ` Prarit Bhargava
2014-10-28 12:22 ` Prarit Bhargava
2014-10-28 12:29 ` Vivek Goyal
2014-10-28 12:29 ` Vivek Goyal
2014-10-28 12:44 ` Andi Kleen
2014-10-28 12:44 ` Andi Kleen
2014-10-28 12:48 ` Prarit Bhargava
2014-10-28 12:48 ` Prarit Bhargava
2014-10-28 12:48 ` Prarit Bhargava
2014-10-28 12:56 ` Andi Kleen
2014-10-28 12:56 ` Andi Kleen
2014-10-28 12:56 ` Andi Kleen
2014-10-28 13:19 ` Prarit Bhargava
2014-10-28 13:19 ` Prarit Bhargava
2014-10-28 13:19 ` Prarit Bhargava
2014-10-28 12:55 ` Vivek Goyal
2014-10-28 12:55 ` Vivek Goyal
2014-10-28 12:59 ` Andi Kleen [this message]
2014-10-28 12:59 ` Andi Kleen
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=20141028125927.GG3274@tassilo.jf.intel.com \
--to=ak@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=corbet@lwn.net \
--cc=fabf@skynet.be \
--cc=hpa@zytor.com \
--cc=isimatu.yasuaki@jp.fujitsu.com \
--cc=jason.wessel@windriver.com \
--cc=kexec@lists.infradead.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masami.hiramatsu.pt@hitachi.com \
--cc=prarit@redhat.com \
--cc=rusty@rustcorp.com.au \
--cc=vgoyal@redhat.com \
/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.