All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nathan_Lynch@mentor.com (Nathan Lynch)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4] ARM: vDSO gettimeofday using generic timer architecture
Date: Tue, 18 Mar 2014 12:17:39 -0500	[thread overview]
Message-ID: <53287FB3.1050103@mentor.com> (raw)
In-Reply-To: <CAASgrz0SaoNGb+ss6ZS+Zh_NoBzmznaneRur7xzp4_dyGb-wMg@mail.gmail.com>

Hi David,

On 03/17/2014 07:49 PM, David Riley wrote:
> Hi Nathan,
> 
> I gave this a try against a 3.10 system and ran into issues when
> vdso.so grew to two pages because of of a large .GCC.command.line
> section.  __get_datapage was returning an address that was at the
> beginning of the second code page instead of the data page since it
> didn't account for the additional section.  I got it working by adding
> .GCC.command.line to the DISCARD group in the linker script, but in
> general it feels as if this code is a bit fragile since it depends on
> knowing exactly which sections exist in the .so for the _vdso_data
> symbol to be correct.

Thanks for giving this a try and reporting the issue.  I'm guessing you
use -frecord-gcc-switches.  I agree this aspect of the vDSO could be
more robust -- at least the build should be made to fail when wrong code
is generated.

I'll look into it, and I'd appreciate any suggestions or additional
review, especially of the linker script.

  reply	other threads:[~2014-03-18 17:17 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-13 18:19 [PATCH v4] ARM: vDSO gettimeofday using generic timer architecture Nathan Lynch
2014-03-14  9:42 ` Steve Capper
2014-03-18  0:49 ` David Riley
2014-03-18 17:17   ` Nathan Lynch [this message]
2014-03-21 14:58   ` Steve Capper
2014-03-21 16:16     ` Nathan Lynch
2014-03-21 17:05       ` David Riley
2014-03-21 17:35         ` David Riley

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=53287FB3.1050103@mentor.com \
    --to=nathan_lynch@mentor.com \
    --cc=linux-arm-kernel@lists.infradead.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 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.