From: Olivier Galibert <galibert@pobox.com>
To: Andi Kleen <ak@suse.de>,
linux-pci@atrey.karlin.mff.cuni.cz,
"Hack inc." <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@osdl.org>
Subject: Re: [PATCH] PCI MMConfig: Detect and support the E7520 and the 945G/GZ/P/PL
Date: Fri, 1 Dec 2006 01:19:01 +0100 [thread overview]
Message-ID: <20061201001901.GA11057@dspnet.fr.eu.org> (raw)
In-Reply-To: <20061127202406.GA90483@dspnet.fr.eu.org>
On Mon, Nov 27, 2006 at 09:24:06PM +0100, Olivier Galibert wrote:
> On Mon, Nov 27, 2006 at 08:07:48PM +0100, Andi Kleen wrote:
> > Is that with just the code movement patch or your feature patch
> > added too? If the later can you test it with only code movement
> > (and compare against vanilla kernel). at least code movement
> > only should behave exactly the same as unpatched kernel.
>
> You misread. Unpatched kernel does not work. That's why I gave the
> git reference of the kernel too. Patched kernel does not work either,
> unsurprisingly (bios gives correct tables on that box).
Ok, I'm trying to debug it, and it's a pain. It's a timing issue,
mmcfg write accesses are too slow for something. The get_base_addr()
call is enough to slow things down too much, which explains why the
fundamentally simpler x86-64 code works without a hitch.
Finding out what it is too slow for, though, is an interesting
proposition. It's not entirely obvious it is actually related to the
sata accesses.
OG.
prev parent reply other threads:[~2006-12-01 0:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-23 19:51 Olivier Galibert
2006-11-23 19:57 ` Arjan van de Ven
2006-11-23 20:40 ` Matthew Wilcox
2006-11-23 20:44 ` Olivier Galibert
2006-11-25 19:34 ` Andi Kleen
2006-11-25 20:51 ` Olivier Galibert
2006-11-25 20:59 ` Andi Kleen
2006-11-26 13:15 ` Olivier Galibert
2006-11-26 19:28 ` Andi Kleen
2006-11-27 19:03 ` Olivier Galibert
2006-11-27 19:07 ` Andi Kleen
2006-11-27 20:24 ` Olivier Galibert
2006-12-01 0:19 ` Olivier Galibert [this message]
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=20061201001901.GA11057@dspnet.fr.eu.org \
--to=galibert@pobox.com \
--cc=ak@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@atrey.karlin.mff.cuni.cz \
--cc=torvalds@osdl.org \
/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
Powered by JetHome