public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Yinghai Lu <yinghai.lu@oracle.com>
To: Bjorn Helgaas <bjorn.helgaas@hp.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Jesse Barnes <jbarnes@virtuousgeek.org>,
	"H. Peter Anvin" <hpa@zytor.com>,
	Andy Isaacson <adi@hexapodia.org>,
	"R. Andrew Bailey" <bailey@akamai.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>,
	guenter.roeck@ericsson.com,
	"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
	"x86@kernel.org" <x86@kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Thomas Renninger <trenn@suse.de>,
	yaneti@declera.com
Subject: Re: [PATCH] x86/PCI: never allocate PCI MMIO resources below    BIOS_END
Date: Wed, 28 Apr 2010 10:14:45 -0700	[thread overview]
Message-ID: <4BD86D05.20402@oracle.com> (raw)
In-Reply-To: <201004281007.37016.bjorn.helgaas@hp.com>

Never mind, for 2.6.34 your patch should be good enough.

On 04/28/2010 09:07 AM, Bjorn Helgaas wrote:
> Yinghai, ping, do you have any more information about this?
>
> On Tuesday 27 April 2010 09:11:10 am Bjorn Helgaas wrote:
>   
>> On Monday 26 April 2010 07:41:55 pm Yinghai wrote:
>> But let's double-check this:
>>
>>     
>>> also find one AMD system:
>>> [    7.056011] pci_root PNP0A03:00: host bridge window [mem 0xfed20000-0xffffffff]
>>> ...
>>> pci assign unassign code could use range like [mem 0xfed20000-0xffffffff] wrongly.
>>>       
>> I agree, it's very unlikely that it's safe to put PCI devices all the
>> way up to 0xffffffff.  I suspect this might be fixed by d558b483d5a,
>> which computes the end of the bridge window using _MAX rather than _LEN.
>>
>> See https://bugzilla.kernel.org/show_bug.cgi?id=15480#c15 for an example
>> similar to the one above: we originally thought the window was
>> [mem 0xcff00000-0xffffffff], but d558b483d5a changes that to
>> [mem 0xcff00000-0xfebfffff], which matches what Windows found.
>>
>> Yinghai, can you take a look at your AMD system again with a kernel that
>> includes d558b483d5a, and see whether we still have a problem?  If we
>> *do* still have a problem, please open a bugzilla and attach a dmesg log
>> with ACPI resource info collected with the debug patch here:
>> https://bugzilla.kernel.org/show_bug.cgi?id=15533#c5
>>
>> Bjorn
>>
>>     
>
>   


  reply	other threads:[~2010-04-28 17:12 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-26 23:02 [PATCH] x86/PCI: never allocate PCI MMIO resources below BIOS_END H. Peter Anvin
2010-04-26 23:25 ` Jesse Barnes
2010-04-26 23:49   ` H. Peter Anvin
2010-04-26 23:49   ` H. Peter Anvin
2010-04-27  0:05     ` Jesse Barnes
2010-04-27  1:27       ` Linus Torvalds
2010-04-27  1:40         ` Jesse Barnes
2010-04-27  1:41         ` Yinghai
2010-04-27 15:11           ` Bjorn Helgaas
2010-04-28 16:07             ` Bjorn Helgaas
2010-04-28 17:14               ` Yinghai Lu [this message]
2010-04-28 19:06                 ` Bjorn Helgaas
2010-04-28 19:10                   ` Yinghai
2010-04-28 19:23                     ` Bjorn Helgaas
  -- strict thread matches above, loose matches on Subject: below --
2010-04-27  2:02 H. Peter Anvin
2010-04-13 21:42 [PATCH -v2 1/2] x86: Reserve [0xa0000, 0x100000] in e820 map Yinghai
2010-04-21  5:33 ` [PATCH -v4 1/3] " Yinghai
2010-04-21 19:31   ` Andy Isaacson
2010-04-23 23:05     ` [PATCH] x86/PCI: never allocate PCI MMIO resources below BIOS_END Bjorn Helgaas
2010-04-23 23:44       ` H. Peter Anvin
2010-04-24  0:36         ` Yinghai Lu
2010-04-26 12:50       ` R. Andrew Bailey
2010-04-26 15:40         ` Bjorn Helgaas
2010-04-26 18:34       ` Andy Isaacson
2010-04-26 19:31         ` Jesse Barnes
2010-04-26 20:27           ` Bjorn Helgaas
2010-04-26 20:37             ` Jesse Barnes
2010-04-26 21:07               ` Yinghai
2010-04-26 21:19                 ` H. Peter Anvin
2010-04-26 21:12               ` H. Peter Anvin
2010-04-26 21:25                 ` Jesse Barnes
2010-04-26 21:44                   ` H. Peter Anvin
2010-04-26 21:53                     ` Jesse Barnes
2010-04-26 21:59                   ` Yinghai Lu
2010-04-26 21:44                 ` jacob pan

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=4BD86D05.20402@oracle.com \
    --to=yinghai.lu@oracle.com \
    --cc=adi@hexapodia.org \
    --cc=bailey@akamai.com \
    --cc=bjorn.helgaas@hp.com \
    --cc=guenter.roeck@ericsson.com \
    --cc=hpa@zytor.com \
    --cc=jbarnes@virtuousgeek.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.org \
    --cc=trenn@suse.de \
    --cc=x86@kernel.org \
    --cc=yaneti@declera.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