mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Breno Leitao <leitao@debian.org>
To: Peter Zijlstra <peterz@infradead.org>
Cc: x86@kernel.org, tglx@kernel.org, mingo@redhat.com, bp@alien8.de,
	 dave.hansen@linux.intel.com, hpa@zytor.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
Subject: Re: [PATCH] x86: Drop KGDB support
Date: Mon, 2 Nov 2026 05:33:15 -0800	[thread overview]
Message-ID: <auiQKR6IhdyOCiex@gmail.com> (raw)
In-Reply-To: <20261028122124.GJ2668804@noisy.programming.kicks-ass.net>

On Wed, Oct 28, 2026 at 01:21:24PM +0100, Peter Zijlstra wrote:
> 
> KGDB does some horrible things, and with everybody having access to
> virtualization these days, there is really no reason to use it over
> Qemu's gdb-server.

kgdb_panic() also adds a different code flow on the crash/kexec path,
which makes things more complex. See a recent discussion about this:

https://lore.kernel.org/all/auiO_x_Am8ZmZcmw@gmail.com/

> Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>

Acked-by: Breno Leitao <leitao@debian.org>

      parent reply	other threads:[~2026-11-02 13:33 UTC|newest]

Thread overview: 15+ 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
2026-10-28 19:58       ` Steve Wahl
2026-10-29  8:46         ` Peter Zijlstra
2026-10-29 10:34           ` David Laight
2026-10-30  2:00             ` Masami Hiramatsu (Google)
2026-10-30 16:27               ` David Laight
2026-10-29 10:51         ` David Laight
2026-10-29 15:32           ` Steve Wahl
2026-10-30 16:28             ` David Laight
2026-10-30 20:56               ` Steve Wahl
2026-10-30 22:31                 ` David Laight
2026-11-02 13:33 ` Breno Leitao [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=auiQKR6IhdyOCiex@gmail.com \
    --to=leitao@debian.org \
    --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=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®