From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: VDSO: depend on CPU_V7
Date: Thu, 16 Apr 2015 17:42:18 +0200 [thread overview]
Message-ID: <3179253.8VITBr4Esl@wuerfel> (raw)
In-Reply-To: <552FD47E.7030107@mentor.com>
On Thursday 16 April 2015 10:25:50 Nathan Lynch wrote:
> > diff --git a/arch/arm/mm/Kconfig b/arch/arm/mm/Kconfig
> > index b7644310236b..b4f92b9a13ac 100644
> > --- a/arch/arm/mm/Kconfig
> > +++ b/arch/arm/mm/Kconfig
> > @@ -827,7 +827,7 @@ config KUSER_HELPERS
> >
> > config VDSO
> > bool "Enable VDSO for acceleration of some system calls"
> > - depends on AEABI && MMU
> > + depends on AEABI && MMU && CPU_V7
> > default y if ARM_ARCH_TIMER
> > select GENERIC_TIME_VSYSCALL
> > help
>
> Before I put this in RMK's patch queue I'd prefer to get an ack or more
> details (kernel config, toolchain) on the build failure, since I've been
> unable to recreate it. Arnd?
>
Good idea. I checked the patch against the failed randconfig, and must
unfortunately report that it does not fix the problem.
I'm attaching the .config to this email. Two things to note:
- this is building for mach-rpc, so CONFIG_CPU_32v3 is enabled, and
presumably this is required for reproducing the problem, while
building for ARMv4 as I previously said in error does not cause
the problem.
- I have verified that CONFIG_VDSO is disabled here, but the file is
still getting compiled.
Arnd
-------------- next part --------------
A non-text attachment was scrubbed...
Name: randconfig-vds-bug.gz
Type: application/gzip
Size: 16868 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20150416/29cd4fb7/attachment-0001.gz>
next prev parent reply other threads:[~2015-04-16 15:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-08 21:41 [PATCH] ARM: VDSO: depend on CPU_V7 Nathan Lynch
2015-04-16 15:25 ` Nathan Lynch
2015-04-16 15:42 ` Arnd Bergmann [this message]
2015-04-16 16:10 ` Russell King - ARM Linux
2015-04-16 16:33 ` Nathan Lynch
2015-04-16 17:14 ` Arnd Bergmann
2015-04-17 20:54 ` Nathan Lynch
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=3179253.8VITBr4Esl@wuerfel \
--to=arnd@arndb.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox