linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bjorn Helgaas <bhelgaas@google.com>
To: Yinghai Lu <yinghai@kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	"H. Peter Anvin" <hpa@zytor.com>, Ingo Molnar <mingo@redhat.com>,
	linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] PCI: Don't reject 64bit mmio on 32bit/PAE mode
Date: Fri, 14 Nov 2014 17:26:18 -0700	[thread overview]
Message-ID: <20141115002618.GA4280@google.com> (raw)
In-Reply-To: <1415937550-14469-1-git-send-email-yinghai@kernel.org>

On Thu, Nov 13, 2014 at 07:59:10PM -0800, Yinghai Lu wrote:
> Aaron reported 32bit/PAE mode, has problem with 64bit resource.
> 
> [    6.610012] pci 0000:03:00.0: reg 0x10: [mem 0x383fffc00000-0x383fffdfffff 64bit pref]
> [    6.622195] pci 0000:03:00.0: reg 0x20: [mem 0x383fffe04000-0x383fffe07fff 64bit pref]
> [    6.656112] pci 0000:03:00.1: reg 0x10: [mem 0x383fffa00000-0x383fffbfffff 64bit pref]
> [    6.668293] pci 0000:03:00.1: reg 0x20: [mem 0x383fffe00000-0x383fffe03fff 64bit pref]
> [    6.702055] pci 0000:00:02.2: PCI bridge to [bus 03-04]
> [    6.706434] pci 0000:00:02.2:   bridge window [io  0x1000-0x1fff]
> [    6.711783] pci 0000:00:02.2:   bridge window [mem 0x91900000-0x91cfffff]
> [    6.717906] pci 0000:00:02.2: can't handle 64-bit address space for bridge
> 
> So the kernel reject 64bit mmio on pci pref bridge that is assigned by
> firmware.
> 
> When 32bit PAE is enabled, we could support 64bit mmio.
> but BITS_PER_LONG==64 checking could reject firmware assigned mmio that
> is above 4G. On x86 32bit always has BITS_PER_LONG equal to 32.
> 
> We could use CONFIG_ARCH_DMA_ADDR_T_64BIT or dma_addr_t size checking instead.
> Use dma_addr_t size checking to avoid using MARCO.
> 
> Also need to change to use dma_addr_t instead of unsigned long
> for base/limit to avoid overflow.
> 
> Link: https://bugzilla.kernel.org/show_bug.cgi?id=88131
> Reported-by: Aaron Ma <mapengyu@gmail.com>
> Tested-by: Aaron Ma <mapengyu@gmail.com>
> Signed-off-by: Yinghai Lu <yinghai@kernel.org>

Applied to for-linus for v3.18, thanks!

> ---
>  drivers/pci/probe.c |   22 +++++++++++-----------
>  1 file changed, 11 insertions(+), 11 deletions(-)
> 
> Index: linux-2.6/drivers/pci/probe.c
> ===================================================================
> --- linux-2.6.orig/drivers/pci/probe.c
> +++ linux-2.6/drivers/pci/probe.c
> @@ -406,15 +406,15 @@ static void pci_read_bridge_mmio_pref(st
>  {
>  	struct pci_dev *dev = child->self;
>  	u16 mem_base_lo, mem_limit_lo;
> -	unsigned long base, limit;
> +	dma_addr_t base, limit;
>  	struct pci_bus_region region;
>  	struct resource *res;
>  
>  	res = child->resource[2];
>  	pci_read_config_word(dev, PCI_PREF_MEMORY_BASE, &mem_base_lo);
>  	pci_read_config_word(dev, PCI_PREF_MEMORY_LIMIT, &mem_limit_lo);
> -	base = ((unsigned long) mem_base_lo & PCI_PREF_RANGE_MASK) << 16;
> -	limit = ((unsigned long) mem_limit_lo & PCI_PREF_RANGE_MASK) << 16;
> +	base = ((dma_addr_t) mem_base_lo & PCI_PREF_RANGE_MASK) << 16;
> +	limit = ((dma_addr_t) mem_limit_lo & PCI_PREF_RANGE_MASK) << 16;
>  
>  	if ((mem_base_lo & PCI_PREF_RANGE_TYPE_MASK) == PCI_PREF_RANGE_TYPE_64) {
>  		u32 mem_base_hi, mem_limit_hi;
> @@ -428,15 +428,15 @@ static void pci_read_bridge_mmio_pref(st
>  		 * this, just assume they are not being used.
>  		 */
>  		if (mem_base_hi <= mem_limit_hi) {
> -#if BITS_PER_LONG == 64
> -			base |= ((unsigned long) mem_base_hi) << 32;
> -			limit |= ((unsigned long) mem_limit_hi) << 32;
> -#else
> -			if (mem_base_hi || mem_limit_hi) {
> -				dev_err(&dev->dev, "can't handle 64-bit address space for bridge\n");
> -				return;
> +			if (sizeof(dma_addr_t) < 8) {
> +				if (mem_base_hi || mem_limit_hi) {
> +					dev_err(&dev->dev, "can't handle 64-bit address space for bridge\n");
> +					return;
> +				}
> +			} else  {
> +				base |= ((dma_addr_t) mem_base_hi) << 32;
> +				limit |= ((dma_addr_t) mem_limit_hi) << 32;
>  			}
> -#endif
>  		}
>  	}
>  	if (base <= limit) {

      reply	other threads:[~2014-11-15  0:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-14  3:59 [PATCH] PCI: Don't reject 64bit mmio on 32bit/PAE mode Yinghai Lu
2014-11-15  0:26 ` Bjorn Helgaas [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20141115002618.GA4280@google.com \
    --to=bhelgaas@google.com \
    --cc=akpm@linux-foundation.org \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=yinghai@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).