From: Petr Tesarik <ptesarik@suse.cz>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Andi Kleen <andi@firstfloor.org>,
LKML <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>
Subject: Re: [PATCH] x86: clean up vdso-layout.lds.S
Date: Tue, 09 Jun 2009 09:32:12 +0200 [thread overview]
Message-ID: <1244532732.5199.29.camel@nathan.suse.cz> (raw)
In-Reply-To: <4A2946B9.3070701@zytor.com>
H. Peter Anvin píše v Pá 05. 06. 2009 v 09:24 -0700:
> Andi Kleen wrote:
> >> Any comments on this? It doesn't change anything. It only makes it
> >> harder to break vDSOs by accident (such as the latest buglet with TSC
> >> synchronization).
> >
> > Looks ok to me. Although it would have been nicer if you hadn't mixed
> > that many changes together.
> >
> > Acked-by: Andi Kleen <ak@linux.intel.com>
> >
>
> It would have. That makes review harder, and right at the moment time
> is a bit at a premium. It looks like a good cleanup, but it also looks
> like it's going to need some testing, which means that since it is not a
> functional change I would feel best if we could put it on the .32 track
> after the imminent merge window craziness is over.
You're right. It doesn't make any functional change, so I'm completely
fine with taking it on the .32 track.
For the time being, please hold on, as I'm going to split the patch into
a series to make reviewing easier. But to be honest, the current content
of vdso-layout.lds.S is such mess that I'm convinced it must have been
done in a big hurry (and then moved around a few times, so a quick
glance at git-blame doesn't tell you that the most messy pieces have
been there since the very beginning).
Petr Tesarik
next prev parent reply other threads:[~2009-06-09 7:32 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-01 14:05 [PATCH] x86: clean up vdso-layout.lds.S Petr Tesarik
2009-06-05 15:25 ` Petr Tesarik
2009-06-05 16:27 ` Andi Kleen
2009-06-05 16:24 ` H. Peter Anvin
2009-06-09 7:32 ` Petr Tesarik [this message]
2009-06-05 20:07 ` Sam Ravnborg
2009-06-09 7:26 ` Petr Tesarik
2009-06-09 7:52 ` Roland McGrath
2009-06-09 7:57 ` Petr Tesarik
2009-06-09 8:09 ` Roland McGrath
2009-06-09 8:29 ` Petr Tesarik
2009-06-09 15:41 ` H. Peter Anvin
2009-06-09 18:11 ` Sam Ravnborg
2009-06-09 18:16 ` H. Peter Anvin
2009-06-09 19:22 ` Sam Ravnborg
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=1244532732.5199.29.camel@nathan.suse.cz \
--to=ptesarik@suse.cz \
--cc=andi@firstfloor.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--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