From: Dave Hansen <dave.hansen@intel.com>
To: Peter Zijlstra <peterz@infradead.org>, "H. Peter Anvin" <hpa@zytor.com>
Cc: x86@kernel.org, tglx@kernel.org, mingo@redhat.com, bp@alien8.de,
dave.hansen@linux.intel.com, steve.wahl@hpe.com,
justin.ernst@hpe.com, kyle.meyer@hpe.com,
dimitri.sivanich@hpe.com, russ.anderson@hpe.com,
linux-kernel@vger.kernel.org, mhiramat@kernel.org,
Matt Mullins <mmullins@fb.com>
Subject: Re: [PATCH] x86: Drop KGDB support
Date: Wed, 28 Oct 2026 08:10:54 -0700 [thread overview]
Message-ID: <27a7b4b6-23da-4469-9161-2ce44e8ac2a9@intel.com> (raw)
In-Reply-To: <20261028142625.GU2668564@noisy.programming.kicks-ass.net>
On 10/28/26 07:26, Peter Zijlstra wrote:
...
> Also, when was the last time you used KGDB? I think I've tried it once,
> some 20 years ago, and haven't bothered since -- it was *that* good 🙂
I can't remember the last time I used it. I also grepped through all of
my stashed-away kernel configs I've been using for the past 15 or so
years. The only place I even see it configured in is in distro-derived
configs. None of my trimmed down debug configs.
There seems to be approximately one clear commit that shows anyone using
the x86 kgdb.c in the last decade:
commit 71ab8323cc357c68985a2d6fc6cfc22b1dbbc1c3
Author: Matt Mullins <mmullins@fb.com>
Date: Fri May 31 12:47:54 2019 -0700
x86/kgdb: Return 0 from kgdb_arch_set_breakpoint()
The only question for me at this point would be whether we should just
config it out for a couple of releases rather than removing it outright.
next prev parent reply other threads:[~2026-10-28 15:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-28 12:21 Peter Zijlstra
2026-10-28 14:15 ` H. Peter Anvin
2026-10-28 14:26 ` Peter Zijlstra
2026-10-28 15:10 ` Dave Hansen [this message]
2026-10-28 19:58 ` Steve Wahl
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=27a7b4b6-23da-4469-9161-2ce44e8ac2a9@intel.com \
--to=dave.hansen@intel.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=dimitri.sivanich@hpe.com \
--cc=hpa@zytor.com \
--cc=justin.ernst@hpe.com \
--cc=kyle.meyer@hpe.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=mingo@redhat.com \
--cc=mmullins@fb.com \
--cc=peterz@infradead.org \
--cc=russ.anderson@hpe.com \
--cc=steve.wahl@hpe.com \
--cc=tglx@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
all inboxes | Powered by JetHome®