From: Borislav Petkov <bp@alien8.de>
To: Oleg Nesterov <oleg@redhat.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
Jan Kratochvil <jan.kratochvil@redhat.com>,
x86@kernel.org, tdevries@suse.de, linux-kernel@vger.kernel.org,
andrew.cooper3@citrix.com,
Frederic Weisbecker <fweisbec@gmail.com>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH v2] x86/debug: Fix DR6 handling
Date: Fri, 29 Jan 2021 17:27:41 +0100 [thread overview]
Message-ID: <20210129162741.GC27841@zn.tnic> (raw)
In-Reply-To: <20210129154109.GA1391@redhat.com>
On Fri, Jan 29, 2021 at 04:41:09PM +0100, Oleg Nesterov wrote:
> This seems to fix the problem reported by Jan, see his test-case below.
Should it be part of
tools/testing/selftests/breakpoints/
?
tglx has one destined for there already, wouldn't hurt to have a second
one:
https://lkml.kernel.org/r/87eei4d4k6.fsf@nanos.tec.linutronix.de
after applying kernel coding style to that one.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
next prev parent reply other threads:[~2021-01-29 16:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-28 18:20 [PATCH] x86/debug: 'Fix' ptrace dr6 output Peter Zijlstra
2021-01-28 18:45 ` Andrew Cooper
2021-01-28 20:21 ` Tom de Vries
2021-01-28 21:16 ` [PATCH v2] x86/debug: Fix DR6 handling Peter Zijlstra
2021-01-28 23:28 ` [PATCH] selftests: breakpoints: Add "WINE" test for x86 Thomas Gleixner
[not found] ` <YBPQq6ccKL68aIZg@hirez.programming.kicks-ass.net>
2021-01-29 19:09 ` Thomas Gleixner
[not found] ` <20210129154109.GA1391@redhat.com>
2021-01-29 16:27 ` Borislav Petkov [this message]
[not found] ` <20210129144816.GB27841@zn.tnic>
2021-01-29 16:59 ` [PATCH v2] x86/debug: Fix DR6 handling Tom de Vries
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=20210129162741.GC27841@zn.tnic \
--to=bp@alien8.de \
--cc=andrew.cooper3@citrix.com \
--cc=fweisbec@gmail.com \
--cc=jan.kratochvil@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oleg@redhat.com \
--cc=peterz@infradead.org \
--cc=tdevries@suse.de \
--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 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.