Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1661319 > unrolled thread

Re: [PATCH 13/20] arm64: ilp32: share aarch32 syscall handlers

Started byCatalin Marinas <catalin.marinas@arm.com>
First post2017-06-08 16:20 +0200
Last post2017-06-08 16:30 +0200
Articles 2 — 2 participants

Back to article view | Back to linux.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Re: [PATCH 13/20] arm64: ilp32: share aarch32 syscall handlers Catalin Marinas <catalin.marinas@arm.com> - 2017-06-08 16:20 +0200
    Re: [PATCH 13/20] arm64: ilp32: share aarch32 syscall handlers Arnd Bergmann <arnd@arndb.de> - 2017-06-08 16:30 +0200

#1661319 — Re: [PATCH 13/20] arm64: ilp32: share aarch32 syscall handlers

FromCatalin Marinas <catalin.marinas@arm.com>
Date2017-06-08 16:20 +0200
SubjectRe: [PATCH 13/20] arm64: ilp32: share aarch32 syscall handlers
Message-ID<tQ6s2-5m5-21@gated-at.bofh.it>
On Sun, Jun 04, 2017 at 03:00:02PM +0300, Yury Norov wrote:
> off_t is  passed in register pair just like in aarch32.
> In this patch corresponding aarch32 handlers are shared to
> ilp32 code.

Is the comment here relevant? IOW, do we have any AArch64/ILP32 syscall
where off_t is used as an argument? AFAICT, the *64 syscalls use loff_t
or loff_t *.

-- 
Catalin

[toc] | [next] | [standalone]


#1661329

FromArnd Bergmann <arnd@arndb.de>
Date2017-06-08 16:30 +0200
Message-ID<tQ6BI-5pp-15@gated-at.bofh.it>
In reply to#1661319
On Thu, Jun 8, 2017 at 4:10 PM, Catalin Marinas <catalin.marinas@arm.com> wrote:
> On Sun, Jun 04, 2017 at 03:00:02PM +0300, Yury Norov wrote:
>> off_t is  passed in register pair just like in aarch32.
>> In this patch corresponding aarch32 handlers are shared to
>> ilp32 code.
>
> Is the comment here relevant? IOW, do we have any AArch64/ILP32 syscall
> where off_t is used as an argument? AFAICT, the *64 syscalls use loff_t
> or loff_t *.

I think it should just be reworded, the 'off_t' above seems to refer to the
user space type that corresponds to the kernel's loff_t.

       Arnd

[toc] | [prev] | [standalone]


Back to top | Article view | linux.kernel


csiph-web