MIME-Version: 1.0
In-Reply-To: <20151210114005.GF19496@dhcp22.suse.cz>
References: <5667128B.3080704@sigmadesigns.com>
	<20151209135544.GE30907@dhcp22.suse.cz>
	<566835B6.9010605@sigmadesigns.com>
	<20151209143207.GF30907@dhcp22.suse.cz>
	<56684062.9090505@sigmadesigns.com>
	<20151209151254.GH30907@dhcp22.suse.cz>
	<56684A59.7030605@sigmadesigns.com>
	<20151210114005.GF19496@dhcp22.suse.cz>
Date: Thu, 10 Dec 2015 13:04:48 +0100
Message-ID: <CAFLxGvy7z5zo1_9QfYZj1AMLN-+iVnErir_U7=5=y2bRFKHhNQ@mail.gmail.com>
Subject: Re: m(un)map kmalloc buffers to userspace
From: Richard Weinberger <richard.weinberger@gmail.com>
To: Michal Hocko <mhocko@kernel.org>
Cc: Sebastian Frias <sebastian_frias@sigmadesigns.com>,
        Marc Gonzalez <marc_gonzalez@sigmadesigns.com>,
        linux-mm <linux-mm@kvack.org>, LKML <linux-kernel@vger.kernel.org>
Content-Type: text/plain; charset=UTF-8
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1036
Lines: 26

On Thu, Dec 10, 2015 at 12:40 PM, Michal Hocko <mhocko@kernel.org> wrote:
> On Wed 09-12-15 16:35:53, Sebastian Frias wrote:
> [...]
>> We've seen that drivers/media/pci/zoran/zoran_driver.c for example seems to
>> be doing as us kmalloc+remap_pfn_range,
>
> This driver is broken - I will post a patch.
>
>> is there any guarantee (or at least an advised heuristic) to determine
>> if a driver is "current" (ie: uses the latest APIs and works)?
>
> OK, it seems I was overly optimistic when directing you to existing
> drivers. Sorry about that I wasn't aware you could find such a terrible
> code there. Please refer to Linux Device Drivers book which should give
> you a much better lead (e.g. http://www.makelinux.net/ldd3/chp-15-sect-2)

Also consider using UIO.

-- 
Thanks,
//richard
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/