All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sander Eikelenboom <linux@eikelenboom.it>
To: Andy Lutomirski <luto@MIT.EDU>
Cc: x86@kernel.org, Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
	<jeremy@goop.org>, <xen-devel@lists.xensource.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	<virtualization@lists.linux-foundation.org>, <keir.xen@gmail.com>
Subject: Re: [Xen-devel] [PATCH v2 0/6] Collected vdso/vsyscall fixes for 3.1
Date: Wed, 3 Aug 2011 19:34:25 +0200	[thread overview]
Message-ID: <284611976.20110803193425@eikelenboom.it> (raw)
In-Reply-To: <cover.1312378163.git.luto@mit.edu>

Hello Andy,

Wednesday, August 3, 2011, 3:31:48 PM, you wrote:

> This fixes various problems that cropped up with the vdso patches.

>  - Patch 1 fixes an information leak to userspace.
>  - Patches 2 and 3 fix the kernel build on gold.
>  - Patches 4 and 5 fix Xen (I hope).
>  - Patch 6 (optional) adds a trace event to vsyscall emulation.  It will
>    make it easier to handle performance regression reports :)

> [1] https://gitorious.org/linux-test-utils/linux-clock-tests

> Changes from v1:
>  - Improve changelog message for "x86-64/xen: Enable the vvar mapping"
>  - Fix 32-bit build.
>  - Add patch 6.

> Andy Lutomirski (6):
>   x86-64: Pad vDSO to a page boundary
>   x86-64: Move the "user" vsyscall segment out of the data segment.
>   x86-64: Work around gold bug 13023
>   x86-64/xen: Enable the vvar mapping
>   x86-64: Add user_64bit_mode paravirt op
>   x86-64: Add vsyscall:emulate_vsyscall trace event

>  arch/x86/include/asm/desc.h           |    4 +-
>  arch/x86/include/asm/paravirt_types.h |    6 ++++
>  arch/x86/include/asm/ptrace.h         |   19 +++++++++++++
>  arch/x86/kernel/paravirt.c            |    4 +++
>  arch/x86/kernel/step.c                |    2 +-
>  arch/x86/kernel/vmlinux.lds.S         |   46 ++++++++++++++++++---------------
>  arch/x86/kernel/vsyscall_64.c         |   12 +++++---
>  arch/x86/kernel/vsyscall_trace.h      |   29 ++++++++++++++++++++
>  arch/x86/mm/fault.c                   |    2 +-
>  arch/x86/vdso/vdso.S                  |    1 +
>  arch/x86/xen/enlighten.c              |    4 +++
>  arch/x86/xen/mmu.c                    |    4 ++-
>  12 files changed, 102 insertions(+), 31 deletions(-)
>  create mode 100644 arch/x86/kernel/vsyscall_trace.h

Compile and boot tested on Xen 4.1.1 and baremetal on x86_64, it fixes my boot panic under Xen.

Tested-by: Sander Eikelenboom <linux@eikelenboom.it>


WARNING: multiple messages have this Message-ID (diff)
From: Sander Eikelenboom <linux@eikelenboom.it>
To: Andy Lutomirski <luto@MIT.EDU>
Cc: x86@kernel.org, Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
	jeremy@goop.org, xen-devel@lists.xensource.com,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	virtualization@lists.linux-foundation.org, keir.xen@gmail.com
Subject: Re: [Xen-devel] [PATCH v2 0/6] Collected vdso/vsyscall fixes for 3.1
Date: Wed, 3 Aug 2011 19:34:25 +0200	[thread overview]
Message-ID: <284611976.20110803193425@eikelenboom.it> (raw)
In-Reply-To: <cover.1312378163.git.luto@mit.edu>

Hello Andy,

Wednesday, August 3, 2011, 3:31:48 PM, you wrote:

> This fixes various problems that cropped up with the vdso patches.

>  - Patch 1 fixes an information leak to userspace.
>  - Patches 2 and 3 fix the kernel build on gold.
>  - Patches 4 and 5 fix Xen (I hope).
>  - Patch 6 (optional) adds a trace event to vsyscall emulation.  It will
>    make it easier to handle performance regression reports :)

> [1] https://gitorious.org/linux-test-utils/linux-clock-tests

> Changes from v1:
>  - Improve changelog message for "x86-64/xen: Enable the vvar mapping"
>  - Fix 32-bit build.
>  - Add patch 6.

> Andy Lutomirski (6):
>   x86-64: Pad vDSO to a page boundary
>   x86-64: Move the "user" vsyscall segment out of the data segment.
>   x86-64: Work around gold bug 13023
>   x86-64/xen: Enable the vvar mapping
>   x86-64: Add user_64bit_mode paravirt op
>   x86-64: Add vsyscall:emulate_vsyscall trace event

