RE: [Xen-devel] problem with direct_remap_pfn_range parameters

["Magenheimer, Dan (HP Labs Fort Collins)" <dan.magenheimer@xxxxxx>]

sparse/drivers/xen is slowly (but surely) becoming common code
and direct_remap_pfn_range is called in
drivers/xen/privcmd/privcmd.c.  Changing that usage
means changing many other (x86) files, including some that
call it with &init_mm.  (Is there a parent vma for
init_mm?)

Or did I misunderstand your point?

Thanks,
Dan

> -----Original Message-----
> From: Keir Fraser [mailto:Keir.Fraser@xxxxxxxxxxxx] 
> Sent: Thursday, September 15, 2005 11:17 AM
> To: Magenheimer, Dan (HP Labs Fort Collins)
> Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
> Subject: Re: [Xen-devel] problem with direct_remap_pfn_range 
> parameters
> 
> 
> On 15 Sep 2005, at 17:45, Magenheimer, Dan (HP Labs Fort 
> Collins) wrote:
> 
> > I see there are a number of possible solutions and
> > none of them are particularly pretty, so thought
> > I would open a discussion rather than submit an
> > ugly patch that would likely be rejected :-)
> 
> I think direct_remap_pfn_range() is not accessed directly from common 
> code, so the interface can easily be changed. If so, changing 
> to take a 
> vma instead of mm is the obvious fix.
> 
>   -- Keir
> 
> 

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel