public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andy Lutomirski <luto@amacapital.net>
To: <hpa@zytor.com>, Kui Zhang <kuizhang@gmail.com>
Cc: x86@kernel.org,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Andy Lutomirski <luto@amacapital.net>
Subject: [PATCH v3 0/4] vDSO reference parser updates and Go workaround
Date: Thu, 12 Jun 2014 17:53:08 -0700	[thread overview]
Message-ID: <cover.1402620737.git.luto@amacapital.net> (raw)

Patches 1 and 2 update the vDSO reference parser.

Despite the late submission, this might be 3.16 material: it's just
documentation.  If I'd been more on top of this, I would have done it
for 3.15.  It's also probably worthwhile given that there is at least
one rather buggy vDSO parser in the wild.

Patches 3 and 4 make "Hello world" as built by Go stop segfaulting.
It's a performance regression for Go programs: it causes them to stop
finding any symbols in the vDSO, but that's a lot better than
segfaulting.

Changes from v1:
 - Improve portability of the vdso parser.
 - Add an explicit ELFCLASS check in the vdso parser (why not?).
 - Fix x32 build.
 - Add a comment describing what the hack works around, why, and where the
   Go bug was introduced.

Changes from v2: Re-add patch 1.  Whoops.

Andy Lutomirski (4):
  doc,vdso: Rename vdso_test.c to vdso_standalone_test_x86.c
  doc,vdso: Make vDSO examples more portable
  x86,vdso: Add PUT_LE to store little-endian values
  x86,vdso: Hack to keep 64-bit Go programs working

 Documentation/vDSO/parse_vdso.c               |  67 ++++++++------
 Documentation/vDSO/vdso_standalone_test_x86.c | 128 ++++++++++++++++++++++++++
 Documentation/vDSO/vdso_test.c                | 107 +++++----------------
 arch/x86/vdso/Makefile                        |  18 ++--
 arch/x86/vdso/vdso-fakesections.c             |  32 +++++++
 arch/x86/vdso/vdso2c.c                        |  19 +++-
 arch/x86/vdso/vdso2c.h                        |  23 ++++-
 7 files changed, 268 insertions(+), 126 deletions(-)
 create mode 100644 Documentation/vDSO/vdso_standalone_test_x86.c
 create mode 100644 arch/x86/vdso/vdso-fakesections.c

-- 
1.9.3


             reply	other threads:[~2014-06-13  0:53 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-13  0:53 Andy Lutomirski [this message]
2014-06-13  0:53 ` [PATCH v3 1/4] doc,vdso: Rename vdso_test.c to vdso_standalone_test_x86.c Andy Lutomirski
2014-06-13  2:27   ` [tip:x86/vdso] x86/vdso/doc: " tip-bot for Andy Lutomirski
2014-06-13  0:53 ` [PATCH v3 2/4] doc,vdso: Make vDSO examples more portable Andy Lutomirski
2014-06-13  2:27   ` [tip:x86/vdso] x86/vdso/doc: " tip-bot for Andy Lutomirski
2014-06-13  0:53 ` [PATCH v3 3/4] x86,vdso: Add PUT_LE to store little-endian values Andy Lutomirski
2014-06-13  2:28   ` [tip:x86/vdso] x86/vdso: " tip-bot for Andy Lutomirski
2014-06-13  0:53 ` [PATCH v3 4/4] x86,vdso: Hack to keep 64-bit Go programs working Andy Lutomirski
2014-06-13  1:49   ` H. Peter Anvin
2014-06-13  1:52     ` Andy Lutomirski
2014-06-13  1:54       ` H. Peter Anvin
2014-06-13  2:28   ` [tip:x86/vdso] x86/vdso: " 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=cover.1402620737.git.luto@amacapital.net \
    --to=luto@amacapital.net \
    --cc=hpa@zytor.com \
    --cc=kuizhang@gmail.com \
    --cc=linux-kernel@vger.kernel.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