From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mukesh Rathor Subject: Re: [RFC PATCH 3/16]: PVH xen: Add PHYSDEVOP_map_iomem Date: Fri, 25 Jan 2013 18:23:49 -0800 Message-ID: <20130125182349.1e666ec1@mantra.us.oracle.com> References: <20130111173243.2438c22a@mantra.us.oracle.com> <50F3F8CE02000078000B53E6@nat28.tlf.novell.com> <20130115153538.7b82b284@mantra.us.oracle.com> <50F684B302000078000B612B@nat28.tlf.novell.com> <20130123181223.186f5c28@mantra.us.oracle.com> <51010BA502000078000B9031@nat28.tlf.novell.com> <20130124175327.1266b156@mantra.us.oracle.com> <51024AE402000078000B9792@nat28.tlf.novell.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <51024AE402000078000B9792@nat28.tlf.novell.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Jan Beulich Cc: xen-devel List-Id: xen-devel@lists.xenproject.org On Fri, 25 Jan 2013 08:05:40 +0000 "Jan Beulich" wrote: > >>> On 25.01.13 at 02:53, Mukesh Rathor > >>> wrote: > > Since this happens once during boot, I am ok either way. Staying > > with what I've keeps linux code clean and also provides flexibily > > for future in case. But if you feel strongly, I can special case > > dom0 in linux to assume xen has it all mapped, and generate a patch > > there. Please lmk. > > Hmm, special casing Dom0 isn't what I'm after. I want this to be > transparent to the kernel in all cases (keeps the Linux code even > cleaner). Ok. I am looking into it. Stefano, Ian, any comments? You guys OK with that approach? I probably won't need PHYSDEVOP_map_iomem then. thanks, Mukesh