Re: mmap in PV xen-4.0.1

[Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>]

On Tue, Aug 16, 2011 at 11:27:03AM -0700, Ranjith Ravi wrote:
> On Mon, Aug 15, 2011 at 10:06 PM, Konrad Rzeszutek Wilk <
> konrad.wilk@oracle.com> wrote:
> 
> > On Mon, Aug 15, 2011 at 08:13:37PM -0700, Ranjith Ravi wrote:
> > > > Looking into the kernel source, a check in range_is_allowed failed so
> > > > I just can't map /dev/mem with specified range (-EPERM).
> > >
> > >  mmap() and read access  works on 2.6.37.6
> > > ( dom0 - fc13 xen 4.0.2)
> > > Tried it after disabling 'CONFIG_STRICT_DEVMEM' in kernel config.
> >
> > So it did not work with CONFIG_STRICT_DEVMEM=y?
> >
> >
> mmap() returns failure with CONFIG_STRICT_DEVMEM=y
> 
>  >
> > > Can someone point out the changes/patches in 2.6.37.6 which fixes mmap()
> > > problem ?
> >
> > Um, so 2.6.37 did not work?
> > >
> >
> 
> mmap()/read access worked on 2.6.37.6
> Would like to try the same changes on 2.6.32 (Debian 6.0-pvops)
> if some one can point the changes/patches.

No idea. Looking at the changelog of 2.6.37 nothing really strikes
me as having fixed this.