From: Ingo Molnar <mingo@elte.hu>
To: Mike Travis <travis@sgi.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] x86: cleanup early per cpu variables/accesses v2
Date: Wed, 16 Apr 2008 11:35:05 +0200 [thread overview]
Message-ID: <20080416093505.GG5343@elte.hu> (raw)
In-Reply-To: <20080415233551.964024000@polaris-admin.engr.sgi.com>
* Mike Travis <travis@sgi.com> wrote:
> * Introduce a new PER_CPU macro called "EARLY_PER_CPU". This is
> used by some per_cpu variables that are initialized and accessed
> before there are per_cpu areas allocated.
>
> * Small change in kernel/sched.c to remove another 512 bytes from
> the stack.
thanks Mike, i have picked your patches up.
Ingo
prev parent reply other threads:[~2008-04-16 9:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-15 23:35 [PATCH 0/2] x86: cleanup early per cpu variables/accesses v2 Mike Travis
2008-04-15 23:35 ` [PATCH 1/2] sched: remove another cpumask_t variable from stack Mike Travis
2008-04-15 23:35 ` [PATCH 2/2] x86: cleanup early per cpu variables/accesses v2 Mike Travis
2008-04-16 9:35 ` Ingo Molnar [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=20080416093505.GG5343@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@linux-foundation.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=travis@sgi.com \
/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