From: Avi Kivity <avi@redhat.com>
To: Marcelo Tosatti <mtosatti@redhat.com>
Cc: lmr@redhat.com, kvm@vger.kernel.org
Subject: Re: [PATCH 3/3] KVM: x86 emulator: fuzz tester
Date: Mon, 29 Aug 2011 15:42:41 +0300 [thread overview]
Message-ID: <4E5B8941.9040807@redhat.com> (raw)
In-Reply-To: <4E569CD4.6010101@redhat.com>
On 08/25/2011 10:04 PM, Avi Kivity wrote:
>
>> Also fuzzing from an actual guest is useful to test the real backend
>> functions. What problem did you encounter? The new testsuite scheme
>> seems a good fit for that (with the exception of being locked to 32-bit
>> mode).
>
> Mostly that I forgot it exists. Other issues are that it's harder to
> force random values through it - though I could allocate a couple GB
> and fill it with random values. We also lose the ability to test
> inputs to callbacks (not that I do much of that here).
Further issues would be:
- much slower - heavyweight exit on every insn, KVM_SET_SREGS, etc.
- need to set up GDT/LDT, I guess we can do this once and fill it with
random entries
- much more care in setting up registers so we can get a context that runs
- need to figure out where %rip EA is so we can put insn there, hope it
doesn't conflict with other code
So it will probably work, but the result will be of lower quality.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2011-08-29 12:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-22 13:41 [PATCH 0/3] Emulator fuzz tester Avi Kivity
2011-08-22 13:41 ` [PATCH 1/3] KVM: x86 emulator: make prototype of ->write_std() the same as ->write_emulated Avi Kivity
2011-08-22 13:41 ` [PATCH 2/3] KVM: x86 emulator: export main interface Avi Kivity
2011-08-22 13:41 ` [PATCH 3/3] KVM: x86 emulator: fuzz tester Avi Kivity
2011-08-25 16:27 ` Marcelo Tosatti
2011-08-25 19:04 ` Avi Kivity
2011-08-29 12:42 ` Avi Kivity [this message]
2011-08-25 22:17 ` Lucas Meneghel Rodrigues
2011-08-29 12:01 ` Avi Kivity
2011-08-25 19:07 ` [PATCH 0/3] Emulator " Lucas Meneghel Rodrigues
2011-08-26 0:11 ` Lucas Meneghel Rodrigues
2011-08-29 12:05 ` Avi Kivity
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=4E5B8941.9040807@redhat.com \
--to=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=lmr@redhat.com \
--cc=mtosatti@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox