From: Paul Moore <pmoore@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
coreyb@linux.vnet.ibm.com, qemu-devel@nongnu.org,
Anthony Liguori <anthony@codemonkey.ws>,
Eduardo Otubo <otubo@linux.vnet.ibm.com>
Subject: Re: [Qemu-devel] seccomp: remove unused syscalls - for 1.6
Date: Thu, 18 Jul 2013 17:34:29 -0400 [thread overview]
Message-ID: <6517417.4xQE50F6tB@sifl> (raw)
In-Reply-To: <CAFEAcA9sx8J8hnMJQ1gO2LDY8a6jLLwopp4gg_QE6CcDW-DRog@mail.gmail.com>
On Thursday, July 18, 2013 10:31:46 PM Peter Maydell wrote:
> On 18 July 2013 21:05, Paul Moore <pmoore@redhat.com> wrote:
> > On Thursday, July 18, 2013 08:48:10 PM Peter Maydell wrote:
> >> On 18 July 2013 20:39, Paul Moore <pmoore@redhat.com> wrote:
> >> > On the plus side, I think libseccomp is very close to being pretty much
> >> > feature complete (excluding new architectures that may pop up, at
> >> > present
> >> > we are only x86, x86_64, x32, and ARM)
> >>
> >> ...AArch64 ? :-)
> >
> > Not yet, just 32-bit ARM EABI.
> >
> > If you've got a working system and are willing to so some hacking or run
> > some tests we could work on it for a future libseccomp release. An
> > emulated AArch64 VM would also work, but that route can be slow/annoying.
>
> Simulators are all we have right now (we're juuust getting to the
> point where hardware is starting to become available). I wasn't
> being serious really, though I'm sure somebody (possibly even
> somebody at Red Hat :-)) will work around to it at some point.
Regardless, consider it a standing offer.
--
paul moore
security and virtualization @ redhat
next prev parent reply other threads:[~2013-07-18 21:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-16 18:07 [Qemu-devel] seccomp: remove unused syscalls - for 1.6 Eduardo Otubo
2013-07-16 18:07 ` [Qemu-devel] [PATCHv2 1/2] seccomp: no need to check arch in syscall whitelist Eduardo Otubo
2013-07-16 18:07 ` [Qemu-devel] [PATCHv2 2/2] seccomp: removing unused syscalls from whitelist Eduardo Otubo
2013-07-18 16:28 ` [Qemu-devel] seccomp: remove unused syscalls - for 1.6 Anthony Liguori
2013-07-18 16:35 ` Eduardo Otubo
2013-07-18 16:37 ` Paolo Bonzini
2013-07-18 19:39 ` Paul Moore
2013-07-18 19:48 ` Peter Maydell
2013-07-18 20:05 ` Paul Moore
2013-07-18 21:31 ` Peter Maydell
2013-07-18 21:34 ` Paul Moore [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-07-15 17:29 Eduardo Otubo
2013-07-15 17:29 ` Eduardo Otubo
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=6517417.4xQE50F6tB@sifl \
--to=pmoore@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=coreyb@linux.vnet.ibm.com \
--cc=otubo@linux.vnet.ibm.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).