From: "H. Peter Anvin" <hpa@zytor.com>
To: Andy Lutomirski <luto@amacapital.net>, x86@kernel.org
Cc: Stefani Seibold <stefani@seibold.net>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/6] Clean up and unify the vDSO
Date: Thu, 24 Apr 2014 21:21:28 -0700 [thread overview]
Message-ID: <5359E2C8.7030809@zytor.com> (raw)
In-Reply-To: <cover.1398377016.git.luto@amacapital.net>
On 04/24/2014 03:08 PM, Andy Lutomirski wrote:
> This rewrites a bunch of the vdso code. After these patches, the vvar
> and hpet pages are mapped directly after the vdso text on all five vdso
> variants. The fixmaps are gone on 64-bit systems.
>
> It would be possible to build the x32 vdso the normal way on top of
> these patches.
>
> I haven't touched the pvclock code. I'd want to understand why it
> exists, why it isn't using rdtsc, and why it has two rdtsc_barrier calls
> before rearranging it. In a discussion with Marcello Tosatti, I think
> we concluded that the kvmclock code could be significantly simplified
> and sped up without breaking anything, but I want to save that for
> later.
>
> This should apply to -linus or to tip/x86/vdso. It's also here:
>
> https://git.kernel.org/cgit/linux/kernel/git/luto/linux.git/log/?h=vdso/cleanups
>
> and it has survived the build bot for a day.
>
This doesn't apply cleanly on top of v3.15-rc2. Could I ask you do
rebase it again?
-hpa
next prev parent reply other threads:[~2014-04-25 4:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-24 22:08 [PATCH v2 0/6] Clean up and unify the vDSO Andy Lutomirski
2014-04-24 22:09 ` [PATCH v2 1/6] x86: Clean up 32-bit vs 64-bit vdso params Andy Lutomirski
2014-04-24 22:09 ` [PATCH v2 2/6] x86: Move syscall and sysenter setup into kernel/cpu/common.c Andy Lutomirski
2014-04-24 22:09 ` [PATCH v2 3/6] x86: Reimplement vdso.so preparation in build-time C Andy Lutomirski
2014-04-24 22:09 ` [PATCH v2 4/6] x86: Move the 32-bit vdso special pages after the text Andy Lutomirski
2014-04-24 22:09 ` [PATCH v2 5/6] x86: Move the vvar and hpet mappings next to the 64-bit vDSO Andy Lutomirski
2014-04-24 22:09 ` [PATCH v2 6/6] x86: Remove vestiges of VDSO_PRELINK and some outdated comments Andy Lutomirski
2014-04-25 4:21 ` H. Peter Anvin [this message]
2014-04-25 4:22 ` [PATCH v2 0/6] Clean up and unify the vDSO H. Peter Anvin
2014-05-02 18:59 ` H. Peter Anvin
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=5359E2C8.7030809@zytor.com \
--to=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=stefani@seibold.net \
--cc=x86@kernel.org \
/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