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 19:38:25 +0000 [thread overview]
Message-ID: <20201125193825.GM3222@work-vm> (raw)
In-Reply-To: <6a61ce43-055b-65bc-29e0-55edea534f28@nvidia.com>
* Kirti Wankhede (kwankhede@nvidia.com) wrote:
>
>
> On 11/26/2020 12:33 AM, Dr. David Alan Gilbert wrote:
> > * Kirti Wankhede (kwankhede@nvidia.com) wrote:
> > >
> > >
> > > On 11/25/2020 3:00 PM, Dr. David Alan Gilbert wrote:
> > > > * 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.
> > > >
> > >
> > > Still function prototype for populate_vfio_info() and its stub has to be
> > > placed in some header file.
> >
> > Which header file isn't that important;
>
> Any recommendation which header file to use?
I guess ./include/hw/vfio/vfio.h or one of the other vfio headers that
works even if vfio isn't configured?
Dave
> Thanks,
> Kirti
>
> > and the stub goes in a file in
> > stubs/
> >
> > > Earlier I used CONFIG_LINUX instead of CONFIG_VFIO which works here. Should
> > > I change it back to CONFIG_LINUX?
> >
> > No.
> >
> > > I'm not very much aware of meson build system, I tested by configuring
> > > specific target, but I think by default if target build is not specified
> > > during configuration, it builds for multiple target that's where this build
> > > is failing. Any help on how to fix it would be helpful.
> >
> > With my suggestion you don't have to do anything clever to meson
> > (which I don't know much about either).
> >
> > Dave
> >
> > > Thanks,
> > > Kirti
> > >
> > > > 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
prev parent reply other threads:[~2020-11-25 19:40 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
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 [this message]
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=20201125193825.GM3222@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).