From: Thomas Huth <thuth@redhat.com>
To: Kenneth Adam Miller <kennethadammiller@gmail.com>,
QEMU Developers <qemu-devel@nongnu.org>
Cc: "Alex Bennée" <alex.bennee@linaro.org>
Subject: Re: TCG development tools?
Date: Mon, 20 Jun 2022 09:10:24 +0200 [thread overview]
Message-ID: <89d6b974-667e-d331-7f55-0ab71a117e13@redhat.com> (raw)
In-Reply-To: <CAK7rcp8M=B0PmvZ4FnXNAnSh5TuvxNA4aKXJ8+JF06XogMmsEg@mail.gmail.com>
On 19/06/2022 05.34, Kenneth Adam Miller wrote:
> Hello all,
>
> Suppose I am wanting to implement and test for the TCG. Is there any set of
> interactive binaries or other things that I could use to work with it? Could
> I open a shell to it? Perhaps feed it specific byte sequences for tests to
> ensure correct operation? Are there a canonical set of unit tests that
> exercise the TCG that each architecture implements?
We've got a bunch of TCG-related tests in the tests/tcg/ , so I suggest you
start with these.
HTH,
Thomas
next prev parent reply other threads:[~2022-06-20 7:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-19 3:34 TCG development tools? Kenneth Adam Miller
2022-06-20 7:10 ` Thomas Huth [this message]
2022-06-20 15:17 ` Alex Bennée
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=89d6b974-667e-d331-7f55-0ab71a117e13@redhat.com \
--to=thuth@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=kennethadammiller@gmail.com \
--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).