The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Alex Williamson <alex.williamson@redhat.com>
To: Russell King - ARM Linux <linux@armlinux.org.uk>
Cc: kvm@vger.kernel.org, eric.auger@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 8/9] amba: Export amba_bustype
Date: Mon, 19 Jun 2017 11:53:30 -0600	[thread overview]
Message-ID: <20170619115330.6f068dd4@w520.home> (raw)
In-Reply-To: <20170619173109.GI4902@n2100.armlinux.org.uk>

On Mon, 19 Jun 2017 18:31:10 +0100
Russell King - ARM Linux <linux@armlinux.org.uk> wrote:

> This patch on its own doesn't make much sense to me... any chance of
> seeing the full series please?

Hi Russell,

Please find it here:

https://lkml.org/lkml/2017/6/19/808

Patches 7 and 9:

https://lkml.org/lkml/2017/6/19/813
https://lkml.org/lkml/2017/6/19/812

Are particularly relevant.  The gist of it is that we want to get to
the driver_override field of the device in order to force a no-match
for a driver bind when we're in a situation where binding to a host
driver could compromise the system integrity (user owned devices and
host owned devices in the same iommu group).  driver_override is handled
in a common way, but is not part of struct device, it's part of the
containing structure, so we identify the bustype and therefore device
container to get to the override.  The bustype is typically exported
and some bus drivers like PCI even offer convenient helpers like
dev_is_pci() to facilitate this sort of matching.  Thanks,

Alex

> On Mon, Jun 19, 2017 at 11:15:29AM -0600, Alex Williamson wrote:
> > This allows modules to match struct device.bus to amba_bustype for the
> > purpose of casting the device to an amba_device with to_amba_device().
> > 
> > Signed-off-by: Alex Williamson <alex.williamson@redhat.com>
> > Reported-by: Eric Auger <eric.auger@redhat.com>
> > Cc: Russell King <linux@armlinux.org.uk>
> > ---
> >  drivers/amba/bus.c |    1 +
> >  1 file changed, 1 insertion(+)
> > 
> > diff --git a/drivers/amba/bus.c b/drivers/amba/bus.c
> > index a56fa2a1e9aa..4e118cd3ddf3 100644
> > --- a/drivers/amba/bus.c
> > +++ b/drivers/amba/bus.c
> > @@ -197,6 +197,7 @@ struct bus_type amba_bustype = {
> >  	.uevent		= amba_uevent,
> >  	.pm		= &amba_pm,
> >  };
> > +EXPORT_SYMBOL_GPL(amba_bustype);
> >  
> >  static int __init amba_init(void)
> >  {
> >   
> 

  reply	other threads:[~2017-06-19 17:53 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-19 17:14 [PATCH v2 0/9] vfio: Fix release ordering races and use driver_override Alex Williamson
2017-06-19 17:14 ` [PATCH v2 1/9] vfio: Fix group release deadlock Alex Williamson
2017-06-19 17:14 ` [PATCH v2 2/9] kvm-vfio: Decouple only when we match a group Alex Williamson
2017-06-20  2:34   ` Alexey Kardashevskiy
2017-06-20  2:42     ` Alex Williamson
2017-06-19 17:14 ` [PATCH v2 3/9] vfio: New external user group/file match Alex Williamson
2017-06-20  5:01   ` kbuild test robot
2017-06-19 17:14 ` [PATCH v2 4/9] iommu: Add driver-not-bound notification Alex Williamson
2017-06-19 17:15 ` [PATCH v2 5/9] vfio: Create interface for vfio bus drivers to register Alex Williamson
2017-06-19 17:15 ` [PATCH v2 6/9] vfio: Register pci, platform, amba, and mdev bus drivers Alex Williamson
2017-06-19 17:15 ` [PATCH v2 7/9] vfio: Use driver_override to avert binding to compromising drivers Alex Williamson
2017-06-19 17:15 ` [PATCH v2 8/9] amba: Export amba_bustype Alex Williamson
2017-06-19 17:31   ` Russell King - ARM Linux
2017-06-19 17:53     ` Alex Williamson [this message]
2017-06-19 17:15 ` [PATCH v2 9/9] vfio: Add AMBA driver_override support Alex Williamson

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=20170619115330.6f068dd4@w520.home \
    --to=alex.williamson@redhat.com \
    --cc=eric.auger@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    /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