From: Oleg Nesterov <oleg@redhat.com>
To: Andy Lutomirski <luto@amacapital.net>
Cc: Andrei Vagin <avagin@gmail.com>,
LKML <linux-kernel@vger.kernel.org>, X86 ML <x86@kernel.org>,
Andy Lutomirski <luto@kernel.org>,
Cyrill Gorcunov <gorcunov@openvz.org>
Subject: Re: x86: A process doesn't stop on hw breakpoints sometimes
Date: Wed, 25 May 2016 01:29:58 +0200 [thread overview]
Message-ID: <20160524232958.GA14477@redhat.com> (raw)
In-Reply-To: <CALCETrWsO3h-trontU121d-2YnpJ=7aqYDngzr4PpAeFfC14Sw@mail.gmail.com>
On 05/23, Andy Lutomirski wrote:
>
> I'm guessing you're either hitting a subtle bug in the mess that is
> breakpoint handling or you're hitting a bug in perf's context switch
> code.
yes, same feeling...
> Given that the breakpoint gets missed many times in a row,
yes, the child specially tries to hit the same bp again and again,
> this is
> presumably either a bug in breakpoint programming (i.e. the thing
> isn't actually set in dr0/dr7) or a bug in the bp state tracking.
or some buf in perf_sched_in(). In fact this is what I think now, but
I can be wrong.
> If
> it were a bug in RF flag handling, I'd expect it to skip once and trip
> the second time through.
Exactly.
It would be nice to ensure that this problem has actually gone, and how.
So, Andrei, if you have any motivation, we can continue. The next step
needs a simple kernel patch or kernel module which allows to read dr0/dr7
and print these registers in the "fail" loop.
Oleg.
prev parent reply other threads:[~2016-05-24 23:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-23 23:05 x86: A process doesn't stop on hw breakpoints sometimes Andrei Vagin
2016-05-24 1:28 ` Andrei Vagin
2016-05-24 5:30 ` Andrei Vagin
2016-05-24 1:37 ` Andy Lutomirski
2016-05-24 23:29 ` Oleg Nesterov [this message]
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=20160524232958.GA14477@redhat.com \
--to=oleg@redhat.com \
--cc=avagin@gmail.com \
--cc=gorcunov@openvz.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=luto@kernel.org \
--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