All of lore.kernel.org
 help / color / mirror / Atom feed
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 0/2] x86: split out dumpstack code from traps_xx.c
Date: Tue, 30 Sep 2008 13:27:28 +0200	[thread overview]
Message-ID: <20080930112728.GD21367@elte.hu> (raw)
In-Reply-To: <1222773135-1073-1-git-send-email-heukelum@fastmail.fm>


* Alexander van Heukelum <heukelum@fastmail.fm> wrote:

> Hi Ingo,
> 
> I intend to keep looking for possibilities to bring traps_32.c and 
> traps_64.c closer to each-other. One trivial way (from my point of 
> view) is to split out code into separate files. These two patches 
> split out a large piece of code that has nothing to do with hardware 
> traps. Are you willing to take those two patches? Or are they to 
> intrusive?

they are not intrusive at all! The right way to do such things is to 
keep them in reasonably small files.

> Patches are against the current master branch of the tip tree. The 
> defconfigs compile fine and I ran some simple configs within qemu.

would be nice to bring dumpstack_32.c and dumpstack_64.c together as 
well. While some of the details like IST stack logic (which dont exist 
on 32-bit) are special, most of the glue, the iterators, the boot 
parameters, and even the output should be unified some more.

	Ingo

  parent reply	other threads:[~2008-09-30 11:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-30 11:12 [PATCH 0/2] x86: split out dumpstack code from traps_xx.c Alexander van Heukelum
2008-09-30 11:12 ` [PATCH 1/2] i386: split out dumpstack code from traps_32.c Alexander van Heukelum
2008-09-30 11:12   ` [PATCH 2/2] x86_64: split out dumpstack code from traps_64.c Alexander van Heukelum
2008-09-30 11:27 ` Ingo Molnar [this message]
2008-09-30 11:44 ` [PATCH 0/2] x86: split out dumpstack code from traps_xx.c Ingo Molnar

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=20080930112728.GD21367@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.