From: Andi Kleen <ak@suse.de>
To: Tom Rini <trini@kernel.crashing.org>
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH][6/6] A different KGDB stub
Date: 12 Feb 2004 07:43:04 +0100 [thread overview]
Message-ID: <p73wu6syf0n.fsf@verdi.suse.de> (raw)
In-Reply-To: <20040212000408.GG19676@smtp.west.cox.net.suse.lists.linux.kernel>
Tom Rini <trini@kernel.crashing.org> writes:
Andrew, please don't add this broken version.
> @@ -219,7 +219,7 @@
> jnc sysret_signal
> sti
> pushq %rdi
> - call schedule
> + call user_schedule
I really don't like this change. It is completely useless because you
can get the pt_regs as well from the stack. Please don't add it.
George's stub also didn't need it.
> +#ifdef CONFIG_KGDB_THREAD
> +ENTRY(kern_schedule)
Similar. No such crap please.
> @@ -317,13 +318,26 @@
> return;
>
> sum = read_pda(apic_timer_irqs);
> - if (last_irq_sums[cpu] == sum) {
> + if (atomic_read(&debugger_active)) {
> +
> + /*
> + * The machine is in debugger, hold this cpu if already
> + * not held.
> + */
> + debugger_nmihook(cpu, regs);
> + alert_counter[cpu] = 0;
This should be a notify_die.
> + } else if (last_irq_sums[cpu] == sum) {
> +
> /*
> * Ayiee, looks like this CPU is stuck ...
> * wait a few IRQs (5 seconds) before doing the oops ...
> */
> alert_counter[cpu]++;
> if (alert_counter[cpu] == 5*nmi_hz) {
> +
> + CHK_DEBUGGER(2,SIGSEGV,0,regs,)
> +
> if (notify_die(DIE_NMI, "nmi", regs, reason, 2, SIGINT) == NOTIFY_BAD) {
That's complete crap. You have a debugger hook and you add your own
hook one line before it. Please fix that.
I note that the old stub in -mm* didn't need such wards.
>
> void die(const char * str, struct pt_regs * regs, long err)
> {
> + CHK_DEBUGGER(1,SIGTRAP,err,regs,)
Same issue here. All the CHK_DEBUGGER are redundant with notify_die.
> --- a/include/asm-x86_64/processor.h Wed Feb 11 15:42:06 2004
> +++ b/include/asm-x86_64/processor.h Wed Feb 11 15:42:06 2004
> @@ -252,6 +252,7 @@
> unsigned long *io_bitmap_ptr;
> /* cached TLS descriptors. */
> u64 tls_array[GDT_ENTRY_TLS_ENTRIES];
> + void *debuggerinfo;
> };
This should not be needed
> #define INIT_THREAD {}
> --- a/include/asm-x86_64/system.h Wed Feb 11 15:42:06 2004
> +++ b/include/asm-x86_64/system.h Wed Feb 11 15:42:06 2004
> @@ -19,6 +19,56 @@
> #define __SAVE(reg,offset) "movq %%" #reg ",(14-" #offset ")*8(%%rsp)\n\t"
> #define __RESTORE(reg,offset) "movq (14-" #offset ")*8(%%rsp),%%" #reg "\n\t"
>
> +/* #ifdef CONFIG_KGDB */
> +
> +/* full frame for the debug stub */
> +/* Should be replaced with a dwarf2 cie/fde description, then gdb could
> + figure it out all by itself. */
> +struct save_context_frame {
That's completely broken too. We have a full CFI description in the kernel
now, so this isn't needed anymore.
-Andi
next parent reply other threads:[~2004-02-12 6:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20040212000408.GG19676@smtp.west.cox.net.suse.lists.linux.kernel>
2004-02-12 6:43 ` Andi Kleen [this message]
2004-02-12 15:50 ` Tom Rini
2004-02-13 3:00 ` Andi Kleen
2004-02-12 16:27 ` Tom Rini
2004-02-16 19:47 ` Pavel Machek
2004-02-12 18:32 ` Tom Rini
2004-02-17 22:04 Tom Rini
[not found] ` <20040217223040.GA1560@elf.ucw.cz>
[not found] ` <20040217223817.GJ16881@smtp.west.cox.net>
2004-02-17 23:08 ` Pavel Machek
2004-02-17 23:13 ` Tom Rini
-- strict thread matches above, loose matches on Subject: below --
2004-02-12 0:04 Tom Rini
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=p73wu6syf0n.fsf@verdi.suse.de \
--to=ak@suse.de \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=trini@kernel.crashing.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®