From: "H. Peter Anvin" <hpa@zytor.com>
To: Andy Lutomirski <luto@amacapital.net>,
Stefani Seibold <stefani@seibold.net>
Cc: Greg KH <gregkh@linuxfoundation.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
X86 ML <x86@kernel.org>, Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Andi Kleen <ak@linux.intel.com>,
Andrea Arcangeli <aarcange@redhat.com>,
John Stultz <john.stultz@linaro.org>,
Pavel Emelyanov <xemul@parallels.com>,
Cyrill Gorcunov <gorcunov@openvz.org>,
andriy.shevchenko@linux.intel.com,
Martin.Runge@rohde-schwarz.com, Andreas.Brief@rohde-schwarz.com
Subject: Re: [PATCH 3/4] Add 32 bit VDSO time support for 32 bit kernel
Date: Sat, 01 Feb 2014 16:26:11 -0800 [thread overview]
Message-ID: <52ED90A3.9080802@zytor.com> (raw)
In-Reply-To: <CALCETrVp+aTm_mT4bg6kcaX3QOnqyjVdfM9vdhHZPsKG276X0A@mail.gmail.com>
On 02/01/2014 03:59 PM, Andy Lutomirski wrote:
>
> If it is, indeed, okay to use non-fixed maps on 32-bit, it might
> also be okay on 64-bit. If so, it could be useful to implement that,
> which would remove a bit of a wart and allow PR_SET_TSC to work
> usefully for 64-bit userspace. (This would remove the need for the
> VVAR macro and would allow shorter rip-relative address modes.)
>
We can't really move the 64-bit legacy vsyscall area, though, as it is
an ABI. It can be disabled with vsyscall=none, but Linus has vehemently
vetoed removing them.
> (Note that those fixmaps are a security problem on native 32-bit if
> NX is not available. We may not care.)
Not only on native 32 bit... although the amount of 64-bit hardware
without NX is quite small, the same is true for anywhere near modern
32-bit hardware.
>>
>> -#define VDSO_HIGH_BASE 0xffffe000U /* CONFIG_COMPAT_VDSO address */
>> +#define VDSO_HIGH_BASE 0xffffc000U /* CONFIG_COMPAT_VDSO address */
>
> This is odd. Can you explain it?
>
He needs 3 pages instead of 1 after his changes.
-hpa
next prev parent reply other threads:[~2014-02-02 0:27 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-01 15:32 [PATCH 0/4] Add 32 bit VDSO time function support stefani
2014-02-01 15:32 ` [PATCH 1/4] Make vsyscall_gtod_data handling x86 generic stefani
2014-02-01 23:40 ` Andy Lutomirski
2014-02-01 15:32 ` [PATCH 2/4] Add new func _install_special_mapping() to mmap.c stefani
2014-02-01 15:32 ` [PATCH 3/4] Add 32 bit VDSO time support for 32 bit kernel stefani
2014-02-01 23:59 ` Andy Lutomirski
2014-02-02 0:26 ` H. Peter Anvin [this message]
2014-02-02 0:30 ` Andy Lutomirski
2014-02-02 0:41 ` H. Peter Anvin
2014-02-02 0:56 ` H. Peter Anvin
2014-02-03 21:11 ` Roland McGrath
2014-02-02 11:20 ` Stefani Seibold
2014-02-02 15:25 ` H. Peter Anvin
2014-02-01 15:32 ` [PATCH 4/4] Add 32 bit VDSO time support for 64 " stefani
2014-02-01 20:29 ` 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=52ED90A3.9080802@zytor.com \
--to=hpa@zytor.com \
--cc=Andreas.Brief@rohde-schwarz.com \
--cc=Martin.Runge@rohde-schwarz.com \
--cc=aarcange@redhat.com \
--cc=ak@linux.intel.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=gorcunov@openvz.org \
--cc=gregkh@linuxfoundation.org \
--cc=john.stultz@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=mingo@redhat.com \
--cc=stefani@seibold.net \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=xemul@parallels.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