All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Andreas Färber" <afaerber@suse.de>
To: Peter Maydell <peter.maydell@linaro.org>, qemu-devel@nongnu.org
Cc: patches@linaro.org, Richard Henderson <rth@twiddle.net>
Subject: Re: [Qemu-devel] [RFC] translate-all.c: add hack for coverage testing
Date: Wed, 12 Feb 2014 16:25:39 +0100	[thread overview]
Message-ID: <52FB9273.5080907@suse.de> (raw)
In-Reply-To: <1392132687-18664-1-git-send-email-peter.maydell@linaro.org>

Am 11.02.2014 16:31, schrieb Peter Maydell:
> Actually this barely even rises to the level of an RFC, but
> since I'm not entirely sure how or if it might be possible to
> turn this into upstreamable code I thought I might as well
> send it out as-is in case anybody else finds it useful.
> 
> The basic idea is that you build the linux-user binary and
> run it on something (anything). Instead of actually running
> code we instead just loop round feeding every possible
> instruction pattern to the decoder. This lets us catch:
>  * "can't happen" assertions in the wrong place
>  * TCG temp leaks
>  * insns which generate too many TCG ops
> 
> Obvious deficiencies here:
>  * no UI for specifying that you want to test a smaller
>    part of the instruction space
>  * an assumption that instructions are fixed-length 32 bits
>  * cheesily hardwired in

Wasn't there a previous proposal to do an accel=tcgtest? That would be
the way I'd expect such test frameworks to be dynamically invoked.

Regards,
Andreas

-- 
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg

      reply	other threads:[~2014-02-12 15:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-11 15:31 [Qemu-devel] [RFC] translate-all.c: add hack for coverage testing Peter Maydell
2014-02-12 15:25 ` Andreas Färber [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=52FB9273.5080907@suse.de \
    --to=afaerber@suse.de \
    --cc=patches@linaro.org \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=rth@twiddle.net \
    /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.