From: Vincenzo Frascino <vincenzo.frascino@arm.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: linux-arch <linux-arch@vger.kernel.org>,
Shuah Khan <shuah@kernel.org>,
Rasmus Villemoes <linux@rasmusvillemoes.dk>,
Catalin Marinas <catalin.marinas@arm.com>,
Daniel Lezcano <daniel.lezcano@linaro.org>,
Will Deacon <will.deacon@arm.com>,
Russell King <linux@armlinux.org.uk>,
Ralf Baechle <ralf@linux-mips.org>,
Mark Salyzyn <salyzyn@android.com>,
Paul Burton <paul.burton@mips.com>,
Dmitry Safonov <0x7f454c46@gmail.com>,
Thomas Gleixner <tglx@linutronix.de>,
Peter Collingbourne <pcc@google.com>,
Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v5 00/23] Unify vDSOs across more architectures
Date: Thu, 28 Feb 2019 12:09:21 +0000 [thread overview]
Message-ID: <b02ee1da-e756-f7c7-ad8d-944b9b9e56e0@arm.com> (raw)
In-Reply-To: <CAK8P3a1Q1uMFLs6eq26Rkv8hQdu0FkPUoq0gDnZPju-Eu1oHgQ@mail.gmail.com>
Hi Arnd,
thank you for testing my code.
On 28/02/2019 11:40, Arnd Bergmann wrote:
> On Fri, Feb 22, 2019 at 1:25 PM Vincenzo Frascino
> <vincenzo.frascino@arm.com> wrote:
>>
>> vDSO (virtual dynamic shared object) is a mechanism that the Linux
>> kernel provides as an alternative to system calls to reduce where
>> possible the costs in terms of cycles.
>> This is possible because certain syscalls like gettimeofday() do
>> not write any data and return one or more values that are stored
>> in the kernel, which makes relatively safe calling them directly
>> as a library function.
>
> I tried applying the series on top of v5.0-rc7, and got a set of
> build warnings with arm64 defconfig:
>
> In file included from /git/arm-soc/arch/arm64/include/asm/thread_info.h:30:0,
> from /git/arm-soc/include/linux/thread_info.h:38,
> from /git/arm-soc/arch/arm64/include/asm/preempt.h:5,
> from /git/arm-soc/include/linux/preempt.h:78,
> from /git/arm-soc/include/linux/spinlock.h:51,
> from /git/arm-soc/include/linux/seqlock.h:36,
> from /git/arm-soc/include/linux/time.h:6,
> from /git/arm-soc/lib/vdso/gettimeofday.c:7,
> from <command-line>:0:
> /git/arm-soc/arch/arm64/include/asm/memory.h: In function ‘kaslr_offset’:
> /git/arm-soc/arch/arm64/include/asm/memory.h:191:2: warning: left
> shift count >= width of type [enabled by default]
> return kimage_vaddr - KIMAGE_VADDR;
> ^
> /git/arm-soc/arch/arm64/include/asm/memory.h: In function ‘virt_to_phys’:
> /git/arm-soc/arch/arm64/include/asm/memory.h:283:2: warning: left
> shift count >= width of type [enabled by default]
> return __virt_to_phys((unsigned long)(x));
> ^
> /git/arm-soc/arch/arm64/include/asm/memory.h:283:2: warning: left
> shift count >= width of type [enabled by default]
> /git/arm-soc/arch/arm64/include/asm/memory.h: In function ‘phys_to_virt’:
> /git/arm-soc/arch/arm64/include/asm/memory.h:289:2: warning: left
> shift count >= width of type [enabled by default]
> return (void *)(__phys_to_virt(x));
> ^
> In file included from /git/arm-soc/arch/arm64/include/asm/pgtable-hwdef.h:19:0,
> from /git/arm-soc/arch/arm64/include/asm/processor.h:46,
> from /git/arm-soc/arch/arm64/include/asm/elf.h:129,
> from /git/arm-soc/include/linux/elf.h:5,
> from /git/arm-soc/include/linux/elfnote.h:62,
> from /git/arm-soc/arch/arm64/kernel/vdso32/note.c:11:
> /git/arm-soc/arch/arm64/include/asm/memory.h: In function ‘kaslr_offset’:
> /git/arm-soc/arch/arm64/include/asm/memory.h:191:2: warning: left
> shift count >= width of type [enabled by default]
> return kimage_vaddr - KIMAGE_VADDR;
> ^
> /git/arm-soc/arch/arm64/include/asm/memory.h: In function ‘virt_to_phys’:
> /git/arm-soc/arch/arm64/include/asm/memory.h:283:2: warning: left
> shift count >= width of type [enabled by default]
> return __virt_to_phys((unsigned long)(x));
> ^
> /git/arm-soc/arch/arm64/include/asm/memory.h:283:2: warning: left
> shift count >= width of type [enabled by default]
> /git/arm-soc/arch/arm64/include/asm/memory.h: In function ‘phys_to_virt’:
> /git/arm-soc/arch/arm64/include/asm/memory.h:289:2: warning: left
> shift count >= width of type [enabled by default]
> return (void *)(__phys_to_virt(x));
> ^
>
> I think this is all harmless, but we need to limit the set of header files
> that can be included indirectly when compiling the vdso in arm32 mode.
>
I agree with you on the principle, but I am unable to replicate the warnings.
Did you make any customization to the default defconfig? What is the top
commit-id you have on your tree?
> Arnd
>
--
Regards,
Vincenzo
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: Vincenzo Frascino <vincenzo.frascino@arm.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: linux-arch <linux-arch@vger.kernel.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will.deacon@arm.com>,
Russell King <linux@armlinux.org.uk>,
Ralf Baechle <ralf@linux-mips.org>,
Paul Burton <paul.burton@mips.com>,
Daniel Lezcano <daniel.lezcano@linaro.org>,
Thomas Gleixner <tglx@linutronix.de>,
Mark Salyzyn <salyzyn@android.com>,
Peter Collingbourne <pcc@google.com>,
Shuah Khan <shuah@kernel.org>,
Dmitry Safonov <0x7f454c46@gmail.com>,
Rasmus Villemoes <linux@rasmusvillemoes.dk>
Subject: Re: [PATCH v5 00/23] Unify vDSOs across more architectures
Date: Thu, 28 Feb 2019 12:09:21 +0000 [thread overview]
Message-ID: <b02ee1da-e756-f7c7-ad8d-944b9b9e56e0@arm.com> (raw)
Message-ID: <20190228120921._e55pJKyKYo96kAd1LwrLZ5F6NTtgOA8muy9083-pvY@z> (raw)
In-Reply-To: <CAK8P3a1Q1uMFLs6eq26Rkv8hQdu0FkPUoq0gDnZPju-Eu1oHgQ@mail.gmail.com>
Hi Arnd,
thank you for testing my code.
On 28/02/2019 11:40, Arnd Bergmann wrote:
> On Fri, Feb 22, 2019 at 1:25 PM Vincenzo Frascino
> <vincenzo.frascino@arm.com> wrote:
>>
>> vDSO (virtual dynamic shared object) is a mechanism that the Linux
>> kernel provides as an alternative to system calls to reduce where
>> possible the costs in terms of cycles.
>> This is possible because certain syscalls like gettimeofday() do
>> not write any data and return one or more values that are stored
>> in the kernel, which makes relatively safe calling them directly
>> as a library function.
>
> I tried applying the series on top of v5.0-rc7, and got a set of
> build warnings with arm64 defconfig:
>
> In file included from /git/arm-soc/arch/arm64/include/asm/thread_info.h:30:0,
> from /git/arm-soc/include/linux/thread_info.h:38,
> from /git/arm-soc/arch/arm64/include/asm/preempt.h:5,
> from /git/arm-soc/include/linux/preempt.h:78,
> from /git/arm-soc/include/linux/spinlock.h:51,
> from /git/arm-soc/include/linux/seqlock.h:36,
> from /git/arm-soc/include/linux/time.h:6,
> from /git/arm-soc/lib/vdso/gettimeofday.c:7,
> from <command-line>:0:
> /git/arm-soc/arch/arm64/include/asm/memory.h: In function ‘kaslr_offset’:
> /git/arm-soc/arch/arm64/include/asm/memory.h:191:2: warning: left
> shift count >= width of type [enabled by default]
> return kimage_vaddr - KIMAGE_VADDR;
> ^
> /git/arm-soc/arch/arm64/include/asm/memory.h: In function ‘virt_to_phys’:
> /git/arm-soc/arch/arm64/include/asm/memory.h:283:2: warning: left
> shift count >= width of type [enabled by default]
> return __virt_to_phys((unsigned long)(x));
> ^
> /git/arm-soc/arch/arm64/include/asm/memory.h:283:2: warning: left
> shift count >= width of type [enabled by default]
> /git/arm-soc/arch/arm64/include/asm/memory.h: In function ‘phys_to_virt’:
> /git/arm-soc/arch/arm64/include/asm/memory.h:289:2: warning: left
> shift count >= width of type [enabled by default]
> return (void *)(__phys_to_virt(x));
> ^
> In file included from /git/arm-soc/arch/arm64/include/asm/pgtable-hwdef.h:19:0,
> from /git/arm-soc/arch/arm64/include/asm/processor.h:46,
> from /git/arm-soc/arch/arm64/include/asm/elf.h:129,
> from /git/arm-soc/include/linux/elf.h:5,
> from /git/arm-soc/include/linux/elfnote.h:62,
> from /git/arm-soc/arch/arm64/kernel/vdso32/note.c:11:
> /git/arm-soc/arch/arm64/include/asm/memory.h: In function ‘kaslr_offset’:
> /git/arm-soc/arch/arm64/include/asm/memory.h:191:2: warning: left
> shift count >= width of type [enabled by default]
> return kimage_vaddr - KIMAGE_VADDR;
> ^
> /git/arm-soc/arch/arm64/include/asm/memory.h: In function ‘virt_to_phys’:
> /git/arm-soc/arch/arm64/include/asm/memory.h:283:2: warning: left
> shift count >= width of type [enabled by default]
> return __virt_to_phys((unsigned long)(x));
> ^
> /git/arm-soc/arch/arm64/include/asm/memory.h:283:2: warning: left
> shift count >= width of type [enabled by default]
> /git/arm-soc/arch/arm64/include/asm/memory.h: In function ‘phys_to_virt’:
> /git/arm-soc/arch/arm64/include/asm/memory.h:289:2: warning: left
> shift count >= width of type [enabled by default]
> return (void *)(__phys_to_virt(x));
> ^
>
> I think this is all harmless, but we need to limit the set of header files
> that can be included indirectly when compiling the vdso in arm32 mode.
>
I agree with you on the principle, but I am unable to replicate the warnings.
Did you make any customization to the default defconfig? What is the top
commit-id you have on your tree?
> Arnd
>
--
Regards,
Vincenzo
next prev parent reply other threads:[~2019-02-28 12:09 UTC|newest]
Thread overview: 120+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-22 12:24 [PATCH v5 00/23] Unify vDSOs across more architectures Vincenzo Frascino
2019-02-22 12:24 ` Vincenzo Frascino
2019-02-22 12:24 ` [PATCH v5 01/23] kernel: Standardize vdso_datapage Vincenzo Frascino
2019-02-22 12:24 ` Vincenzo Frascino
2019-02-22 12:58 ` Mark Rutland
2019-02-22 12:58 ` Mark Rutland
2019-02-23 16:51 ` Thomas Gleixner
2019-02-23 16:51 ` Thomas Gleixner
2019-02-27 14:23 ` Vincenzo Frascino
2019-02-27 14:23 ` Vincenzo Frascino
2019-02-22 12:24 ` [PATCH v5 02/23] kernel: Define gettimeofday vdso common code Vincenzo Frascino
2019-02-22 12:24 ` Vincenzo Frascino
2019-02-22 13:34 ` Mark Rutland
2019-02-22 13:34 ` Mark Rutland
2019-02-22 13:49 ` Arnd Bergmann
2019-02-22 13:49 ` Arnd Bergmann
2019-02-22 14:36 ` Arnd Bergmann
2019-02-22 14:36 ` Arnd Bergmann
2019-02-27 14:52 ` Vincenzo Frascino
2019-02-27 14:52 ` Vincenzo Frascino
2019-02-28 9:29 ` Arnd Bergmann
2019-02-28 9:29 ` Arnd Bergmann
2019-02-28 11:58 ` [PATCH 1/2] vdso: use fixed-size time types Arnd Bergmann
2019-02-28 11:58 ` Arnd Bergmann
2019-02-28 11:58 ` [PATCH 2/2] vdso: add clock_gettime64 Arnd Bergmann
2019-02-28 11:58 ` Arnd Bergmann
2019-02-28 13:42 ` [PATCH 1/2] vdso: use fixed-size time types Thomas Gleixner
2019-02-28 13:42 ` Thomas Gleixner
2019-02-28 13:45 ` Vincenzo Frascino
2019-02-28 13:45 ` Vincenzo Frascino
2019-02-23 10:34 ` [PATCH v5 02/23] kernel: Define gettimeofday vdso common code Thomas Gleixner
2019-02-23 10:34 ` Thomas Gleixner
2019-02-25 14:09 ` Vincenzo Frascino
2019-02-25 14:09 ` Vincenzo Frascino
2019-02-23 17:31 ` Thomas Gleixner
2019-02-23 17:31 ` Thomas Gleixner
2019-02-27 13:47 ` Vincenzo Frascino
2019-02-27 13:47 ` Vincenzo Frascino
2019-02-27 15:49 ` Thomas Gleixner
2019-02-27 15:49 ` Thomas Gleixner
2019-02-27 16:06 ` Vincenzo Frascino
2019-02-27 16:06 ` Vincenzo Frascino
2019-02-22 12:24 ` [PATCH v5 03/23] arm64: Build vDSO with -ffixed-x18 Vincenzo Frascino
2019-02-22 12:24 ` Vincenzo Frascino
2019-02-22 12:24 ` [PATCH v5 04/23] arm64: Substitute gettimeofday with C implementation Vincenzo Frascino
2019-02-22 12:24 ` Vincenzo Frascino
2019-02-22 13:42 ` Mark Rutland
2019-02-22 13:42 ` Mark Rutland
2019-02-22 12:24 ` [PATCH v5 05/23] arm64: compat: Alloc separate pages for vectors and sigpage Vincenzo Frascino
2019-02-22 12:24 ` Vincenzo Frascino
2019-02-22 12:24 ` [PATCH v5 06/23] arm64: compat: Split kuser32 Vincenzo Frascino
2019-02-22 12:24 ` Vincenzo Frascino
2019-02-22 12:24 ` [PATCH v5 07/23] arm64: compat: Refactor aarch32_alloc_vdso_pages() Vincenzo Frascino
2019-02-22 12:24 ` Vincenzo Frascino
2019-02-22 12:24 ` [PATCH v5 08/23] arm64: compat: Add KUSER_HELPERS config option Vincenzo Frascino
2019-02-22 12:24 ` Vincenzo Frascino
2019-02-22 14:04 ` Mark Rutland
2019-02-22 14:04 ` Mark Rutland
2019-02-22 14:09 ` Russell King - ARM Linux admin
2019-02-22 14:09 ` Russell King - ARM Linux admin
2019-02-26 12:10 ` Vincenzo Frascino
2019-02-26 12:10 ` Vincenzo Frascino
2019-02-22 12:24 ` [PATCH v5 09/23] arm64: compat: Add missing syscall numbers Vincenzo Frascino
2019-02-22 12:24 ` Vincenzo Frascino
2019-02-22 12:24 ` [PATCH v5 10/23] arm64: compat: Expose signal related structures Vincenzo Frascino
2019-02-22 12:24 ` Vincenzo Frascino
2019-02-22 12:24 ` [PATCH v5 11/23] arm64: compat: Generate asm offsets for signals Vincenzo Frascino
2019-02-22 12:24 ` Vincenzo Frascino
2019-02-22 14:22 ` Mark Rutland
2019-02-22 14:22 ` Mark Rutland
2019-02-22 12:24 ` [PATCH v5 12/23] lib: vdso: Add compat support Vincenzo Frascino
2019-02-22 12:24 ` Vincenzo Frascino
2019-02-22 12:24 ` [PATCH v5 13/23] arm64: compat: Add vDSO Vincenzo Frascino
2019-02-22 12:24 ` Vincenzo Frascino
2019-02-22 14:32 ` Mark Rutland
2019-02-22 14:32 ` Mark Rutland
2019-02-22 12:24 ` [PATCH v5 14/23] arm64: Refactor vDSO code Vincenzo Frascino
2019-02-22 12:24 ` Vincenzo Frascino
2019-02-22 14:37 ` Mark Rutland
2019-02-22 14:37 ` Mark Rutland
2019-02-22 12:24 ` [PATCH v5 15/23] arm64: compat: vDSO setup for compat layer Vincenzo Frascino
2019-02-22 12:24 ` Vincenzo Frascino
2019-02-22 12:24 ` [PATCH v5 16/23] arm64: elf: vDSO code page discovery Vincenzo Frascino
2019-02-22 12:24 ` Vincenzo Frascino
2019-02-22 12:24 ` [PATCH v5 17/23] arm64: compat: Get sigreturn trampolines from vDSO Vincenzo Frascino
2019-02-22 12:24 ` Vincenzo Frascino
2019-02-22 12:24 ` [PATCH v5 18/23] arm64: Add vDSO compat support Vincenzo Frascino
2019-02-22 12:24 ` Vincenzo Frascino
2019-02-22 12:24 ` [PATCH v5 19/23] arm64: Enable compat vDSO support Vincenzo Frascino
2019-02-22 12:24 ` Vincenzo Frascino
2019-02-22 14:39 ` Mark Rutland
2019-02-22 14:39 ` Mark Rutland
2019-02-22 14:41 ` Mark Rutland
2019-02-22 14:41 ` Mark Rutland
2019-02-22 12:24 ` [PATCH v5 20/23] arm: Add support for generic vDSO Vincenzo Frascino
2019-02-22 12:24 ` Vincenzo Frascino
2019-02-22 12:24 ` [PATCH v5 21/23] mips: " Vincenzo Frascino
2019-02-22 12:24 ` Vincenzo Frascino
2019-02-22 12:24 ` [PATCH v5 22/23] x86: " Vincenzo Frascino
2019-02-22 12:24 ` Vincenzo Frascino
2019-02-23 10:45 ` Thomas Gleixner
2019-02-23 10:45 ` Thomas Gleixner
2019-02-27 16:18 ` Vincenzo Frascino
2019-02-27 16:18 ` Vincenzo Frascino
2019-02-22 12:24 ` [PATCH v5 23/23] kselftest: Extend vDSO selftest Vincenzo Frascino
2019-02-22 12:24 ` Vincenzo Frascino
2019-02-23 17:39 ` [PATCH v5 00/23] Unify vDSOs across more architectures Thomas Gleixner
2019-02-23 17:39 ` Thomas Gleixner
2019-02-28 11:40 ` Arnd Bergmann
2019-02-28 11:40 ` Arnd Bergmann
2019-02-28 12:09 ` Vincenzo Frascino [this message]
2019-02-28 12:09 ` Vincenzo Frascino
2019-02-28 12:38 ` Arnd Bergmann
2019-02-28 12:38 ` Arnd Bergmann
2019-02-28 12:42 ` Vincenzo Frascino
2019-02-28 12:42 ` Vincenzo Frascino
2019-02-28 13:54 ` Arnd Bergmann
2019-02-28 13:54 ` Arnd Bergmann
2019-02-28 15:51 ` Vincenzo Frascino
2019-02-28 15:51 ` Vincenzo Frascino
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=b02ee1da-e756-f7c7-ad8d-944b9b9e56e0@arm.com \
--to=vincenzo.frascino@arm.com \
--cc=0x7f454c46@gmail.com \
--cc=arnd@arndb.de \
--cc=catalin.marinas@arm.com \
--cc=daniel.lezcano@linaro.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux@armlinux.org.uk \
--cc=linux@rasmusvillemoes.dk \
--cc=paul.burton@mips.com \
--cc=pcc@google.com \
--cc=ralf@linux-mips.org \
--cc=salyzyn@android.com \
--cc=shuah@kernel.org \
--cc=tglx@linutronix.de \
--cc=will.deacon@arm.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