From: Alexander Graf <graf@amazon.com>
To: Sam Caccavale <samcacc@amazon.de>
Cc: <samcaccavale@gmail.com>, <nmanthey@amazon.de>,
<wipawel@amazon.de>, <dwmw@amazon.co.uk>, <mpohlack@amazon.de>,
<karahmed@amazon.de>, <andrew.cooper3@citrix.com>,
<JBeulich@suse.com>, <pbonzini@redhat.com>, <rkrcmar@redhat.com>,
<tglx@linutronix.de>, <mingo@redhat.com>, <bp@alien8.de>,
<hpa@zytor.com>, <paullangton4@gmail.com>,
<anirudhkaushik@google.com>, <x86@kernel.org>,
<kvm@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [v2, 1/4] Build target for emulate.o as a userspace binary
Date: Fri, 21 Jun 2019 15:33:44 +0200 [thread overview]
Message-ID: <32e39f46-68ef-c27a-d81a-510ca7e61c89@amazon.com> (raw)
In-Reply-To: <20190612153600.13073-2-samcacc@amazon.de>
On 12.06.19 17:35, Sam Caccavale wrote:
> This commit contains the minimal set of functionality to build
> afl-harness around arch/x86/emulate.c which allows exercising code
> in that source file, like x86_emulate_insn. Resolving the
> dependencies was done via GCC's -H flag by get_headers.py.
>
> CR: https://code.amazon.com/reviews/CR-8325546
I'm fairly sure that nobody on the LKML can access this page or even
remotely cares about it ;).
Also, your patches are missing an SoB line.
Alex
next prev parent reply other threads:[~2019-06-21 13:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-12 15:35 [v2, 0/4] x86 instruction emulator fuzzing Sam Caccavale
2019-06-12 15:35 ` [v2, 1/4] Build target for emulate.o as a userspace binary Sam Caccavale
2019-06-21 13:33 ` Alexander Graf [this message]
2019-06-12 15:35 ` [v2, 2/4] Emulate simple x86 instructions in userspace Sam Caccavale
2019-06-21 13:40 ` Alexander Graf
2019-06-12 15:35 ` [v2, 3/4] Demonstrating unit testing via simple-harness Sam Caccavale
2019-06-21 13:43 ` Alexander Graf
2019-06-12 15:36 ` [v2, 4/4] Added scripts for filtering, building, deploying Sam Caccavale
2019-06-21 13:50 ` Alexander Graf
2019-06-21 13:30 ` [v2, 0/4] x86 instruction emulator fuzzing Alexander Graf
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=32e39f46-68ef-c27a-d81a-510ca7e61c89@amazon.com \
--to=graf@amazon.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=anirudhkaushik@google.com \
--cc=bp@alien8.de \
--cc=dwmw@amazon.co.uk \
--cc=hpa@zytor.com \
--cc=karahmed@amazon.de \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=mpohlack@amazon.de \
--cc=nmanthey@amazon.de \
--cc=paullangton4@gmail.com \
--cc=pbonzini@redhat.com \
--cc=rkrcmar@redhat.com \
--cc=samcacc@amazon.de \
--cc=samcaccavale@gmail.com \
--cc=tglx@linutronix.de \
--cc=wipawel@amazon.de \
--cc=x86@kernel.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