[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1382983205.3410.6.camel@snotra.buserror.net>
Date: Mon, 28 Oct 2013 13:00:05 -0500
From: Scott Wood <scottwood@...escale.com>
To: Alex Williamson <alex.williamson@...hat.com>
CC: Kim Phillips <kim.phillips@...aro.org>,
Bhushan Bharat <R65777@...escale.com>,
Wood Scott <B07421@...escale.com>,
Yoder Stuart <B08248@...escale.com>,
<christoffer.dall@...aro.org>, <linux-kernel@...r.kernel.org>,
<a.motakis@...tualopensystems.com>, <agraf@...e.de>,
Sethi Varun <B16395@...escale.com>, <peter.maydell@...aro.org>,
<santosh.shukla@...aro.org>, <kvm@...r.kernel.org>,
<gregkh@...uxfoundation.org>
Subject: Re: [PATCH 3/4] VFIO: pci: amend vfio-pci for explicit binding via
sysfs only
On Mon, 2013-10-28 at 11:47 -0600, Alex Williamson wrote:
> On Fri, 2013-10-11 at 01:27 -0500, Kim Phillips wrote:
> > Force the vfio-pci driver to only be bound explicitly via sysfs to avoid
> > conflics with other drivers in the event of a hotplug.
>
> We can't break userspace, so we can't disable the current method of
> binding devices to vfio-pci. We can add a new method and perhaps
> deprecate the existing mechanism to be removed at some point in the
> future. Thanks,
I thought the existing method involved using sysfs bind, and this was
just eliminating a race. How does the bind get triggered currently?
-Scott
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists