mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Andrew Lutomirski <luto@mit.edu>
Cc: x86@kernel.org, Andi Kleen <andi@firstfloor.org>,
	linux-kernel@vger.kernel.org, torvalds@linux-foundation.org,
	lueckintel@yahoo.com, kimwooyoung@gmail.com,
	Ingo Molnar <mingo@elte.hu>, Borislav Petkov <bp@alien8.de>
Subject: Re: [PATCH 3/3] x86-64: Rework vsyscall emulation and add vsyscall= parameter
Date: Wed, 10 Aug 2011 17:20:58 -0500	[thread overview]
Message-ID: <4b8d6929-6163-4e25-933c-c875a1857f3a@email.android.com> (raw)
In-Reply-To: <CAObL_7HO_6krk86GQuqt3o4aqjkp3CMbQ1s2P9L5bU0R0m8Hpg@mail.gmail.com>

Andrew Lutomirski <luto@mit.edu> wrote:

>On Wed, Aug 10, 2011 at 5:14 PM, H. Peter Anvin <hpa@zytor.com> wrote:
>> Andrew Lutomirski <luto@mit.edu> wrote:
>>
>>>On Wed, Aug 10, 2011 at 1:21 PM, H. Peter Anvin <hpa@zytor.com>
>wrote:
>>>> On 08/10/2011 10:15 AM, Andy Lutomirski wrote:
>>>>> There are three choices:
>>>>>
>>>>> vsyscall=native: Vsyscalls are native code that issues the
>>>>> corresponding syscalls.
>>>>>
>>>>> vsyscall=emulate (default): Vsyscalls are emulated by instruction
>>>>> fault traps, tested in the bad_area path.  The actual contents of
>>>>> the vsyscall page is the same as the vsyscall=native case except
>>>>> that it's marked NX.  This way programs that make assumptions
>about
>>>>> what the code in the page does will not be confused when they read
>>>>> that code.
>>>>>
>>>>> vsyscall=none: Trying to execute a vsyscall will segfault.
>>>>>
>>>>> Signed-off-by: Andy Lutomirski <luto@mit.edu>
>>>>
>>>> Hi Andy,
>>>>
>>>> This patch doesn't apply.  What is your baseline for this patch?
>>>
>>>My baseline was a commit that probably only lives in my tree, but the
>>>patches should apply cleanly on top of
>>>c149a665ac488e0dac22a42287f45ad1bda06ff1, which is the current
>>>tip/x86/vdso.
>>>
>>>--Andy
>>
>> Please rebase your patch on the current -linus since it appears to
>have changed since x86/vdso was merged.
>>
>
>Can you double-check?  I think it's the other way around: x86/vdso has
>fixes that should be pushed to Linus.
>
>$ git log tip/x86/vdso ^origin/master --oneline
>c149a66 x86-64: Add vsyscall:emulate_vsyscall trace event
>318f5a2 x86-64: Add user_64bit_mode paravirt op
>5d5791a x86-64, xen: Enable the vvar mapping
>f670bb7 x86-64: Work around gold bug 13023
>9c40818 x86-64: Move the "user" vsyscall segment out of the data
>segment.
>1bdfac1 x86-64: Pad vDSO to a page boundary
>17b0436 Merge commit 'v3.0' into x86/vdso
>
>--Andy

You're right, although coupling it makes the testing harder.
-- 
Sent from my mobile phone. Please excuse my brevity and lack of formatting.

  reply	other threads:[~2011-08-10 22:22 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-10 15:15 [PATCH 0/3] vsyscall emulation compatibility fixes Andy Lutomirski
2011-08-10 15:15 ` [PATCH 1/3] x86: Remove unnecessary compile flag tweaks for vsyscall code Andy Lutomirski
2011-08-11  0:01   ` [tip:x86/vdso] " tip-bot for Andy Lutomirski
2011-08-10 15:15 ` [PATCH 2/3] x86-64: Wire up getcpu syscall Andy Lutomirski
2011-08-11  0:01   ` [tip:x86/vdso] " tip-bot for Andy Lutomirski
2011-08-11  0:31   ` tip-bot for Andy Lutomirski
2011-08-10 15:15 ` [PATCH 3/3] x86-64: Rework vsyscall emulation and add vsyscall= parameter Andy Lutomirski
2011-08-10 17:21   ` H. Peter Anvin
2011-08-10 17:47     ` Andrew Lutomirski
2011-08-10 21:14       ` H. Peter Anvin
2011-08-10 21:18         ` Andrew Lutomirski
2011-08-10 22:20           ` H. Peter Anvin [this message]
2011-08-10 22:56             ` Andrew Lutomirski
2011-08-11  0:02   ` [tip:x86/vdso] " tip-bot for Andy Lutomirski
2011-08-11  0:31   ` tip-bot for Andy Lutomirski

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=4b8d6929-6163-4e25-933c-c875a1857f3a@email.android.com \
    --to=hpa@zytor.com \
    --cc=andi@firstfloor.org \
    --cc=bp@alien8.de \
    --cc=kimwooyoung@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lueckintel@yahoo.com \
    --cc=luto@mit.edu \
    --cc=mingo@elte.hu \
    --cc=torvalds@linux-foundation.org \
    --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

all inboxes | Powered by JetHome®