Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S262549AbUKRBXG (ORCPT ); Wed, 17 Nov 2004 20:23:06 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S262661AbUKRBXF (ORCPT ); Wed, 17 Nov 2004 20:23:05 -0500 Received: from e31.co.us.ibm.com ([32.97.110.129]:49043 "EHLO e31.co.us.ibm.com") by vger.kernel.org with ESMTP id S262549AbUKRBUf (ORCPT ); Wed, 17 Nov 2004 20:20:35 -0500 Subject: Re: [patch 4/4] Xen core patch : /dev/mem calls io_remap_page_range From: Dave Hansen To: Ian Pratt Cc: Linux Kernel Mailing List , Andrew Morton , Keir.Fraser@cl.cam.ac.uk, Christian.Limpach@cl.cam.ac.uk In-Reply-To: References: Content-Type: text/plain Message-Id: <1100740828.12373.269.camel@localhost> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Wed, 17 Nov 2004 17:20:28 -0800 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 782 Lines: 21 On Wed, 2004-11-17 at 17:05, Ian Pratt wrote: > If there really are no uses, an alternative patch would be to > introduce an ARCH_HAS_REMAP_PAGE_RANGE. Would this be preferable? Well, first of all, remap_page_range() is now deprecated, so some of this might not even be relevant. :) My only worry is that you might want *all* calls to remap_page/pfn_range() to be to io_remap_page/pfn_range() for your arch. If this isn't the case, then there really isn't an issue. And, yes, mem.c is a mess. Thanks for the explanation. -- Dave - 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/