From: Ingo Molnar <mingo@elte.hu>
To: Alexander van Heukelum <heukelum@fastmail.fm>
Cc: LKML <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>
Subject: Re: [PATCH] dumpstack: x86: various small unification steps
Date: Sun, 5 Oct 2008 11:35:23 +0200 [thread overview]
Message-ID: <20081005093523.GE16819@elte.hu> (raw)
In-Reply-To: <1223154766-19350-1-git-send-email-heukelum@fastmail.fm>
* Alexander van Heukelum <heukelum@fastmail.fm> wrote:
> Hi Ingo,
>
> Here is the first round of unification of dumpstack_32.c
> and dumpstack_64.c. The first patch can also be seen as
> a clean-up of the traps.c-unification as I forgot to move
> one function at the time. Anyhow, the series depends on
> the traps unification.
great - i've created tip/x86/dumpstack for this and applied your patches
there. (that branch embedds tip/x86/core which already embedds
tip/x86/traps)
> B.T.W., I could reproduce the spontaneous reboot with the
> traps unification with glibc. The change GATE_INTERRUPT ->
> GATE_TRAP fixed the crash there. Usually I test only with
> a small klibc-based userspace, and there the reboot does
> not happen. I guess the int 0x80 interface is less picky.
> (Just to say that I do test the changes a bit ;) )
it also passed -tip testing still then so the changes are fine.
Generally if you see your commits show up and stay in tip/master it
means they get tested with a newly built random kernel about once every
two minutes or so.
regarding klibc, that's interesting: is that the in-kernel klibc from
hpa? Which tree are you using to pull that into tip/master? (unless i
misunderstood what you are doing)
Ingo
next prev parent reply other threads:[~2008-10-05 9:35 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-04 21:12 [PATCH] dumpstack: x86: various small unification steps Alexander van Heukelum
2008-10-04 21:12 ` [PATCH] dumpstack: x86: move die_nmi to dumpstack_32.c Alexander van Heukelum
2008-10-04 21:12 ` [PATCH] dumpstack: x86: make printk_address equal Alexander van Heukelum
2008-10-04 21:12 ` [PATCH] dumpstack: x86: add "end" parameter to valid_stack_ptr and print_context_stack Alexander van Heukelum
2008-10-04 21:12 ` [PATCH] dumptrace: x86: consistently include loglevel, print stack switch Alexander van Heukelum
2008-10-04 21:12 ` [PATCH] dumpstack: x86: use log_lvl and unify trace formatting Alexander van Heukelum
2008-10-04 21:12 ` [PATCH] dumpstack: i386: make kstack= an early boot-param and add oops=panic Alexander van Heukelum
2008-10-04 21:12 ` [PATCH] dumpstack: x86: various small unification steps Alexander van Heukelum
2008-10-06 9:35 ` Louis Rilling
2008-10-06 9:43 ` Alexander van Heukelum
2008-10-05 9:35 ` Ingo Molnar [this message]
2008-10-05 9:46 ` Ingo Molnar
2008-10-05 10:39 ` Alexander van Heukelum
2008-10-05 16:38 ` Ingo Molnar
2008-10-05 11:40 ` Alexander van Heukelum
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=20081005093523.GE16819@elte.hu \
--to=mingo@elte.hu \
--cc=heukelum@fastmail.fm \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
/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.