[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5613E93B.6010903@cloudius-systems.com>
Date: Tue, 6 Oct 2015 18:31:07 +0300
From: Vlad Zolotarov <vladz@...udius-systems.com>
To: "Michael S. Tsirkin" <mst@...hat.com>,
Gleb Natapov <gleb@...lladb.com>
Cc: Greg KH <gregkh@...uxfoundation.org>,
Bruce Richardson <bruce.richardson@...el.com>,
linux-kernel@...r.kernel.org, hjk@...sjkoch.de,
avi@...udius-systems.com, corbet@....net,
alexander.duyck@...il.com, gleb@...udius-systems.com,
stephen@...workplumber.org
Subject: Re: [PATCH v3 1/3] uio: add ioctl support
On 10/06/15 18:19, Michael S. Tsirkin wrote:
> On Tue, Oct 06, 2015 at 05:30:31PM +0300, Gleb Natapov wrote:
>> On Tue, Oct 06, 2015 at 05:19:22PM +0300, Michael S. Tsirkin wrote:
>>> On Tue, Oct 06, 2015 at 11:33:56AM +0300, Vlad Zolotarov wrote:
>>>> the solution u propose should be a matter of a separate patch and is
>>>> obviously orthogonal to this series.
>>> Doesn't work this way, sorry. You want a patch enabling MSI merged,
>>> you need to secure the MSI configuration.
>>>
>> MSI can be enabled right now without the patch by writing directly into
>> PCI bar.
> By poking at config registers in sysfs? We can block this, or we
> can log this, pretty easily. We don't ATM but it's not hard to do.
>
>> The only thing this patch adds is forwarding the interrupt to
>> an eventfd.
> This one just adds a bunch of ioctls. The next ones do
> more than you describe.
This one adds zero ioctls and the next one does exactly what Gleb
describes.
>
>> --
>> Gleb.
--
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