From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757524Ab0CaXHS (ORCPT ); Wed, 31 Mar 2010 19:07:18 -0400 Received: from mx1.redhat.com ([209.132.183.28]:56652 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756138Ab0CaXHQ (ORCPT ); Wed, 31 Mar 2010 19:07:16 -0400 Organization: Red Hat UK Ltd. Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod Street, Windsor, Berkshire, SI4 1TE, United Kingdom. Registered in England and Wales under Company Registration No. 3798903 From: David Howells In-Reply-To: <201003311554.38473.vapier@gentoo.org> References: <201003311554.38473.vapier@gentoo.org> <1268151081-28307-1-git-send-email-vapier@gentoo.org> <1261413866-30634-1-git-send-email-vapier@gentoo.org> <14998.1270055484@redhat.com> To: Mike Frysinger Cc: dhowells@redhat.com, uclinux-dev@uclinux.org, David McCullough , Greg Ungerer , Paul Mundt , linux-kernel@vger.kernel.org, uclinux-dist-devel@blackfin.uclinux.org Subject: Re: [PATCH v2] NOMMU: implement vmap/vunmap with kmalloc Date: Thu, 01 Apr 2010 00:06:53 +0100 Message-ID: <19891.1270076813@redhat.com> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Mike Frysinger wrote: > how about putting this implementation into like vmap_nommu() and only > rewriting vmap() to vmap_nommu() when we know it's safe ? such as this > firmware case ? Well, I'd argue it's _not_ vmap(), so it doesn't really make sense to call it such. Perhaps some better name? Perhaps vcopy()? David