Re: The brief status of Debian riscv porting --2023/01/08
Hi!
On Tue, Jun 20, 2023 at 5:17 PM Bo YU <tsu.yubo@gmail.com> wrote:
>
> Hi!
>
> On Tue, Jun 20, 2023 at 12:21 PM Umit Sami <umit.sami@memcus.com> wrote:
> >
> > I meant to say eBPF !
> I just tested eBPF demo with libbpf-bootstrap[0] but unfortunately,
> the demo can not be run due to kernel config
> does not support BTF maybe:
After this MR[0] has been merged, I think now Debian riscv64 can run
the eBFP program:
```
rv@unmatched:~/git/libbpf-bootstrap/examples/c$ sudo ./minimal
[sudo] password for rv:
libbpf: loading object 'minimal_bpf' from buffer
libbpf: elf: section(2) .symtab, size 216, link 1, flags 0, type=2
libbpf: elf: section(3) tp/syscalls/sys_enter_write, size 104, link 0,
flags 6, type=1
libbpf: sec 'tp/syscalls/sys_enter_write': found program 'handle_tp'
at insn offset 0 (0 bytes), code size 13 insns (104 bytes)
libbpf: elf: section(4) license, size 13, link 0, flags 3, type=1
libbpf: license of minimal_bpf is Dual BSD/GPL
libbpf: elf: section(5) .bss, size 4, link 0, flags 3, type=8
libbpf: elf: section(6) .rodata, size 28, link 0, flags 2, type=1
libbpf: elf: section(7) .reltp/syscalls/sys_enter_write, size 32, link
2, flags 40, type=9
...
libbpf: map 'minimal_.bss': created successfully, fd=4
libbpf: map 'minimal_.rodata': created successfully, fd=5
Successfully started! Please run `sudo cat
/sys/kernel/debug/tracing/trace_pipe` to see output of the BPF
programs.
```
BR,
Bo
[0]: https://salsa.debian.org/kernel-team/linux/-/merge_requests/779
>
> ```
> rv@unmatched:~/git/libbpf-bootstrap/examples/c$ sudo ./bootstrap
> [sudo] password for rv:
> libbpf: failed to get EHDR from /boot/vmlinux-6.3.0-1-riscv64
> libbpf: failed to find valid kernel BTF
> libbpf: Error loading vmlinux BTF: -3
> libbpf: failed to load object 'bootstrap_bpf'
> libbpf: failed to load BPF skeleton 'bootstrap_bpf': -3
> Failed to load and verify BPF skeleton
> ```
> I have submitted the MR[1] and let's see how it goes.
>
> BR,
> Bo
> [0]: https://github.com/libbpf/libbpf-bootstrap
> [1]: https://salsa.debian.org/kernel-team/linux/-/merge_requests/755
>
> >
> > ------------------------
> > Umit D. Sami
> > Founder and CEO - Memcus Inc.
> >
> > Cell: (857) 472-0480
> > Email: umit.sami@memcus.com
> >
> >
> >
> > On Tue, Jun 20, 2023 at 12:19 AM Umit Sami <umit.sami@memcus.com> wrote:
> >>
> >> Hi All,
> >>
> >> I have a question. Is it possible to run an eBFP application inside Linux Kernel for RISC-V architectures at this point in time or is it still a work in progress?
> >>
> >> Umit
> >>
> >>
> >>
> >> ------------------------
> >> Umit D. Sami
> >> Founder and CEO - Memcus Inc.
> >>
> >> Cell: (857) 472-0480
> >> Email: umit.sami@memcus.com
> >>
> >>
> >>
> >> On Sun, Jan 8, 2023 at 10:17 AM Bo YU <tsu.yubo@gmail.com> wrote:
> >>>
> >>> Hi,
> >>>
> >>> This is the first issue of status with Debian riscv64 porting of the
> >>> new year. With less than a week[0] to go, The freeze for bookworm
> >>> will happen. So anyway from now let's look forward to the release of
> >>> bookworm.
> >>>
> >>> Debian riscv64 arch did not catch up with the release of bookworm in
> >>> my view. But we're so close to achieve the goal. Many thanks to
> >>> everyone involved in this process. Without their participation, this
> >>> achievement would not have been possible.
> >>>
> >>> In 2023, we should have several powerful boards(kernel upstream
> >>> supported) that can be used as buildd machines. This will make it
> >>> easier for us to meet Debian official porting requirements.
> >>>
> >>> After several waves of rebuilding[1] for some packages that have not
> >>> built for a long time, There's not a lot of FTBFS on riscv64 packages
> >>> was added here. Another important thing from my view is to help
> >>> nodejs[2] that can be built on riscv64 as soon as possible. This
> >>> caused some dependency issues for debci[3].
> >>>
> >>> BR,
> >>> Bo
> >>>
> >>> [0]: https://release.debian.org/testing/freeze_policy.html
> >>> [1]: https://buildd.debian.org/status/architecture.php?a=riscv64&suite=sid
> >>> [2]: https://buildd.debian.org/status/logs.php?pkg=nodejs&arch=riscv64
> >>> [3]: https://ci.debian.net/packages/n/node-esrecurse/unstable/riscv64/
> >>> --
> >>> Regards,
> >>> --
> >>> Bo YU
> >>>
Reply to: