From mboxrd@z Thu Jan 1 00:00:00 1970 From: Konrad Rzeszutek Wilk Subject: Re: mmap in PV xen-4.0.1 Date: Tue, 16 Aug 2011 22:20:20 -0400 Message-ID: <20110817022020.GA21337@dumpdata.com> References: <20110810192546.GA2875@dumpdata.com> <20110811013104.GB1889@limbo> <20110812042608.GA2760@limbo> <20110816050608.GB27908@dumpdata.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Ranjith Ravi Cc: xen-devel@lists.xensource.com, Eric Camachat , Wei Liu List-Id: xen-devel@lists.xenproject.org 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.