From: lsorense@csclub.uwaterloo.ca (Lennart Sorensen)
To: takada <takada@mbf.nifty.com>
Cc: rdreier@cisco.com, pcnet32@verizon.net, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: MediaGX/GeodeGX1 requires X86_OOSTORE.
Date: Tue, 20 Feb 2007 09:48:23 -0500 [thread overview]
Message-ID: <20070220144823.GN7585@csclub.uwaterloo.ca> (raw)
In-Reply-To: <20070220.203413.260790539.takada@mbf.nifty.com>
On Tue, Feb 20, 2007 at 08:34:13PM +0900, takada wrote:
> I posted with 2.6.20 + enabled X86_OOSTORE.
> The clflush sze line is in /proc/cpuinfo. but clfush is not in flags line.
>
> BTW, can we use WBINVD instruction? I tested compile only.
> Do you know a method to change dynamically without #ifdef when it works
> with MediaGX/GeodeGX.
>
> diff -Narup a/include/asm-i386/io.h b/include/asm-i386/io.h
> --- a/include/asm-i386/io.h 2007-02-20 16:23:25.000000000 +0900
> +++ b/include/asm-i386/io.h 2007-02-20 17:07:14.000000000 +0900
> @@ -232,7 +232,19 @@ static inline void memcpy_toio(volatile
> * 2. Accidentally out of order processors (PPro errata #51)
> */
>
> -#if defined(CONFIG_X86_OOSTORE) || defined(CONFIG_X86_PPRO_FENCE)
> +#ifdef CONFIG_MGEODEGX1
> +
> +static inline void dma_flush_cache(void)
> +{
> + __asm__ __volatile__ ("wbinvd": : :"memory");
> +}
> +
> +#define dma_cache_inv(_start,_size) dma_flush_cache()
> +#define dma_cache_wback(_start,_size) dma_flush_cache()
> +#define dma_cache_wback_inv(_start,_size) dma_flush_cache()
> +#define flush_write_buffers()
> +
> +#elif defined(CONFIG_X86_OOSTORE) || defined(CONFIG_X86_PPRO_FENCE)
>
> static inline void flush_write_buffers(void)
> {
> -
Well it is starting to look like it isn't a caching issue, but more
likely an issue of which order writes are performed in. I think the MAC
might be seeing the ownership bit change before the rest of the
descriptor, which shouldn't happen. With X86_OOSTORE, wmb() is called
between setting the fields in the descriptor and setting the ownership
bit to the MAC. I still have to investigate a bit more to find out for
sure, but that could certainly explain why X86_OOSTORE makes the problem
become much less frequent. It doesn't completely elliminate it though.
Of course maybe there are two different problems with the same symptoms.
--
Len Sorensen
next prev parent reply other threads:[~2007-02-20 14:48 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <32943920.1119801171642884331.JavaMail.root@vms226.mailsrvcs.net>
[not found] ` <20070216172110.GC7582@csclub.uwaterloo.ca>
[not found] ` <20070216202300.GD7585@csclub.uwaterloo.ca>
[not found] ` <20070216210157.GE7585@csclub.uwaterloo.ca>
[not found] ` <20070216222728.GF7585@csclub.uwaterloo.ca>
2007-02-16 22:48 ` MediaGX/GeodeGX1 requires X86_OOSTORE. (Was: Re: Strange connection slowdown on pcnet32) Lennart Sorensen
2007-02-17 0:00 ` Lennart Sorensen
2007-02-17 14:11 ` MediaGX/GeodeGX1 requires X86_OOSTORE takada
2007-02-17 15:07 ` Lennart Sorensen
2007-02-19 14:55 ` Lennart Sorensen
2007-02-19 19:48 ` Roland Dreier
2007-02-19 19:57 ` Lennart Sorensen
2007-02-19 23:56 ` takada
2007-02-20 0:02 ` Lennart Sorensen
2007-02-20 11:34 ` takada
2007-02-20 14:48 ` Lennart Sorensen [this message]
2007-03-15 5:39 ` takada
2007-03-15 17:31 ` Lennart Sorensen
2007-03-17 13:08 ` takada
2007-03-19 18:23 ` Lennart Sorensen
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=20070220144823.GN7585@csclub.uwaterloo.ca \
--to=lsorense@csclub.uwaterloo.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pcnet32@verizon.net \
--cc=rdreier@cisco.com \
--cc=takada@mbf.nifty.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
all inboxes | Powered by JetHome®