From: TJ <tj@iam.tj>
To: unlisted-recipients:; (no To-header on input)
Cc: linux-pci@vger.kernel.org
Subject: Re: Limiting BAR resource region size allocation (device claims 2x what it needs) ?
Date: Wed, 29 Aug 2012 15:19:04 +0100 [thread overview]
Message-ID: <503E24D8.3010601@iam.tj> (raw)
In-Reply-To: <20120829132415.GA21160@parisc-linux.org>
On 29/08/12 14:24, Matthew Wilcox wrote:
> On Wed, Aug 29, 2012 at 01:50:47PM +0100, TJ wrote:
>> The CPU is 64-bit but the i945PM northbridge is 32-bit (so no physical > 4GB addressing). With PCI allocations as they are the system is limited to 2GB of RAM under Linux (3GB on Windows Vista).
>
> According to the laptop specs, it's limited to 2GB RAM:
>
> http://www.sony.co.uk/support/en/product/VGN-FE41Z/specifications
>
> Personally, I'm not terribly excited about doing much work to enhance
> a 6 year old laptop...
>
I've had it from new. It supports 4GB physically - 2 SO-DIM slots @ 2GB each.
Up until now I've been using my own resource allocation patches I wrote in 2009 to do things the same way as Windows does, to allow access to 3GB of RAM. At that time I discussed them with Jesse
Barnes and analysed the problem comprehensively. See http://tjworld.net/wiki/Linux/Kernel/Bug/PciAllocationAlgorithm
I'd now like to work with a mainline kernel but that would force me to lose 1/3 of RAM as things stand.
As things have changed significantly in PCI-land since I wrote my patches they no longer fit so I'm looking to find a way to use mainline and keep the 3GB of RAM.
Relatively recently I realised the VRAM is only 128MB so I wondered if there might be a slightly easier way by forcing the region size allocation to match. Reducing the region size to 128MB would also
mean double the number of boundaries it could align to. That might avoid the need for my custom patches to shuffle allocations around.
prev parent reply other threads:[~2012-08-29 14:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-29 12:50 Limiting BAR resource region size allocation (device claims 2x what it needs) ? TJ
2012-08-29 13:24 ` Matthew Wilcox
2012-08-29 14:19 ` TJ [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=503E24D8.3010601@iam.tj \
--to=tj@iam.tj \
--cc=linux-pci@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.