linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Yinghai Lu <yinghai@kernel.org>
To: Bjorn Helgaas <bhelgaas@google.com>
Cc: Guo Chao <yan@linux.vnet.ibm.com>,
	linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
	Yinghai Lu <yinghai@kernel.org>
Subject: [PATCH v4 0/5] PCI: allocate 64bit mmio pref
Date: Mon,  9 Dec 2013 22:54:39 -0800	[thread overview]
Message-ID: <1386658484-15774-1-git-send-email-yinghai@kernel.org> (raw)

mmio 64 allocation that could help Guo Chao <yan@linux.vnet.ibm.com> on powerpc mmio allocation.
It will try to assign 64 bit resource above 4g at first.

And it is based on current pci/for-linus.

-v2: update after patch that move device_del down to pci_destroy_dev.
     add "Try best to allocate pref mmio 64bit above 4G"

-v3: refresh and send out after pci_clip_resource() changes,
     as Bjorn is not happy with attachments.

-v4: make pcibios_resource_to_bus take bus directly.

Yinghai Lu (5):
  PCI: pcibus address to resource converting take bus instead of dev
  PCI: Don't use 4G bus address directly in resource allocation
  PCI: Try to allocate mem64 above 4G at first
  PCI: Try best to allocate pref mmio 64bit above 4g
  PCI: Sort pci root bus resources list

 arch/alpha/kernel/pci-sysfs.c       |   4 +-
 arch/powerpc/kernel/pci-common.c    |   4 +-
 arch/powerpc/kernel/pci_of_scan.c   |   4 +-
 arch/sparc/kernel/pci.c             |   6 +-
 arch/x86/include/asm/pci.h          |   1 -
 drivers/pci/bus.c                   |  73 +++++++++++++++---
 drivers/pci/host-bridge.c           |  24 +++---
 drivers/pci/probe.c                 |  18 ++---
 drivers/pci/quirks.c                |   2 +-
 drivers/pci/rom.c                   |   2 +-
 drivers/pci/setup-bus.c             | 149 +++++++++++++++++++++++-------------
 drivers/pci/setup-res.c             |  16 +++-
 drivers/pcmcia/i82092.c             |   2 +-
 drivers/pcmcia/yenta_socket.c       |   6 +-
 drivers/scsi/sym53c8xx_2/sym_glue.c |   5 +-
 drivers/video/arkfb.c               |   2 +-
 drivers/video/s3fb.c                |   2 +-
 drivers/video/vt8623fb.c            |   2 +-
 include/linux/pci.h                 |   8 +-
 19 files changed, 217 insertions(+), 113 deletions(-)

-- 
1.8.4


             reply	other threads:[~2013-12-10  6:54 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-10  6:54 Yinghai Lu [this message]
2013-12-10  6:54 ` [PATCH v4 1/5] PCI: pcibus address to resource converting take bus instead of dev Yinghai Lu
2013-12-10  6:54 ` [PATCH v4 2/5] PCI: Don't use 4G bus address directly in resource allocation Yinghai Lu
2013-12-10  6:54 ` [PATCH v4 3/5] PCI: Try to allocate mem64 above 4G at first Yinghai Lu
2013-12-10  6:54 ` [PATCH v4 4/5] PCI: Try best to allocate pref mmio 64bit above 4g Yinghai Lu
2013-12-16  8:23   ` Guo Chao
2013-12-16 18:13     ` Yinghai Lu
2013-12-16 21:36       ` Yinghai Lu
2013-12-17  0:36         ` Yinghai Lu
2013-12-18  9:51           ` Guo Chao
2013-12-10  6:54 ` [PATCH v4 5/5] PCI: Sort pci root bus resources list Yinghai Lu

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=1386658484-15774-1-git-send-email-yinghai@kernel.org \
    --to=yinghai@kernel.org \
    --cc=bhelgaas@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=yan@linux.vnet.ibm.com \
    /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).