>  arch/x86/include/asm/desc.h           |    4 +-
>  arch/x86/include/asm/paravirt_types.h |    6 ++++
>  arch/x86/include/asm/ptrace.h         |   19 +++++++++++++
>  arch/x86/kernel/paravirt.c            |    4 +++
>  arch/x86/kernel/step.c                |    2 +-
>  arch/x86/kernel/vmlinux.lds.S         |   46 ++++++++++++++++++---------------
>  arch/x86/kernel/vsyscall_64.c         |   12 +++++---
>  arch/x86/kernel/vsyscall_trace.h      |   29 ++++++++++++++++++++
>  arch/x86/mm/fault.c                   |    2 +-
>  arch/x86/vdso/vdso.S                  |    1 +
>  arch/x86/xen/enlighten.c              |    4 +++
>  arch/x86/xen/mmu.c                    |    4 ++-
>  12 files changed, 102 insertions(+), 31 deletions(-)
>  create mode 100644 arch/x86/kernel/vsyscall_trace.h

Compile and boot tested on Xen 4.1.1 and baremetal on x86_64, it fixes my boot panic under Xen.

Tested-by: Sander Eikelenboom <linux@eikelenboom.it>

  parent reply	other threads:[~2011-08-03 17:34 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-03 13:31 [PATCH v2 0/6] Collected vdso/vsyscall fixes for 3.1 Andy Lutomirski
2011-08-03 13:31 ` Andy Lutomirski
2011-08-03 13:31 ` [PATCH v2 1/6] x86-64: Pad vDSO to a page boundary Andy Lutomirski
2011-08-03 13:31 ` Andy Lutomirski
2011-08-05  5:37   ` [tip:x86/vdso] " tip-bot for Andy Lutomirski
2011-08-03 13:31 ` [PATCH v2 1/6] " Andy Lutomirski
2011-08-03 13:31 ` [PATCH v2 2/6] x86-64: Move the "user" vsyscall segment out of the data segment Andy Lutomirski
2011-08-03 13:31 ` Andy Lutomirski
2011-08-03 13:31   ` Andy Lutomirski
2011-08-05  5:37   ` [tip:x86/vdso] " tip-bot for Andy Lutomirski
2011-08-03 13:31 ` [PATCH v2 3/6] x86-64: Work around gold bug 13023 Andy Lutomirski
2011-08-03 13:31 ` Andy Lutomirski
2011-08-05  5:38   ` [tip:x86/vdso] " tip-bot for Andy Lutomirski
2011-08-03 13:31 ` [PATCH v2 4/6] x86-64/xen: Enable the vvar mapping Andy Lutomirski
2011-08-03 13:31 ` Andy Lutomirski
2011-08-03 13:49   ` Konrad Rzeszutek Wilk
2011-08-03 13:49   ` Konrad Rzeszutek Wilk
2011-08-03 13:49     ` Konrad Rzeszutek Wilk
2011-08-05  5:38   ` [tip:x86/vdso] x86-64, xen: " tip-bot for Andy Lutomirski
2011-08-03 13:31 ` [PATCH v2 5/6] x86-64: Add user_64bit_mode paravirt op Andy Lutomirski
2011-08-05  5:39   ` [tip:x86/vdso] " tip-bot for Andy Lutomirski
2011-08-03 13:31 ` [PATCH v2 5/6] " Andy Lutomirski
2011-08-03 13:31 ` [PATCH v2 6/6] x86-64: Add vsyscall:emulate_vsyscall trace event Andy Lutomirski
2011-08-05  5:39   ` [tip:x86/vdso] " tip-bot for Andy Lutomirski
2011-08-03 13:31 ` [PATCH v2 6/6] " Andy Lutomirski
2011-08-03 13:53 ` [PATCH v2 0/6] Collected vdso/vsyscall fixes for 3.1 Konrad Rzeszutek Wilk
2011-08-03 13:53 ` Konrad Rzeszutek Wilk
2011-08-03 13:53   ` Konrad Rzeszutek Wilk
2011-08-03 13:56   ` Konrad Rzeszutek Wilk
2011-08-03 13:56     ` Konrad Rzeszutek Wilk
2011-08-03 13:59     ` Andrew Lutomirski
2011-08-03 13:59     ` Andrew Lutomirski
2011-08-11 20:28       ` Jeremy Fitzhardinge
2011-08-11 20:47         ` Andrew Lutomirski
2011-08-11 20:47         ` Andrew Lutomirski
2011-08-11 20:28       ` Jeremy Fitzhardinge
2011-08-03 13:56   ` Konrad Rzeszutek Wilk
2011-08-03 17:34 ` [Xen-devel] " Sander Eikelenboom
2011-08-03 17:34 ` Sander Eikelenboom [this message]
2011-08-03 17:34   ` Sander Eikelenboom

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=284611976.20110803193425@eikelenboom.it \
    --to=linux@eikelenboom.it \
    --cc=jeremy@goop.org \
    --cc=keir.xen@gmail.com \
    --cc=konrad.wilk@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@MIT.EDU \
    --cc=virtualization@lists.linux-foundation.org \
    --cc=x86@kernel.org \
    --cc=xen-devel@lists.xensource.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.