Message-ID: <1437407695.3214.156.camel@hp.com>
Subject: Re: Regression in v4.2-rc1: vmalloc_to_page with ioremap
From: Toshi Kani <toshi.kani@hp.com>
To: "Dixit, Ashutosh" <ashutosh.dixit@intel.com>,
        "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: "Dutt, Sudeep" <sudeep.dutt@intel.com>,
        "Rao, Nikhil" <nikhil.rao@intel.com>,
        "Williams, Dan J" <dan.j.williams@intel.com>
Date: Mon, 20 Jul 2015 09:54:55 -0600
In-Reply-To: <6DC2528F945B4149AB6566DFB5F22ED39BC5540B@ORSMSX115.amr.corp.intel.com>
References: <6DC2528F945B4149AB6566DFB5F22ED39BC5540B@ORSMSX115.amr.corp.intel.com>
Content-Type: text/plain; charset="UTF-8"
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1297
Lines: 35

On Sat, 2015-07-18 at 18:04 +0000, Dixit, Ashutosh wrote:
> vmalloc_to_page with ioremap'd memory used to work correctly till 
> v4.1. In
> v4.2-rc1 when ioremap is done using huge pages vmalloc_to_page on 
> ioremap'd
> memory crashes. Are there plans to fix this?
> 
> An example of the use of vmalloc_to_page with ioremap is in the Intel 
> MIC SCIF
> driver (drivers/misc/mic/scif/scif_nodeqp.c) which dma map's the 
> ioremap'd range
> of one device to a second device.

Yes, vmalloc_to_page() assumes 4KB mappings.  But ioremap with huge
pages was enabled in v4.1, while v4.2-rc1 has update for the check with
MTRRs.  Can you send me outputs of the following files?  If the driver
fails to load in v4.2-rc1, you can obtain the info in v4.1.

  /proc/mtrr
  /proc/iomem
  /proc/vmallocinfo
  /sys/kernel/debug/kernel_page_tables (need CONFIG_X86_PTDUMP set)

Also, does the driver map a regular memory range with ioremap?  If not,
how does 'struct page' get allocated for the range (since
vmalloc_to_page returns a page pointer)?

Thanks,
-Toshi

--
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/