qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Daniel P. Berrangé" <berrange@redhat.com>
To: "Philippe Mathieu-Daudé" <philmd@redhat.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>, qemu-devel <qemu-devel@nongnu.org>
Subject: Re: How to run crypto benchmarks tests?
Date: Wed, 20 Jan 2021 13:06:24 +0000	[thread overview]
Message-ID: <20210120130624.GI3015589@redhat.com> (raw)
In-Reply-To: <c72a38ac-d164-9357-4eda-2334c496c555@redhat.com>

On Wed, Jan 20, 2021 at 01:50:48PM +0100, Philippe Mathieu-Daudé wrote:
> Hi,
> 
> Using the following "build tools and doc" config:
> 
> ../configure --disable-system --disable-user
>                                  ...
>                      TLS priority: "NORMAL"
>                    GNUTLS support: YES
>                         libgcrypt: NO
>                            nettle: YES
>                               XTS: YES
>                          libtasn1: YES
>                               PAM: YES
>                                  ...
> 
> $ make check-help
> ...
>  make check-speed          Run qobject speed tests
> ...
> Test targets:
>   check                          - Run all tests (check-help for details)
>   bench                          - Run all benchmarks
>   docker                         - Help about targets running tests
> inside containers
> 
> $ make check-speed
> make: *** No rule to make target 'bench-speed', needed by 'check-speed'.
>  Stop.
> $ make bench-speed
> make: *** No rule to make target 'bench-speed'.  Stop.
> $ make check-bench
> make: *** No rule to make target 'check-bench'.  Stop.
> $ make bench
> make: Nothing to be done for 'bench'.
> 
> I want to run these tests:
> 
> $ ls -1 tests/test-crypto-*c
> tests/test-crypto-afsplit.c
> tests/test-crypto-block.c
> tests/test-crypto-cipher.c
> tests/test-crypto-hash.c
> tests/test-crypto-hmac.c
> tests/test-crypto-ivgen.c
> tests/test-crypto-pbkdf.c
> tests/test-crypto-secret.c
> tests/test-crypto-tlscredsx509.c
> tests/test-crypto-tlssession.c
> tests/test-crypto-xts.c

These aren't benchmarks - they're regular unit tests - eg make check-unit 

The benchmarks are tests/benchmark-crypto*.c

Either way, all of this is surrounded by 'if have_block' in tests/meson.build
which should apply if you have tools enabled or system emulators enabled.


Regards,
Daniel
-- 
|: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org         -o-            https://fstop138.berrange.com :|
|: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|



  reply	other threads:[~2021-01-20 13:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-20 12:50 How to run crypto benchmarks tests? Philippe Mathieu-Daudé
2021-01-20 13:06 ` Daniel P. Berrangé [this message]
2021-01-20 13:58   ` Philippe Mathieu-Daudé
2021-01-20 14:23     ` Philippe Mathieu-Daudé

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=20210120130624.GI3015589@redhat.com \
    --to=berrange@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=philmd@redhat.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).