From: Yinghai Lu <yinghai@kernel.org>
To: Tvrtko Ursulin <tvrtko@ursulin.net>
Cc: Tvrtko Ursulin <tvrtko.ursulin@sophos.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Are these MTRR settings correct?
Date: Mon, 14 Dec 2009 11:47:40 -0800 [thread overview]
Message-ID: <4B26965C.6020203@kernel.org> (raw)
In-Reply-To: <200912141934.10628.tvrtko@ursulin.net>
Tvrtko Ursulin wrote:
> On Monday 14 Dec 2009 11:25:58 Yinghai Lu wrote:
>>>> something wrong, we should not check that with e820 or acpi resource in
>>>> that case. please check
>>>>
>>>> {PATCH] x86/pci: don't check mmconf again if it is from MSR with amd
>>>> faml0h
>>>>
>>>> for AMD Fam10h, it we read mmconf from MSR early, we should just trust
>>>> it because we check it and correct it already.
>>>>
>>>> so skip the reject check there.
>>> [path snipped]
>>>
>>> Do you want me to test with this patch and that pci=.. option active and
>>> post dmesg? Or without the pci=... option?
>> with this patch and pci=... and post dmesg...
>
> Here you go:
>
...
> [ 0.250041] node 0 link 0: io port [1000, ffffff]
> [ 0.250043] TOM: 00000000e0000000 aka 3584M
> [ 0.250044] Fam 10h mmconf [e0000000, efffffff]
> [ 0.250046] node 0 link 0: mmio [a0000, bffff]
> [ 0.250048] node 0 link 0: mmio [e0000000, efffffff] ==> none
> [ 0.250050] node 0 link 0: mmio [f0000000, fe7fffff]
> [ 0.250051] node 0 link 0: mmio [fe800000, fe9fffff]
> [ 0.250053] node 0 link 0: mmio [fea00000, ffefffff]
> [ 0.250054] TOM2: 0000000120000000 aka 4608M
> [ 0.250056] bus: [00,07] on node 0 link 0
> [ 0.250057] bus: 00 index 0 io port: [0, ffff]
> [ 0.250058] bus: 00 index 1 mmio: [a0000, bffff]
> [ 0.250060] bus: 00 index 2 mmio: [f0000000, ffffffff]
> [ 0.250061] bus: 00 index 3 mmio: [120000000, fcffffffff]
> [ 0.250068] ACPI: bus type pci registered
> [ 0.250091] PCI: Found AMD Family 10h NB with MMCONFIG support.
> [ 0.254793] PCI: Using MMCONFIG at e0000000 - efffffff
> [ 0.254795] PCI: Using configuration type 1 for base access
...
thanks, mmconf works on your system.
YH
next prev parent reply other threads:[~2009-12-14 19:48 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-13 8:07 Are there MTRR settings correct? Tvrtko Ursulin
2009-12-13 8:26 ` Are these " Tvrtko Ursulin
2009-12-13 9:25 ` Yinghai Lu
2009-12-13 17:19 ` Tvrtko Ursulin
2009-12-13 22:56 ` Yinghai Lu
2009-12-14 11:19 ` Tvrtko Ursulin
2009-12-14 11:25 ` Yinghai Lu
2009-12-14 19:34 ` Tvrtko Ursulin
2009-12-14 19:47 ` Yinghai Lu [this message]
2009-12-14 20:16 ` Tvrtko Ursulin
2009-12-14 20:26 ` Yinghai Lu
2009-12-15 1:22 ` Robert Hancock
2009-12-15 1:42 ` Yinghai Lu
2009-12-15 16:55 ` Bjorn Helgaas
2009-12-15 18:01 ` Yinghai Lu
2009-12-15 20:50 ` Robert Hancock
2009-12-15 21:09 ` Jesse Barnes
2009-12-16 0:14 ` Robert Hancock
2009-12-16 6:26 ` Yinghai Lu
2009-12-15 2:47 ` [PATCH] x86/pci: don't check mmconf again if it is from MSR with amd faml0h Yinghai Lu
2009-12-16 20:06 ` Jesse Barnes
2009-12-16 22:18 ` Yinghai Lu
2009-12-13 20:26 ` Are these MTRR settings correct? Robert Hancock
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=4B26965C.6020203@kernel.org \
--to=yinghai@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tvrtko.ursulin@sophos.com \
--cc=tvrtko@ursulin.net \
/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