From: Paul Walmsley <paul.walmsley@sifive.com>
To: "Björn Töpel" <bjorn.topel@gmail.com>
Cc: linux-riscv@lists.infradead.org, palmer@sifive.com,
davidlee@sifive.com, daniel@iogearbox.net,
netdev@vger.kernel.org
Subject: Re: [RFC PATCH 0/3] RV64G eBPF JIT
Date: Fri, 25 Jan 2019 11:54:25 -0800 (PST) [thread overview]
Message-ID: <alpine.DEB.2.21.9999.1901251147250.20864@viisi.sifive.com> (raw)
In-Reply-To: <20190115083518.10149-1-bjorn.topel@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 475 bytes --]
Hi,
thanks for taking a shot at the eBPF JIT; this will be very useful.
On Tue, 15 Jan 2019, Björn Töpel wrote:
> * I've added "HAVE_EFFICIENT_UNALIGNED_ACCESS" to
> arch/riscv/Kconfig. Is this assumption correct?
From a hardware point of view, this is not the case on the Linux-capable
RISC-V ASICs that the public can buy right now (to the best of my
knowledge this is only the SiFive FU540).
So I'd recommend not including this for now.
- Paul
WARNING: multiple messages have this Message-ID (diff)
From: Paul Walmsley <paul.walmsley@sifive.com>
To: "Björn Töpel" <bjorn.topel@gmail.com>
Cc: netdev@vger.kernel.org, linux-riscv@lists.infradead.org,
palmer@sifive.com, daniel@iogearbox.net, davidlee@sifive.com
Subject: Re: [RFC PATCH 0/3] RV64G eBPF JIT
Date: Fri, 25 Jan 2019 11:54:25 -0800 (PST) [thread overview]
Message-ID: <alpine.DEB.2.21.9999.1901251147250.20864@viisi.sifive.com> (raw)
In-Reply-To: <20190115083518.10149-1-bjorn.topel@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 475 bytes --]
Hi,
thanks for taking a shot at the eBPF JIT; this will be very useful.
On Tue, 15 Jan 2019, Björn Töpel wrote:
> * I've added "HAVE_EFFICIENT_UNALIGNED_ACCESS" to
> arch/riscv/Kconfig. Is this assumption correct?
From a hardware point of view, this is not the case on the Linux-capable
RISC-V ASICs that the public can buy right now (to the best of my
knowledge this is only the SiFive FU540).
So I'd recommend not including this for now.
- Paul
[-- Attachment #2: Type: text/plain, Size: 161 bytes --]
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2019-01-25 19:54 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-15 8:35 [RFC PATCH 0/3] RV64G eBPF JIT Björn Töpel
2019-01-15 8:35 ` Björn Töpel
2019-01-15 8:35 ` Björn Töpel
2019-01-15 8:35 ` [RFC PATCH 1/3] riscv: set HAVE_EFFICIENT_UNALIGNED_ACCESS Björn Töpel
2019-01-15 8:35 ` Björn Töpel
2019-01-15 15:39 ` Christoph Hellwig
2019-01-15 15:39 ` Christoph Hellwig
2019-01-15 16:06 ` Björn Töpel
2019-01-15 16:06 ` Björn Töpel
2019-01-25 20:21 ` Palmer Dabbelt
2019-01-25 20:21 ` Palmer Dabbelt
2019-01-26 1:33 ` Jim Wilson
2019-01-26 1:33 ` Jim Wilson
2019-01-29 2:43 ` Palmer Dabbelt
2019-01-29 2:43 ` Palmer Dabbelt
2019-01-15 8:35 ` [RFC PATCH 2/3] riscv: add build infra for JIT compiler Björn Töpel
2019-01-15 8:35 ` Björn Töpel
2019-01-15 15:43 ` Christoph Hellwig
2019-01-15 15:43 ` Christoph Hellwig
2019-01-15 16:09 ` Björn Töpel
2019-01-15 16:09 ` Björn Töpel
2019-01-15 8:35 ` [RFC PATCH 3/3] bpf, riscv: added eBPF JIT for RV64G Björn Töpel
2019-01-15 8:35 ` Björn Töpel
2019-01-15 8:35 ` Björn Töpel
2019-01-15 23:49 ` Daniel Borkmann
2019-01-15 23:49 ` Daniel Borkmann
2019-01-16 7:23 ` Björn Töpel
2019-01-16 7:23 ` Björn Töpel
2019-01-16 15:41 ` Daniel Borkmann
2019-01-16 15:41 ` Daniel Borkmann
2019-01-16 19:06 ` Björn Töpel
2019-01-16 19:06 ` Björn Töpel
2019-01-15 15:40 ` [RFC PATCH 0/3] RV64G eBPF JIT Christoph Hellwig
2019-01-15 15:40 ` Christoph Hellwig
2019-01-15 16:03 ` Björn Töpel
2019-01-15 16:03 ` Björn Töpel
2019-01-25 19:02 ` Palmer Dabbelt
2019-01-25 19:02 ` Palmer Dabbelt
2019-01-25 19:54 ` Paul Walmsley [this message]
2019-01-25 19:54 ` Paul Walmsley
2019-01-27 12:28 ` Björn Töpel
2019-01-27 12:28 ` Björn Töpel
2019-01-30 2:02 ` Palmer Dabbelt
2019-01-30 2:02 ` Palmer Dabbelt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.DEB.2.21.9999.1901251147250.20864@viisi.sifive.com \
--to=paul.walmsley@sifive.com \
--cc=bjorn.topel@gmail.com \
--cc=daniel@iogearbox.net \
--cc=davidlee@sifive.com \
--cc=linux-riscv@lists.infradead.org \
--cc=netdev@vger.kernel.org \
--cc=palmer@sifive.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.