All of lore.kernel.org
 help / color / mirror / Atom feed
From: mathieu.taillefumier@free.fr
To: Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: Mathieu Taillefumier <mathieu.taillefumier@free.fr>,
	linux-kernel@vger.kernel.org
Subject: Re: [Bug] pci allocation resources problems on x86_64
Date: Fri, 24 Oct 2008 22:10:41 +0200	[thread overview]
Message-ID: <1224879041.49022bc1562bb@imp.free.fr> (raw)
In-Reply-To: <200810241131.55129.jbarnes@virtuousgeek.org>

Hi,

> Ultimately we need to do better at grabbing space for PCI allocations on x86.
> I was hoping we'd have some patches in 2.6.28 that would help here, but they
> weren't ready in time.  Can you file a kernel.org bug for this problem with
> the files attached?  I'll try to find time to put together some
> improvements...

yes sure. I will do that this weekend. I already grab some more information
about this problem by reading docs. The problem seems related to iommu setup
since it is not activated when the mem < 3G but activated when the mem>3G. I do
not understand however how the kernel can report more that 4g of memory when
there are only 4g installed (So I think that the bios is buggy too). I also
remarked that the size of the /proc/mem file is not what it is intended to be.
Another supprizing thing is these lines of the dmesg-not-working file

pci 0000:0a:00.0: BAR 0: got res [0x140000000-0x1400007ff] bus [0x140000000-0x14
00007ff] flags 0x20200
pci 0000:0a:00.0: BAR 0: moved to bus [0x140000000-0x1400007ff] flags 0x20200

it seems that the drivers setup some resources that way behind the available
memory.

Regards

MAthieu

  reply	other threads:[~2008-10-24 20:18 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-24 10:13 [Bug] pci allocation resources problems on x86_64 Mathieu Taillefumier
2008-10-24 10:34 ` Mathieu Taillefumier
2008-10-24 18:31   ` Jesse Barnes
2008-10-24 20:10     ` mathieu.taillefumier [this message]
2008-10-25  8:45       ` Yinghai Lu
2008-10-25  9:04         ` Yinghai Lu
2008-10-25 12:43         ` mathieu.taillefumier
2008-10-25 19:55           ` 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=1224879041.49022bc1562bb@imp.free.fr \
    --to=mathieu.taillefumier@free.fr \
    --cc=jbarnes@virtuousgeek.org \
    --cc=linux-kernel@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.