linux-kernel - Re: [PATCH v2 0/6] UIO driver for APM X-Gene QMTM

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 9 Oct 2014 18:00:26 +0530
From:	Ankit Jindal <ankit.jindal@...aro.org>
To:	Richard Weinberger <richard.weinberger@...il.com>
Cc:	Arnd Bergmann <arnd@...db.de>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"Hans J. Koch" <hjk@...sjkoch.de>,
	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	"patches@....com" <patches@....com>,
	"linux-arm-kernel@...ts.infradead.org" 
	<linux-arm-kernel@...ts.infradead.org>,
	Rob Herring <robh+dt@...nel.org>,
	Tushar Jagad <tushar.jagad@...aro.org>,
	Russell King - ARM Linux <linux@....linux.org.uk>,
	"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>
Subject: Re: [PATCH v2 0/6] UIO driver for APM X-Gene QMTM

On 9 October 2014 17:52, Richard Weinberger
<richard.weinberger@...il.com> wrote:
> On Thu, Oct 9, 2014 at 2:17 PM, Ankit Jindal <ankit.jindal@...aro.org> wrote:
>> On 9 October 2014 17:36, Arnd Bergmann <arnd@...db.de> wrote:
>>> On Thursday 09 October 2014 14:14:33 Ankit Jindal wrote:
>>>> On 30 September 2014 09:56, Ankit Jindal <ankit.jindal@...aro.org> wrote:
>>>> > This patchset enables user space access to APM X-Gene QMTM
>>>> > using UIO framework.
>>>> >
>>>> > The patchset also introduces new type UIO_MEM_PHYS_CACHE
>>>> > for mem regions because APM X-Gene QMTM device supports
>>>> > cache coherency with CPU caches.
>>>>
>>>
>>> I haven't been able to review the patch in detail yet, but I have
>>> a very high-level question: how do you decide which driver to use?
>>>
>>> I understand that the normal use case is for the QMTM to be used by
>>> the kernel directly rather than being exported to user space, and
>>> that the network driver will just use it if it is there.
>>
>> This UIO driver will be disabled by default. When this driver is
>> enabled, the other dependent drivers need to be removed from the
>> config.
>
> And if the user forgets or creates an allmod/yesconfig we have
> undefined behavior?

When the conflicting drivers will be added to kernel, necessary
options (depends on not) needs to be added to the Kconfig.

>
> --
> Thanks,
> //richard

Thanks,
Ankit
--
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/