From: "H. Peter Anvin" <hpa@zytor.com>
To: Jeff Merkey <linux.mdb@gmail.com>, linux-kernel@vger.kernel.org
Cc: tglx@linutronix.de, mingo@redhat.com, x86@kernel.org,
peterz@infradead.org, luto@kernel.org
Subject: Re: [PATCH v2] Fix INT1 Exception with unregistered breakpoints
Date: Mon, 14 Dec 2015 20:49:40 -0800 [thread overview]
Message-ID: <9ADACBE2-9CAA-4993-BF03-502DEF0D365D@zytor.com> (raw)
In-Reply-To: <CAO6TR8Wz8p3425amCjpvBu4N8qfPzeRJ7MqoEoOabsNBd_wk8w@mail.gmail.com>
On December 14, 2015 4:49:51 PM PST, Jeff Merkey <linux.mdb@gmail.com> wrote:
>On 12/14/15, Jeff Merkey <linux.mdb@gmail.com> wrote:
>> Please consider the attached patch.
>>
>> SUMMARY
>>
>> This patch corrects a hard lockup failure of the system kernel if the
>> operating system receives a breakpoint exception at a code execution
>> address which was not registered with the operating system. The
>patch
>> allows kernel debuggers, application profiling and performance
>modules,
>> and external debugging tools to work better together at sharing the
>> breakpoint registers on the platform in a way that they do not cause
>> errors and system faults, and enables the full feature set in the
>> breakpoint API. If a kernel application triggers a breakpoint
>> or programs one in error, this patch will catch the condition and
>report
>> it to the system log without the operating system experiencing a
>system
>> fault. There are several consumers of the Linux Breakpoint API and
>all
>> of them can and sometimes do cause the condition this patch corrects.
>>
>
>Peter,
>
>Is that the type of summary that meets the standards. I tried to be
>concise.
>
>Jeff
It would be good if you could be a bit more precise. In particular, explain how and why the condition can appear rather than just explain that it can.
--
Sent from my Android device with K-9 Mail. Please excuse brevity and formatting.
next prev parent reply other threads:[~2015-12-15 4:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-14 23:43 Jeff Merkey
2015-12-15 0:49 ` Jeff Merkey
2015-12-15 4:49 ` H. Peter Anvin [this message]
2015-12-15 4:52 ` Jeff Merkey
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=9ADACBE2-9CAA-4993-BF03-502DEF0D365D@zytor.com \
--to=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux.mdb@gmail.com \
--cc=luto@kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=x86@kernel.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
all inboxes | Powered by JetHome®