qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Laurent Vivier <laurent@vivier.eu>
To: Aleksandar Markovic <aleksandar.markovic@rt-rk.com>,
	qemu-devel@nongnu.org
Cc: amarkovic@wavecomp.com
Subject: Re: [PATCH 10/12] configure: Detect kcov support and introduce CONFIG_KCOV
Date: Wed, 22 Jan 2020 15:10:38 +0100	[thread overview]
Message-ID: <81c1db40-e322-fb08-728f-bffc0fc4ce99@vivier.eu> (raw)
In-Reply-To: <1579214991-19602-11-git-send-email-aleksandar.markovic@rt-rk.com>

Le 16/01/2020 à 23:49, Aleksandar Markovic a écrit :
> From: Aleksandar Markovic <amarkovic@wavecomp.com>
> 
> kcov is kernel code coverage tracing tool. It requires kernel 4.4+
> compiled with certain kernel options.
> 
> This patch checks if kcov header "sys/kcov.h" is present on build
> machine, and stores the result in variable CONFIG_KCOV, meant to
> be used in linux-user code related to the support for three ioctls
> that were introduced at the same time as the mentioned header
> (their definition was a part of the first version of that header).
> 
> Signed-off-by: Aleksandar Markovic <amarkovic@wavecomp.com>
> ---
>  configure | 9 +++++++++
>  1 file changed, 9 insertions(+)
> 
> diff --git a/configure b/configure
> index 940bf9e..57e6eba 100755
> --- a/configure
> +++ b/configure
> @@ -4752,6 +4752,12 @@ if compile_prog "" "" ; then
>    syncfs=yes
>  fi
>  
> +# check for kcov support (kernel must be 4.4+, compiled with certain options)
> +kcov=no
> +if check_include sys/kcov.h ; then
> +    kcov=yes
> +fi
> +
>  # Check we have a new enough version of sphinx-build
>  has_sphinx_build() {
>      # This is a bit awkward but works: create a trivial document and
> @@ -6874,6 +6880,9 @@ fi
>  if test "$syncfs" = "yes" ; then
>    echo "CONFIG_SYNCFS=y" >> $config_host_mak
>  fi
> +if test "$kcov" = "yes" ; then
> +  echo "CONFIG_KCOV=y" >> $config_host_mak
> +fi
>  if test "$inotify" = "yes" ; then
>    echo "CONFIG_INOTIFY=y" >> $config_host_mak
>  fi
>

Reviewed-by: Laurent Vivier <laurent@vivier.eu>



  reply	other threads:[~2020-01-22 14:11 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-16 22:49 [PATCH 00/12] linux-user: Add support for fs, fd,and kcov ioctls Aleksandar Markovic
2020-01-16 22:49 ` [PATCH 01/12] linux-user: Add support for FS_IOC_<GET|SET>VERSION ioctls Aleksandar Markovic
2020-01-22 14:04   ` Laurent Vivier
2020-01-16 22:49 ` [PATCH 02/12] linux-user: Add support for FS_IOC32_<GET|SET>FLAGS ioctls Aleksandar Markovic
2020-01-22 14:06   ` Laurent Vivier
2020-01-16 22:49 ` [PATCH 03/12] linux-user: Add support for FS_IOC32_<GET|SET>VERSION ioctls Aleksandar Markovic
2020-01-22 14:07   ` Laurent Vivier
2020-01-16 22:49 ` [PATCH 04/12] linux-user: Add support for FS_IOC_FS<GET|SET>XATTR ioctls Aleksandar Markovic
2020-01-16 22:49 ` [PATCH 05/12] linux-user: Add support for FITRIM ioctl Aleksandar Markovic
2020-01-16 22:49 ` [PATCH 06/12] linux-user: Add support for FIFREEZE and FITHAW ioctls Aleksandar Markovic
2020-01-16 22:49 ` [PATCH 07/12] linux-user: Add support for FD<SETEMSGTRESH|SETMAXERRS|GETMAXERRS> ioctls Aleksandar Markovic
2020-01-22 14:13   ` Laurent Vivier
2020-01-16 22:49 ` [PATCH 08/12] linux-user: Add support for FDFMT<BEG|TRK|END> ioctls Aleksandar Markovic
2020-01-22 14:13   ` Laurent Vivier
2020-01-16 22:49 ` [PATCH 09/12] linux-user: Add support for FDGETFDCSTAT ioctl Aleksandar Markovic
2020-01-16 22:49 ` [PATCH 10/12] configure: Detect kcov support and introduce CONFIG_KCOV Aleksandar Markovic
2020-01-22 14:10   ` Laurent Vivier [this message]
2020-01-22 14:16   ` Laurent Vivier
2020-01-16 22:49 ` [PATCH 11/12] linux-user: Add support for KCOV_<ENABLE|DISABLE> ioctls Aleksandar Markovic
2020-01-22 14:16   ` Laurent Vivier
2020-01-16 22:49 ` [PATCH 12/12] linux-user: Add support for KCOV_INIT_TRACE ioctl Aleksandar Markovic
2020-01-22 14:16   ` Laurent Vivier

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=81c1db40-e322-fb08-728f-bffc0fc4ce99@vivier.eu \
    --to=laurent@vivier.eu \
    --cc=aleksandar.markovic@rt-rk.com \
    --cc=amarkovic@wavecomp.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).