From: Yanko Kaneti <yaneti@declera.com>
To: Bjorn Helgaas <bjorn.helgaas@hp.com>
Cc: Jesse Barnes <jbarnes@virtuousgeek.org>,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
"Rafael J. Wysocki" <rjw@sisk.pl>,
Linus Torvalds <torvalds@linux-foundation.org>,
Thomas Renninger <trenn@suse.de>,
maciej.rutecki@gmail.com
Subject: Re: [PATCH v1 0/3] [RFC] resource, PCI: work around pci=use_crs conflicts
Date: Fri, 12 Mar 2010 16:49:37 +0200 [thread overview]
Message-ID: <1268405377.3493.4.camel@d2> (raw)
In-Reply-To: <20100311235954.4355.23100.stgit@bob.kio>
On Thu, 2010-03-11 at 17:01 -0700, Bjorn Helgaas wrote:
> These patches are to fix this pci=use_crs regression:
>
> http://bugzilla.kernel.org/show_bug.cgi?id=15480
>
> The problem is that BIOS reported a PCI host bridge window that overlaps
> system RAM. This workaround trims the window to avoid the overlap, which
> requires information about the conflicting resource.
>
> Yanko, I reworked these a bit, so if you have a chance to retest them
> and collect another dmesg log, I'd appreciate it.
>
> I'm still hoping for someone to find out how Windows deals with this, but
> haven't gotten any data yet.
>
> ---
>
> Bjorn Helgaas (3):
> resources: add interfaces that return conflict information
> x86/PCI: trim _CRS windows when they conflict with previous reservations
> PCI: for address space collisions, show conflicting resource
>
>
> arch/x86/pci/acpi.c | 48 ++++++++++++++++++++++++++++++++++-------------
> drivers/pci/setup-res.c | 14 ++++++++------
> include/linux/ioport.h | 2 ++
> kernel/resource.c | 44 ++++++++++++++++++++++++++++++++++++-------
> 4 files changed, 82 insertions(+), 26 deletions(-)
Applied on top of latest rawhide kernel. Boots without pci= workarounds
and works fine so far.
Dmesg attached to the bug report.
Thanks
next prev parent reply other threads:[~2010-03-12 14:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-12 0:01 [PATCH v1 0/3] [RFC] resource, PCI: work around pci=use_crs conflicts Bjorn Helgaas
2010-03-12 0:01 ` [PATCH v1 1/3] resources: add interfaces that return conflict information Bjorn Helgaas
2010-03-19 20:46 ` Jesse Barnes
2010-03-12 0:01 ` [PATCH v1 2/3] x86/PCI: trim _CRS windows when they conflict with previous reservations Bjorn Helgaas
2010-03-17 3:25 ` Kenji Kaneshige
2010-03-17 4:22 ` Bjorn Helgaas
2010-03-17 8:47 ` Kenji Kaneshige
2010-03-17 13:15 ` Bjorn Helgaas
2010-03-12 0:01 ` [PATCH v1 3/3] PCI: for address space collisions, show conflicting resource Bjorn Helgaas
2010-03-12 14:49 ` Yanko Kaneti [this message]
2010-03-16 19:59 ` [PATCH v1 0/3] [RFC] resource, PCI: work around pci=use_crs conflicts Bjorn Helgaas
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=1268405377.3493.4.camel@d2 \
--to=yaneti@declera.com \
--cc=bjorn.helgaas@hp.com \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=maciej.rutecki@gmail.com \
--cc=rjw@sisk.pl \
--cc=torvalds@linux-foundation.org \
--cc=trenn@suse.de \
/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.