All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: qemu-devel@nongnu.org
Cc: peter.maydell@linaro.org
Subject: [PATCH 6/7] docs: move gcov section at the end of testing.rst
Date: Thu, 30 Sep 2021 15:32:49 +0200	[thread overview]
Message-ID: <20210930133250.181156-7-pbonzini@redhat.com> (raw)
In-Reply-To: <20210930133250.181156-1-pbonzini@redhat.com>

gcov testing applies to all tests, not just make check.  Move it
out of the make check section.

Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
---
 docs/devel/testing.rst | 38 +++++++++++++++++++-------------------
 1 file changed, 19 insertions(+), 19 deletions(-)

diff --git a/docs/devel/testing.rst b/docs/devel/testing.rst
index 4a0abbf23d..200ce46c63 100644
--- a/docs/devel/testing.rst
+++ b/docs/devel/testing.rst
@@ -114,25 +114,6 @@ check-block
 are in the "auto" group).
 See the "QEMU iotests" section below for more information.
 
-GCC gcov support
-----------------
-
-``gcov`` is a GCC tool to analyze the testing coverage by
-instrumenting the tested code. To use it, configure QEMU with
-``--enable-gcov`` option and build. Then run ``make check`` as usual.
-
-If you want to gather coverage information on a single test the ``make
-clean-gcda`` target can be used to delete any existing coverage
-information before running a single test.
-
-You can generate a HTML coverage report by executing ``make
-coverage-html`` which will create
-``meson-logs/coveragereport/index.html``.
-
-Further analysis can be conducted by running the ``gcov`` command
-directly on the various .gcda output files. Please read the ``gcov``
-documentation for more information.
-
 QEMU iotests
 ============
 
@@ -1233,3 +1214,22 @@ exercise as many corner cases as possible. It is a useful test suite
 to run to exercise QEMU's linux-user code::
 
   https://linux-test-project.github.io/
+
+GCC gcov support
+================
+
+``gcov`` is a GCC tool to analyze the testing coverage by
+instrumenting the tested code. To use it, configure QEMU with
+``--enable-gcov`` option and build. Then run the tests as usual.
+
+If you want to gather coverage information on a single test the ``make
+clean-gcda`` target can be used to delete any existing coverage
+information before running a single test.
+
+You can generate a HTML coverage report by executing ``make
+coverage-html`` which will create
+``meson-logs/coveragereport/index.html``.
+
+Further analysis can be conducted by running the ``gcov`` command
+directly on the various .gcda output files. Please read the ``gcov``
+documentation for more information.
-- 
2.31.1




  parent reply	other threads:[~2021-09-30 13:56 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-30 13:32 [PATCH 0/7] Cleanup sectioning in a few doc files Paolo Bonzini
2021-09-30 13:32 ` [PATCH 1/7] docs: name included files ".rst.inc" Paolo Bonzini
2021-09-30 14:47   ` Peter Maydell
2021-09-30 14:51     ` Daniel P. Berrangé
2021-09-30 15:02       ` Peter Maydell
2021-10-01  5:14   ` Markus Armbruster
2021-10-01  9:20     ` Peter Maydell
2021-10-01 12:19     ` Paolo Bonzini
2021-09-30 13:32 ` [PATCH 2/7] docs: move notes inside the body of the document Paolo Bonzini
2021-09-30 15:15   ` Peter Maydell
2021-09-30 13:32 ` [PATCH 3/7] docs: put "make" information together in build-system.rst Paolo Bonzini
2021-09-30 15:16   ` Peter Maydell
2021-09-30 13:32 ` [PATCH 4/7] docs: reorganize qgraph.rst Paolo Bonzini
2021-09-30 13:32 ` [PATCH 5/7] docs: reorganize tcg-plugins.rst Paolo Bonzini
2021-09-30 13:32 ` Paolo Bonzini [this message]
2021-09-30 15:17   ` [PATCH 6/7] docs: move gcov section at the end of testing.rst Peter Maydell
2021-09-30 13:32 ` [PATCH 7/7] docs: reorganize testing.rst Paolo Bonzini

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=20210930133250.181156-7-pbonzini@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --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 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.