From: Yinghai Lu <yinghai@kernel.org>
To: Tvrtko Ursulin <tvrtko.ursulin@sophos.com>
Cc: Tvrtko Ursulin <tvrtko@ursulin.net>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Are these MTRR settings correct?
Date: Mon, 14 Dec 2009 03:25:58 -0800 [thread overview]
Message-ID: <4B2620C6.9050901@kernel.org> (raw)
In-Reply-To: <200912141119.55068.tvrtko.ursulin@sophos.com>
Tvrtko Ursulin wrote:
> On Sunday 13 December 2009 22:56:23 Yinghai Lu wrote:
>> Tvrtko Ursulin wrote:
>>> On Sunday 13 Dec 2009 09:25:33 Yinghai Lu wrote:
>>>> On Sun, Dec 13, 2009 at 12:26 AM, Tvrtko Ursulin <tvrtko@ursulin.net>
> wrote:
>>>>> reg00: base=0x000000000 ( 0MB), size= 2048MB, count=1: write-back
>>>>> reg01: base=0x080000000 ( 2048MB), size= 1024MB, count=1: write-back
>>>>> reg02: base=0x0c0000000 ( 3072MB), size= 256MB, count=1: write-back
>>>>> reg03: base=0x0f0000000 ( 3840MB), size= 128MB, count=1:
>>>>> write-combining
>>>>>
>>>>> Still looks like from 3328MB to 3840MB is of status unknown?
>>>>>
>>>>> dmesg in that case:
>>> [ 0.250038] node 0 link 0: io port [1000, ffffff]
>>> [ 0.250040] TOM: 00000000e0000000 aka 3584M
>>> [ 0.250041] Fam 10h mmconf [e0000000, efffffff]
>>> [ 0.250043] node 0 link 0: mmio [a0000, bffff]
>>> [ 0.250045] node 0 link 0: mmio [e0000000, efffffff] ==> none
>>> [ 0.250047] node 0 link 0: mmio [f0000000, fe7fffff]
>>> [ 0.250048] node 0 link 0: mmio [fe800000, fe9fffff]
>>> [ 0.250050] node 0 link 0: mmio [fea00000, ffefffff]
>>> [ 0.250051] TOM2: 0000000120000000 aka 4608M
>>> [ 0.250053] bus: [00,07] on node 0 link 0
>>> [ 0.250054] bus: 00 index 0 io port: [0, ffff]
>>> [ 0.250055] bus: 00 index 1 mmio: [a0000, bffff]
>>> [ 0.250057] bus: 00 index 2 mmio: [f0000000, ffffffff]
>>> [ 0.250058] bus: 00 index 3 mmio: [120000000, fcffffffff]
>>> [ 0.250065] ACPI: bus type pci registered
>>> [ 0.250088] PCI: Found AMD Family 10h NB with MMCONFIG support.
>>> [ 0.250091] PCI: MCFG configuration 0: base e0000000 segment 0 buses 0
>>> - 255 [ 0.250092] PCI: Not using MMCONFIG.
>>> [ 0.250094] PCI: Using configuration type 1 for base access
>>> [ 0.250095] PCI: Using configuration type 1 for extended access
>> 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...
Thanks
Yinghai
next prev parent reply other threads:[~2009-12-14 11:27 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 [this message]
2009-12-14 19:34 ` Tvrtko Ursulin
2009-12-14 19:47 ` Yinghai Lu
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=4B2620C6.9050901@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