qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: Kirti Wankhede <kwankhede@nvidia.com>
Cc: alex.williamson@redhat.com, cjia@nvidia.com,
	qemu-devel@nongnu.org, quintela@redhat.com
Subject: Re: [PATCH 1/1] Fix to show vfio migration stat in migration status
Date: Wed, 25 Nov 2020 09:30:36 +0000	[thread overview]
Message-ID: <20201125093036.GA3222@work-vm> (raw)
In-Reply-To: <1605731327-23533-1-git-send-email-kwankhede@nvidia.com>

* Kirti Wankhede (kwankhede@nvidia.com) wrote:
> Header file where CONFIG_VFIO is defined is not included in migration.c
> file. Include config devices header file in migration.c.
> 
> Fixes: 3710586caa5d ("qapi: Add VFIO devices migration stats in Migration
> stats")
> 
> Signed-off-by: Kirti Wankhede <kwankhede@nvidia.com>

Given it's got build problems; I suggest actually something cleaner
would be to swing populate_vfio_info into one of the vfio specific
files, add a stubs/ entry somewhere and then migration.c doesn't need
to include the device or header stuff.

Dave

> ---
>  meson.build           | 1 +
>  migration/migration.c | 1 +
>  2 files changed, 2 insertions(+)
> 
> diff --git a/meson.build b/meson.build
> index 7ddf983ff7f5..24526499cfb5 100644
> --- a/meson.build
> +++ b/meson.build
> @@ -1713,6 +1713,7 @@ common_ss.add_all(when: 'CONFIG_USER_ONLY', if_true: user_ss)
>  
>  common_all = common_ss.apply(config_all, strict: false)
>  common_all = static_library('common',
> +                            c_args:'-DCONFIG_DEVICES="@0@-config-devices.h"'.format(target) ,
>                              build_by_default: false,
>                              sources: common_all.sources() + genh,
>                              dependencies: common_all.dependencies(),
> diff --git a/migration/migration.c b/migration/migration.c
> index 87a9b59f83f4..650efb81daad 100644
> --- a/migration/migration.c
> +++ b/migration/migration.c
> @@ -57,6 +57,7 @@
>  #include "qemu/queue.h"
>  #include "multifd.h"
>  
> +#include CONFIG_DEVICES
>  #ifdef CONFIG_VFIO
>  #include "hw/vfio/vfio-common.h"
>  #endif
> -- 
> 2.7.0
> 
-- 
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK



  parent reply	other threads:[~2020-11-25  9:32 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-18 20:28 [PATCH 1/1] Fix to show vfio migration stat in migration status Kirti Wankhede
2020-11-23 16:33 ` Alex Williamson
2020-11-23 18:18   ` Kirti Wankhede
2020-11-23 18:39     ` Alex Williamson
2020-11-25  9:30 ` Dr. David Alan Gilbert [this message]
2020-11-25 18:52   ` Kirti Wankhede
2020-11-25 19:03     ` Dr. David Alan Gilbert
2020-11-25 19:35       ` Kirti Wankhede
2020-11-25 19:38         ` Dr. David Alan Gilbert

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=20201125093036.GA3222@work-vm \
    --to=dgilbert@redhat.com \
    --cc=alex.williamson@redhat.com \
    --cc=cjia@nvidia.com \
    --cc=kwankhede@nvidia.com \
    --cc=qemu-devel@nongnu.org \
    --cc=quintela@redhat.com \
    /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).