Re: [PATCH] riscv/entry: get correct syscall number from syscall_get_nr()

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 2024-10-29 03:33, Björn Töpel wrote:
> On Mon, 28 Oct 2024 at 17:26, Celeste Liu <coelacanthushex@xxxxxxxxx> wrote:
>>
>>
>> On 2024-10-28 08:17, Ron Economos wrote:
>>> On 10/27/24 2:52 PM, Thomas Gleixner wrote:
>>>> On Mon, Oct 28 2024 at 01:01, Celeste Liu wrote:
>>>>> On 2024-10-27 23:56, Thomas Gleixner wrote:
>>>>>> Equivalently you need to be able to modify orig_a0 for changing arg0,
>>>>>> no?
>>>>> Ok.
>>>>>
>>>>> Greg, could you accept a backport a new API parameter for
>>>>> PTRACE_GETREGSET/PTRACE_SETREGSET to 4.19 LTS branch?
>>>> Fix the problem properly and put a proper Fixes tag on it and worry
>>>> about the backport later.
>>>>
>>>> Thanks,
>>>>
>>>>          tglx
>>>>
>>> I wouldn't worry about backporting to the 4.19 kernel. It's essentially prehistoric for RISC-V. There's no device tree support for any hardware. Also, 4.19 will be going EOL very soon (December 2024).
>>
>> Ok, I will work on preparing a new patch to add a new set in
>> PTRACE_GETREGSET/PTRACE_SETREGSET.
> 
> Thanks for working/finding working on this! Looking forward to the patch!

The patch to add new regset has been sent.
See https://lore.kernel.org/lkml/20241201-riscv-new-regset-v1-1-c83c58abcc7b@xxxxxxxxxxxxxxxxx/T/





[Index of Archives]     [Linux Kernel]     [Kernel Development Newbies]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite Hiking]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux