RISC-V: sys/user.h

RISC-V: sys/user.h

[Lukasz Stelmach]

[-- Attachment #1: Type: text/plain, Size: 263 bytes --]

Hi,

Has sysdeps/unix/sysv/linux/riscv/sys/user.h been deliberately left
empty? Why, unlike x86/aarch64/arm, riscv haven't got it's register
structures defined there?

Kind regards,
-- 
Łukasz Stelmach
Samsung R&D Institute Poland
Samsung Electronics

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]

Re: RISC-V: sys/user.h

[Palmer Dabbelt]

On Fri, 09 Dec 2022 08:36:33 PST (-0800), l.stelmach@samsung.com wrote:
> Has sysdeps/unix/sysv/linux/riscv/sys/user.h been deliberately left
> empty? Why, unlike x86/aarch64/arm, riscv haven't got it's register
> structures defined there?

We don't have a "struct user_regs_struct", IIUC that's for the old 
flavor of ptrace-based register handling ({GET,SET}REGS vs 
{GET,SET}REGSET).  So I think having it empty is the correct thing to 
do.

Re: RISC-V: sys/user.h

[Lukasz Stelmach]

[-- Attachment #1: Type: text/plain, Size: 673 bytes --]

It was <2022-12-09 pią 09:07>, when Palmer Dabbelt wrote:
> On Fri, 09 Dec 2022 08:36:33 PST (-0800), l.stelmach@samsung.com wrote:
>> Has sysdeps/unix/sysv/linux/riscv/sys/user.h been deliberately left
>> empty? Why, unlike x86/aarch64/arm, riscv haven't got it's register
>> structures defined there?
>
> We don't have a "struct user_regs_struct", IIUC that's for the old
> flavor of ptrace-based register handling ({GET,SET}REGS vs 
> {GET,SET}REGSET).  So I think having it empty is the correct thing to
> do.


Thanks, this is a precious hint. Now, I know where to look around.

-- 
Łukasz Stelmach
Samsung R&D Institute Poland
Samsung Electronics

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]

Re: RISC-V: sys/user.h

[Palmer Dabbelt]

On Fri, 09 Dec 2022 13:36:05 PST (-0800), l.stelmach@samsung.com wrote:
> It was <2022-12-09 pią 09:07>, when Palmer Dabbelt wrote:
>> On Fri, 09 Dec 2022 08:36:33 PST (-0800), l.stelmach@samsung.com wrote:
>>> Has sysdeps/unix/sysv/linux/riscv/sys/user.h been deliberately left
>>> empty? Why, unlike x86/aarch64/arm, riscv haven't got it's register
>>> structures defined there?
>>
>> We don't have a "struct user_regs_struct", IIUC that's for the old
>> flavor of ptrace-based register handling ({GET,SET}REGS vs 
>> {GET,SET}REGSET).  So I think having it empty is the correct thing to
>> do.
>
>
> Thanks, this is a precious hint. Now, I know where to look around.

Those definitions are in <sysdeps/unix/sysv/linux/riscv/sys/ucontext.h> 
(and also in Linux).

Re: RISC-V: sys/user.h

[Lukasz Stelmach]

[-- Attachment #1: Type: text/plain, Size: 1391 bytes --]

It was <2022-12-09 pią 16:26>, when Palmer Dabbelt wrote:
> On Fri, 09 Dec 2022 13:36:05 PST (-0800), l.stelmach@samsung.com wrote:
>> It was <2022-12-09 pią 09:07>, when Palmer Dabbelt wrote:
>>> On Fri, 09 Dec 2022 08:36:33 PST (-0800), l.stelmach@samsung.com wrote:
>>>> Has sysdeps/unix/sysv/linux/riscv/sys/user.h been deliberately left
>>>> empty? Why, unlike x86/aarch64/arm, riscv haven't got it's register
>>>> structures defined there?
>>>
>>> We don't have a "struct user_regs_struct", IIUC that's for the old
>>> flavor of ptrace-based register handling ({GET,SET}REGS vs
>>> {GET,SET}REGSET).  So I think having it empty is the correct thing
>>> to do.
>>
>>
>> Thanks, this is a precious hint. Now, I know where to look around.
>
> Those definitions are in
> <sysdeps/unix/sysv/linux/riscv/sys/ucontext.h>

I missed this one

> (and also in Linux).

but found this <asm/ptrace.h>.


It's not that we didn't have these definitions at all, but because
we'are building a small tool that we want to run on different
architectures, we're looking into how to access the regiester data in
core dumps (we need to read one or two values) without lengthy #if#elifs
around the code and includes. We just want this tiny piece of code of
ours to be noice (-;

Thanks for help (-:
-- 
Łukasz Stelmach
Samsung R&D Institute Poland
Samsung Electronics

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]