From: shea@shealevy.com (Shea Levy)
To: linux-riscv@lists.infradead.org
Subject: RISC-V Seccomp Support?
Date: Thu, 01 Mar 2018 06:44:20 -0500 [thread overview]
Message-ID: <87d10o2f6z.fsf@xps13.shealevy.com> (raw)
In-Reply-To: <mhng-05569257-b64f-4bc4-b7ce-c86060a41e76@palmer-si-x1c4>
OK, thanks. I'll look into getting that working.
Palmer Dabbelt <palmer@sifive.com> writes:
> On Sun, 25 Feb 2018 20:06:52 PST (-0800), shea at shealevy.com wrote:
>> Is anyone actively working on CONFIG_HAVE_ARCH_SECCOMP_FILTER support
>> for RISC-V? If not, any pointers to getting started on that?
>
> IIRC, the filters for seccomp are based on some variant of BPF. I bet the vast
> majority of the work here will be bringing up the BPF infrastructure for
> RISC-V.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 832 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-riscv/attachments/20180301/82271749/attachment.sig>
prev parent reply other threads:[~2018-03-01 11:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-26 4:06 RISC-V Seccomp Support? Shea Levy
2018-02-27 1:28 ` Palmer Dabbelt
2018-03-01 11:44 ` Shea Levy [this message]
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=87d10o2f6z.fsf@xps13.shealevy.com \
--to=shea@shealevy.com \
--cc=linux-riscv@lists.infradead.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox