From: Prarit Bhargava <prarit-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: Andi Kleen <ak-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
Cc: Jonathan Corbet <corbet-T1hC0tSOHrs@public.gmane.org>,
kexec-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
jason.wessel-CWA4WttNNZF54TAoqtyWWQ@public.gmane.org,
Rusty Russell <rusty-8n+1lVoiYb80n/F98K4Iww@public.gmane.org>,
linux-doc-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Fabian Frederick <fabf-AgBVmzD5pcezQB+pC5nmwQ@public.gmane.org>,
isimatu.yasuaki-+CUm20s59erQFUHtdCDX3A@public.gmane.org,
"H. Peter Anvin" <hpa-YMNOUZJC4hwAvxtiuMwx3w@public.gmane.org>,
Masami Hiramatsu
<masami.hiramatsu.pt-FCd8Q96Dh0JBDgjK7y7TUQ@public.gmane.org>,
Andrew Morton
<akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org>,
linux-api-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Vivek Goyal <vgoyal-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Subject: Re: [PATCH V4] kernel, add bug_on_warn
Date: Tue, 28 Oct 2014 09:19:00 -0400 [thread overview]
Message-ID: <544F97C4.8000203@redhat.com> (raw)
In-Reply-To: <20141028125630.GF3274-KWJ+5VKanrL29G5dvP0v1laTQe2KTcn/@public.gmane.org>
On 10/28/2014 08:56 AM, Andi Kleen wrote:
>>> If you have a command line option to execute kdb commands you still
>>> would only have a command line option, just a slightly longer one.
>>>
>>> kdb="on, bp warn_slowpath_common sr c, go"
>>
>> KDB is not on all kernels. This would require me to go to great lengths to
>
> Repeating incorrect statements doesn't suddenly make them correct.
It does when you're introducing unnecessary complexity here Andi. You're not
listening to the original statement: I do not want to provide a modified kernel
to an end user for this simple situation anymore.
>
> Assuming KDB is compiled in the only setup needed would be the line above.
That's a HUGE assumption. It isn't and I'm still stuck in the same mess of
explaining how to recompile a kernel and/or providing a modified kernel to an
end user. That isn't a good solution.
P.
>
> -Andi
>
next prev parent reply other threads:[~2014-10-28 13:19 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-24 12:53 [PATCH V4] kernel, add bug_on_warn Prarit Bhargava
[not found] ` <1414155207-29839-1-git-send-email-prarit-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2014-10-27 18:05 ` Jason Baron
[not found] ` <544E8985.50203-JqFfY2XvxFXQT0dZR+AlfA@public.gmane.org>
2014-10-27 18:15 ` Prarit Bhargava
2014-10-28 2:32 ` Dave Young
2014-10-28 5:41 ` Masami Hiramatsu
2014-10-28 0:00 ` Yasuaki Ishimatsu
2014-10-28 12:16 ` Andi Kleen
[not found] ` <20141028121636.GC3274-KWJ+5VKanrL29G5dvP0v1laTQe2KTcn/@public.gmane.org>
2014-10-28 12:22 ` Prarit Bhargava
2014-10-28 12:29 ` Vivek Goyal
2014-10-28 12:44 ` Andi Kleen
[not found] ` <20141028124425.GD3274-KWJ+5VKanrL29G5dvP0v1laTQe2KTcn/@public.gmane.org>
2014-10-28 12:48 ` Prarit Bhargava
[not found] ` <544F90B1.1070102-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2014-10-28 12:56 ` Andi Kleen
[not found] ` <20141028125630.GF3274-KWJ+5VKanrL29G5dvP0v1laTQe2KTcn/@public.gmane.org>
2014-10-28 13:19 ` Prarit Bhargava [this message]
2014-10-28 12:55 ` Vivek Goyal
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=544F97C4.8000203@redhat.com \
--to=prarit-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
--cc=ak-VuQAYsv1563Yd54FQh9/CA@public.gmane.org \
--cc=akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org \
--cc=corbet-T1hC0tSOHrs@public.gmane.org \
--cc=fabf-AgBVmzD5pcezQB+pC5nmwQ@public.gmane.org \
--cc=hpa-YMNOUZJC4hwAvxtiuMwx3w@public.gmane.org \
--cc=isimatu.yasuaki-+CUm20s59erQFUHtdCDX3A@public.gmane.org \
--cc=jason.wessel-CWA4WttNNZF54TAoqtyWWQ@public.gmane.org \
--cc=kexec-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-api-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-doc-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=masami.hiramatsu.pt-FCd8Q96Dh0JBDgjK7y7TUQ@public.gmane.org \
--cc=rusty-8n+1lVoiYb80n/F98K4Iww@public.gmane.org \
--cc=vgoyal-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).