From: Peter Zijlstra <peterz@infradead.org>
To: daniel.thompson@linaro.org, x86@kernel.org
Cc: sumit.garg@linaro.org, jason.wessel@windriver.com,
dianders@chromium.org, kgdb-bugreport@lists.sourceforge.net,
linux-kernel@vger.kernel.org, pmladek@suse.com,
sergey.senozhatsky@gmail.com, will@kernel.org
Subject: x86/entry vs kgdb
Date: Mon, 25 May 2020 10:36:05 +0200 [thread overview]
Message-ID: <20200525083605.GB317569@hirez.programming.kicks-ass.net> (raw)
Hi!
Since you seem to care about kgdb, I figured you might want to fix this
before I mark it broken on x86 (we've been considering doing that for a
while).
AFAICT the whole debugreg usage of kgdb-x86_64 is completely hosed; it
doesn't respsect the normal exclusion zones as per arch_build_bp_info().
That is, breakpoints must never be in:
- in the cpu_entry_area
- in .entry.text
- in .noinstr.text
- in anything else marked NOKPROBE
by not respecting these constraints it is trivial to completely and
utterly hose the machine. The entry rework that is current underway will
explicitly not deal with #DB triggering in any of those places.
next reply other threads:[~2020-05-25 8:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-25 8:36 Peter Zijlstra [this message]
2020-05-25 9:18 ` x86/entry vs kgdb Peter Zijlstra
2020-05-26 16:16 ` Daniel Thompson
2020-05-26 16:28 ` Peter Zijlstra
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=20200525083605.GB317569@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=daniel.thompson@linaro.org \
--cc=dianders@chromium.org \
--cc=jason.wessel@windriver.com \
--cc=kgdb-bugreport@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=pmladek@suse.com \
--cc=sergey.senozhatsky@gmail.com \
--cc=sumit.garg@linaro.org \
--cc=will@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 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.