linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Richard Weinberger <richard@nod.at>
To: Masahiro Yamada <yamada.masahiro@socionext.com>
Cc: Jeff Dike <jdike@addtoit.com>,
	Nicholas Piggin <npiggin@gmail.com>,
	uml-devel <user-mode-linux-devel@lists.sourceforge.net>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [UML] Question about arch/x86/um/vdso/vdso-syms.lds
Date: Wed, 09 May 2018 08:36:09 +0200	[thread overview]
Message-ID: <1621114.mSmC2JOP5I@blindfold> (raw)
In-Reply-To: <CAK7LNAQREY=32tX7m8dbJ6a_AhXLF_y-n5VLFBBcvXWaRvTmHg@mail.gmail.com>

Masahiro,

Am Mittwoch, 9. Mai 2018, 05:36:18 CEST schrieb Masahiro Yamada:
> Hi Richard,
> 
> 
> Please let me ask a question about vdso-syms.lds
> under arch/x86/um/vdso/.
> 
> This file exists since:
> 
> commit f1c2bb8b9964ed31de988910f8b1cfb586d30091
> Author: Richard Weinberger <richard@nod.at>
> Date:   Mon Jul 25 17:12:54 2011 -0700
> 
>     um: implement a x86_64 vDSO
> 
> 
> So, I think you are the right person
> to reach out to.
> 
> 
> Originally, vdso-syms.lds was linked to vmlinux,
> but it is not since:
> 
> commit 827880ec260ba048f95fe646b96a205c394fa0f0
> Author: Nicholas Piggin <npiggin@gmail.com>
> Date:   Fri Jun 9 15:24:16 2017 +1000
> 
>     x86/um: thin archives build fix
> 
> 
> 
> Something may be missing from my thought,
> but I wonder what vdso-syms.lds is used for.

Hmm, I think we can kill it. In 2011 I used the x86 vdso
code as "template" this is how the file made it into UML.
AFAICT it was forgotten after all the vdso related refactoring
in um and x86.

Thanks,
//richard

  reply	other threads:[~2018-05-09  6:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-09  3:36 [UML] Question about arch/x86/um/vdso/vdso-syms.lds Masahiro Yamada
2018-05-09  6:36 ` Richard Weinberger [this message]
2018-05-11  3:48   ` Masahiro Yamada

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=1621114.mSmC2JOP5I@blindfold \
    --to=richard@nod.at \
    --cc=jdike@addtoit.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=npiggin@gmail.com \
    --cc=user-mode-linux-devel@lists.sourceforge.net \
    --cc=yamada.masahiro@socionext.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;
as well as URLs for NNTP newsgroup(s).