[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAJ+HfNit8dsXV360qUCiG33yNdbf7=w58M9DncOuNqNOCAE40A@mail.gmail.com>
Date: Mon, 3 Feb 2020 13:11:32 +0100
From: Björn Töpel <bjorn.topel@...il.com>
To: Palmer Dabbelt <palmerdabbelt@...gle.com>
Cc: Daniel Borkmann <daniel@...earbox.net>,
Alexei Starovoitov <ast@...nel.org>,
Netdev <netdev@...r.kernel.org>, linux-riscv@...ts.infradead.org,
bpf <bpf@...r.kernel.org>
Subject: Re: [PATCH bpf-next v2 7/9] riscv, bpf: optimize calls
On Tue, 28 Jan 2020 at 03:15, Palmer Dabbelt <palmerdabbelt@...gle.com> wrote:
>
[...]
> >
> > BPF passes arguments in R1, R2, ..., and return value in R0. Given
> > that a0 plays the role of R1 and R0, how can we avoid the register
> > juggling (without complicating the JIT too much)? It would be nice
> > though... and ARM64 has the same concern AFAIK.
>
> Oh, why did you say that? This kind of stuff is why I'm twenty days behind on
> email...
>
> https://lore.kernel.org/bpf/20200128021145.36774-1-palmerdabbelt@google.com/T/#t
>
> :)
>
(back from vacation)
:-D Very nice, I'll take a look!
Björn
Powered by blists - more mailing lists