From: Ingo Molnar <mingo@elte.hu>
To: Dmitri Vorobiev <dmitri.vorobiev@gmail.com>
Cc: tglx@linutronix.de, hpa@zytor.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/4] x86: random clean-ups
Date: Tue, 22 Apr 2008 21:22:15 +0200 [thread overview]
Message-ID: <20080422192215.GA11665@elte.hu> (raw)
In-Reply-To: <480E3A00.7060401@gmail.com>
* Dmitri Vorobiev <dmitri.vorobiev@gmail.com> wrote:
> >> This should be #1, #3 and #4. The NexGen patch, which was #2 in the
> >> original series, have been replaced by a bigger patch that kills
> >> NexGen altogether. Plese check, if you have time for that.
> >
> > yeah, i did the right thing and described the wrong selection :) You
> > can check the end result via:
> >
> > http://people.redhat.com/mingo/x86.git/README
>
> ... which indicates that #4 is still not there, which is a pity, since
> the #4 patch gave me a more-than-negligible binary shrinkage for the
> case CONFIG_SYSFS=n :)
oh, yes, i forgot - that collided with some changes to that file -
percpu changes and 4Kcpu support. I think we should delay #4 to a bit
later, when the other changes have gone in - or you could try to send a
patch against sched-devel.git/latest which should show the merged up
status of that code:
http://people.redhat.com/mingo/sched-devel.git/README
sched-devel/latest has all of the x86 tree 'embedded' in it - plus the
4Kcpu changes as well.
Ingo
next prev parent reply other threads:[~2008-04-22 19:22 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-20 2:54 [PATCH 0/4] x86: random clean-ups Dmitri Vorobiev
2008-04-20 2:54 ` [PATCH 1/4] x86: remove unused function amd_init_cpu() Dmitri Vorobiev
2008-04-20 2:54 ` [PATCH 2/4] x86: remove unused code and data in nexgen.c Dmitri Vorobiev
2008-04-20 4:22 ` H. Peter Anvin
2008-04-20 10:33 ` [PATCH 2/2 v2] x86: remove unused function, register the cpu vendor " Dmitri Vorobiev
2008-04-20 18:51 ` [PATCH 2/4] x86: remove unused code and data " Andi Kleen
2008-04-20 19:24 ` Dmitri Vorobiev
2008-04-20 19:34 ` H. Peter Anvin
2008-04-20 19:45 ` Dmitri Vorobiev
2008-04-20 19:47 ` H. Peter Anvin
2008-04-20 20:03 ` Andi Kleen
2008-04-20 20:26 ` H. Peter Anvin
2008-04-23 18:19 ` Alan Cox
2008-04-23 19:02 ` Dmitri Vorobiev
2008-04-20 2:54 ` [PATCH 3/4] x86_64: the standard_io_resources[] array can become static Dmitri Vorobiev
2008-04-20 2:54 ` [PATCH 4/4] x86: conditionally compile sysfs stuff in intel_cacheinfo.c Dmitri Vorobiev
2008-04-21 12:25 ` [PATCH 0/4] x86: random clean-ups Ingo Molnar
[not found] ` <90edad820804210541h26c8e66dh70895f32e4b4038d@mail.gmail.com>
2008-04-22 14:02 ` Ingo Molnar
2008-04-22 19:18 ` Dmitri Vorobiev
2008-04-22 19:22 ` Ingo Molnar [this message]
2008-04-22 19:37 ` Dmitri Vorobiev
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=20080422192215.GA11665@elte.hu \
--to=mingo@elte.hu \
--cc=dmitri.vorobiev@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox