From: "H. Peter Anvin" <hpa@zytor.com>
To: Yinghai Lu <yhlu.kernel@gmail.com>
Cc: Andi Kleen <ak@suse.de>, Greg KH <greg@kroah.com>,
Andrew Morton <akpm@linux-foundation.org>,
Jeff Garzik <jeff@garzik.org>, Martin Mares <mj@ucw.cz>,
dean gaudet <dean@arctic.org>,
Robert Richter <robert.richter@amd.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] x86_64: set cfg_size for AMD Family 10h in case MMCONFIG is used
Date: Thu, 13 Sep 2007 12:31:00 -0700 [thread overview]
Message-ID: <46E98FF4.4060901@zytor.com> (raw)
In-Reply-To: <86802c440709131222v6e819e4ayed27430ba4e61154@mail.gmail.com>
Yinghai Lu wrote:
> On 9/13/07, H. Peter Anvin <hpa@zytor.com> wrote:
>> Yinghai Lu wrote:
>>> BIOS guys also said that fam 10h need mmconfig via eax accessing, may
>>> need OS do sth, so it is safe to stay with MCFG entry for SB like
>>> mcp55...
>>>
>>> but latest kernel already have that workaround to make mmconfig via eax...
>>>
>> This is actually a good point. Since the CPU vendor managed to
>> completely fuck up the operation of MMCONFIG itself on this CPU (it's a
>> *MEMORY REFERENCE*, guys!), it is actually to be expected and prudent
>> that BIOS vendors will drop the MCFG entry. MMCONFIG doesn't actually
>> work on this CPU for any system software which doesn't already know to
>> work around this particular piece of severe braindamage;
>> standards-complicant MMCONFIG isn't supported at all.
>
> if other mmconfig device on x86 is sick of accessing via eax, may need
> to provide one fam10h_pci_mmcfg to be assigned to raw_pci_ops instead
> and leave pci_mmcfg to default behavior ( *MEMORY REFERENCE*).
>
We already have the workaround. WE do. However, you could easily see
why a BIOS vendor would want to leave out the MCFG ACPI info, since fam
10h's mmconfig is broken.
-hpa
next prev parent reply other threads:[~2007-09-13 19:31 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-13 2:21 [PATCH] x86_64: set cfg_size for AMD Family 10h in case MMCONFIG is used Yinghai Lu
2007-09-13 2:17 ` Andrew Morton
2007-09-13 9:47 ` Andi Kleen
2007-09-13 10:47 ` Greg KH
2007-09-13 11:53 ` Andi Kleen
2007-09-13 17:01 ` Yinghai Lu
2007-09-13 17:20 ` H. Peter Anvin
2007-09-13 19:22 ` Yinghai Lu
2007-09-13 19:31 ` H. Peter Anvin [this message]
2007-09-13 20:15 ` Andreas Herrmann
2007-09-13 20:54 ` H. Peter Anvin
2007-09-14 11:21 ` [PATCH] x86_64: set cfg_size for AMD Family 10h in case MMCONFIG Andreas Herrmann
2007-09-14 14:08 ` H. Peter Anvin
2007-09-14 17:28 ` Yinghai Lu
2007-09-14 18:09 ` Yinghai Lu
2007-09-16 3:18 ` [PATCH] x86_64: set cfg_size for AMD Family 10h in case MMCONFIG is used Andi Kleen
2007-09-13 19:52 ` Andreas Herrmann
2007-09-13 20:14 ` 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=46E98FF4.4060901@zytor.com \
--to=hpa@zytor.com \
--cc=ak@suse.de \
--cc=akpm@linux-foundation.org \
--cc=dean@arctic.org \
--cc=greg@kroah.com \
--cc=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mj@ucw.cz \
--cc=robert.richter@amd.com \
--cc=yhlu.kernel@gmail.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