dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Alex Williamson <alex.williamson@redhat.com>
To: Zhenyu Wang <zhenyuw@linux.intel.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	Jike Song <jike.song@intel.com>,
	Daniel Vetter <daniel.vetter@ffwll.ch>,
	Intel Graphics <intel-gfx@lists.freedesktop.org>,
	linux-kernel@vger.kernel.org,
	DRI <dri-devel@lists.freedesktop.org>,
	linux-next@vger.kernel.org
Subject: Re: linux-next: build failure after merge of the drm-intel-fixes tree
Date: Mon, 2 Jan 2017 21:48:57 -0700	[thread overview]
Message-ID: <20170102214857.6ad8f2eb@t450s.home> (raw)
In-Reply-To: <20170103025929.35gp5n27uc7iszra@zhen-hp.sh.intel.com>

On Tue, 3 Jan 2017 10:59:29 +0800
Zhenyu Wang <zhenyuw@linux.intel.com> wrote:

> On 2017.01.03 10:42:39 +1100, Stephen Rothwell wrote:
> > Hi all,
> > 
> > After merging the drm-intel-fixes tree, today's linux-next build (x86_64
> > allmodconfig) failed like this:
> > 
> > drivers/gpu/drm/i915/gvt/kvmgt.c: In function 'intel_vgpu_open':
> > drivers/gpu/drm/i915/gvt/kvmgt.c:511:32: error: dereferencing pointer to incomplete type 'struct mdev_device'
> >   vfio_unregister_notifier(&mdev->dev, VFIO_GROUP_NOTIFY,
> >                                 ^   
> > 
> > Caused by commit
> > 
> >   99e3123e3d72 ("vfio-mdev: Make mdev_device private and abstract interfaces")
> > 
> > from the vfio-fixes tree interacting with commit
> > 
> >   364fb6b789ff ("drm/i915/gvt/kvmgt: prevent double-release of vgpu")
> > 
> > from the drm-intel-fixes tree.  
> 
> Alex, I liked to have kvmgt related mdev interface change be merged through
> vfio tree, but wasn't awared one of Jike's fix had conflict. Could you apply
> below fix in your tree? I think in general for possible interface change in
> future we still need a pull request for i915 to resolve dependence earlier.

Hi Zhenyu,

Hopefully this abstraction will help to isolate vendor drivers from
mdev API changes in the future.  I can certainly roll this patch into
the original to maintain bisectability.  I want to get these changes in
for rc3, will a pull request for the i915 changes be sent this week?
Thanks for spotting and fixing this, Stephen.  Thanks,

Alex

> > I applied this merge fix patch:
> > 
> > From: Stephen Rothwell <sfr@canb.auug.org.au>
> > Date: Tue, 3 Jan 2017 10:38:48 +1100
> > Subject: [PATCH] vfio-mdev: fixup for "Make mdev_device private and abstract interfaces"
> > 
> > Signed-off-by: Stephen Rothwell <sfr@canb.auug.org.au>
> > ---
> >  drivers/gpu/drm/i915/gvt/kvmgt.c | 2 +-
> >  1 file changed, 1 insertion(+), 1 deletion(-)
> > 
> > diff --git a/drivers/gpu/drm/i915/gvt/kvmgt.c b/drivers/gpu/drm/i915/gvt/kvmgt.c
> > index c24b665e007b..faaae07ae487 100644
> > --- a/drivers/gpu/drm/i915/gvt/kvmgt.c
> > +++ b/drivers/gpu/drm/i915/gvt/kvmgt.c
> > @@ -508,7 +508,7 @@ static int intel_vgpu_open(struct mdev_device *mdev)
> >  	return ret;
> >  
> >  undo_group:
> > -	vfio_unregister_notifier(&mdev->dev, VFIO_GROUP_NOTIFY,
> > +	vfio_unregister_notifier(mdev_dev(mdev), VFIO_GROUP_NOTIFY,
> >  					&vgpu->vdev.group_notifier);
> >  
> >  undo_iommu:
> > -- 
> > 2.10.2
> > 
> > -- 
> > Cheers,
> > Stephen Rothwell  
> 

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2017-01-03  4:48 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-02 23:42 linux-next: build failure after merge of the drm-intel-fixes tree Stephen Rothwell
2017-01-03  2:59 ` Zhenyu Wang
2017-01-03  4:07   ` Stephen Rothwell
2017-01-03  4:48   ` Alex Williamson [this message]
2017-01-03  9:23     ` Zhenyu Wang
2017-01-03 13:25       ` Jani Nikula
2017-01-03 20:37         ` Alex Williamson
2017-01-04  9:07           ` Daniel Vetter
  -- strict thread matches above, loose matches on Subject: below --
2022-07-13 12:14 Stephen Rothwell
2022-01-31 22:27 Stephen Rothwell
2020-11-03 22:37 Stephen Rothwell
2020-11-04  0:25 ` Rodrigo Vivi
2020-06-15 23:39 Stephen Rothwell
2020-06-16  9:22 ` Joonas Lahtinen
2020-05-28 22:30 Stephen Rothwell
2020-01-20 21:34 Stephen Rothwell
2020-01-21  7:13 ` Joonas Lahtinen
2019-01-29 22:39 Stephen Rothwell
2019-01-29 22:53 ` Lucas De Marchi
2019-01-30  8:22   ` Jani Nikula
2018-05-29  9:26 Stephen Rothwell
2018-05-29 11:45 ` Joonas Lahtinen
2017-10-10  7:03 Mark Brown
2017-10-11  8:51 ` Mark Brown
2014-06-06  2:03 Stephen Rothwell
2014-06-06  6:45 ` Daniel Vetter

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=20170102214857.6ad8f2eb@t450s.home \
    --to=alex.williamson@redhat.com \
    --cc=daniel.vetter@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jike.song@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=zhenyuw@linux.intel.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).