From: Linus Torvalds <torvalds@transmeta.com>
To: Alexander Viro <viro@math.psu.edu>
Cc: "David S. Miller" <davem@redhat.com>, <linux-kernel@vger.kernel.org>
Subject: Re: oops in bk pull (oct 03)
Date: Fri, 4 Oct 2002 20:26:20 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.44.0210042024080.1257-100000@home.transmeta.com> (raw)
In-Reply-To: <Pine.GSO.4.21.0210042314130.21637-100000@weyl.math.psu.edu>
On Fri, 4 Oct 2002, Alexander Viro wrote:
>
> It's getting better. The thing _does_ survive if there is no cacheline
> boundary between the calls of pci_write_config_dword(); otherwise it
> dies on that boundary.
Ok, that definitely clinches it - it's the cache miss coupled with host
bridge confusion that causes it to start fetching from PCI space instead
of RAM (or, more likely just get really confused about it and maybe
fetch from both).
It's always good to understand why someting doesn't work, rather than just
revert it because it breaks inexplicably.
Linus
next prev parent reply other threads:[~2002-10-05 3:18 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-04 20:14 oops in bk pull (oct 03) Paul E. Erkkila
2002-10-04 21:58 ` Linus Torvalds
2002-10-05 0:03 ` Paul E. Erkkila
2002-10-05 0:33 ` Alexander Viro
2002-10-05 0:40 ` Linus Torvalds
2002-10-05 0:51 ` Alexander Viro
2002-10-05 1:02 ` Linus Torvalds
2002-10-05 1:13 ` David S. Miller
2002-10-05 1:27 ` Alexander Viro
2002-10-05 1:41 ` Linus Torvalds
2002-10-05 2:00 ` David S. Miller
2002-10-05 2:22 ` Linus Torvalds
2002-10-05 2:22 ` David S. Miller
2002-10-05 2:00 ` Linus Torvalds
2002-10-05 3:20 ` Alexander Viro
2002-10-05 3:26 ` Linus Torvalds [this message]
2002-10-05 9:35 ` Ivan Kokshaysky
2002-10-05 1:14 ` Alexander Viro
2002-10-05 0:44 ` Alexander Viro
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=Pine.LNX.4.44.0210042024080.1257-100000@home.transmeta.com \
--to=torvalds@transmeta.com \
--cc=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@math.psu.edu \
/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;
as well as URLs for NNTP newsgroup(s).