From: Steven Newbury <steve@snewbury.org.uk>
To: Yinghai Lu <yinghai@kernel.org>
Cc: "Barnes, Jesse" <jesse.barnes@intel.com>,
Dave Airlie <airlied@linux.ie>,
Bjorn Helgaas <bhelgaas@google.com>,
linux-pci@vger.kernel.org,
DRI mailing list <dri-devel@lists.freedesktop.org>
Subject: Re: PCI resources above 4GB
Date: Fri, 13 Apr 2012 09:34:36 +0100 [thread overview]
Message-ID: <1334306076.2910.10.camel@Nokia-N900> (raw)
In-Reply-To: <CAE9FiQXvHjW3pL4Nrb-3Oqw5Ht-7MqCL7_isL+Gm41qWOd1yRQ@mail.gmail.com>
On Fri, 13 Apr 2012, 09:26:55 BST, Yinghai Lu <yinghai@kernel.org> wrote:
> On Thu, Apr 12, 2012 at 9:40 AM, Steven Newbury <steve@snewbury.org.uk>
> wrote:
> > > >
> > > > It would be useful to preserve as much low PCI memory address
> > > > space as possible for hotplug devices (like my Radeon), but the
> > > > other problem is small regions get allocated at the bottom,
> > > > resulting in the inability to find large aligned regions later on.
> > > > I see code to default to top-down allocation was reverted, I
> > > > guess I'm going to have to dig into the archive to find out why...
>
> Please check attached patches that will find_resource with fit. It may
> leave space for your hotplug devices.
>
> PCI: Should add children device res to fail list
> PCI: Try to allocate mem64 above 4G at first
> intel-gtt: Read 64bit for gmar_bus_addr
> PCI: Make sure assign same align with large size resource at first
> resource: make find_resource could return just fit resource
> PCI: Don't allocate small resource in big empty space.
> resource: only return range with needed align
>
> You can get them from
>
>
> git://git.kernel.org/pub/scm/linux/kernel/git/yinghai/linux-yinghai.git
> for-pci-res-alloc
>
Thanks Yinghai, I'll give it a spin.
next prev parent reply other threads:[~2012-04-13 8:35 UTC|newest]
Thread overview: 73+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-09 10:49 PCI resources above 4GB Steven Newbury
2012-04-10 0:51 ` Bjorn Helgaas
2012-04-10 10:53 ` Steven Newbury
2012-04-10 15:16 ` Yinghai Lu
[not found] ` <4F8467AA.90305@snewbury.org.uk>
2012-04-10 17:29 ` Steven Newbury
2012-04-10 18:40 ` Yinghai Lu
2012-04-10 18:44 ` Steven Newbury
2012-04-10 19:00 ` Steven Newbury
2012-04-10 19:04 ` Steven Newbury
2012-04-10 19:16 ` Yinghai Lu
2012-04-10 19:46 ` Steven Newbury
2012-04-10 20:07 ` Yinghai Lu
2012-04-10 20:26 ` Steven Newbury
2012-04-10 20:45 ` Yinghai Lu
2012-04-10 21:19 ` Steven Newbury
2012-04-11 3:37 ` Bjorn Helgaas
2012-04-11 5:33 ` Steven Newbury
2012-04-11 9:03 ` Steven Newbury
2012-04-11 14:33 ` Steven Newbury
2012-04-11 23:59 ` Bjorn Helgaas
2012-04-12 11:39 ` Steven Newbury
2012-04-12 0:57 ` Yinghai Lu
2012-04-12 11:22 ` Steven Newbury
2012-04-12 16:07 ` Yinghai Lu
2012-04-12 16:40 ` Steven Newbury
2012-04-13 8:26 ` Yinghai Lu
2012-04-13 8:34 ` Steven Newbury [this message]
2012-04-13 11:45 ` Steven Newbury
2012-04-13 11:58 ` Steven Newbury
2012-04-13 12:49 ` Steven Newbury
2012-04-13 13:26 ` Steven Newbury
2012-04-13 13:52 ` drm-next i915 regression? ( was: Re: PCI resources above 4GB) Steven Newbury
2012-04-13 14:08 ` Steven Newbury
2012-04-13 14:13 ` Daniel Vetter
2012-04-13 14:19 ` Steven Newbury
2012-04-13 15:23 ` Steven Newbury
2012-04-13 15:49 ` Steven Newbury
2012-04-13 16:17 ` Yinghai Lu
2012-04-13 17:12 ` btrfs oops [was Re: drm-next i915 regression? ( was: Re: PCI resources above 4GB)] Steven Newbury
2012-04-13 17:38 ` drm-next i915 regression? ( was: Re: PCI resources above 4GB) Steven Newbury
2012-04-13 18:12 ` Steven Newbury
2012-04-13 21:51 ` Btrfs corruption Oops " Steven Newbury
2012-04-14 17:37 ` PCI resources above 4GB Steven Newbury
2012-04-14 18:05 ` Steven Newbury
2012-04-14 18:42 ` Steven Newbury
2012-04-14 19:08 ` Steven Newbury
2012-04-14 19:21 ` Steven Newbury
2012-04-14 20:48 ` Yinghai Lu
2012-04-15 10:19 ` Steven Newbury
2012-04-15 10:20 ` Steven Newbury
2012-04-15 11:37 ` Steven Newbury
2012-04-15 17:25 ` Steven Newbury
2012-04-15 17:31 ` Steven Newbury
2012-04-15 20:05 ` Yinghai Lu
2012-04-15 20:06 ` Yinghai Lu
2012-04-16 6:54 ` Yinghai Lu
2012-04-16 7:01 ` Steven Newbury
2012-04-16 17:29 ` Yinghai Lu
2012-04-18 7:21 ` Steven Newbury
2012-04-24 9:49 ` Steven Newbury
[not found] ` <4FB227D3.7090002@snewbury.org.uk>
[not found] ` <CAE9FiQX48eCS85eWMFxm6fCWgu2zwxvSywtQhsf-35WEvBfJVQ@mail.gmail.com>
2012-05-17 12:27 ` Steven Newbury
2012-05-17 12:34 ` Steven Newbury
2012-05-17 16:36 ` Yinghai Lu
2012-05-18 7:45 ` Yinghai Lu
2012-05-18 9:08 ` Yinghai Lu
2012-05-21 17:27 ` Steven Newbury
2012-05-29 23:19 ` Bjorn Helgaas
2012-06-01 23:06 ` Bjorn Helgaas
2012-04-15 3:21 ` Yinghai Lu
2012-04-15 10:18 ` Steven Newbury
2012-04-15 11:31 ` Steven Newbury
2012-04-12 16:29 ` Steven Newbury
2012-04-11 11:43 ` Steven Newbury
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=1334306076.2910.10.camel@Nokia-N900 \
--to=steve@snewbury.org.uk \
--cc=airlied@linux.ie \
--cc=bhelgaas@google.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=jesse.barnes@intel.com \
--cc=linux-pci@vger.kernel.org \
--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).