From: Gururaj Ananthateerta <gururaj@cup.hp.com>
To: linux-ia64@vger.kernel.org
Subject: [Linux-ia64] Weird PIO behavior.
Date: Wed, 17 Oct 2001 19:03:14 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590698805362@msgid-missing> (raw)
I am experiencing some bizarre problem when I try to do PIO (memory writes) to
MMIO space for a 64-bits
addressing capable PCI NIC on a Lion platform (The one I have is a 2 processors,
733 MHz Itanium, 1GB RAM).
This problem is on HP-UX and not I haven't tried on Linux (for which I need to
port my driver).
Problem
-----
When multiple PIO writes are in flight, there is something that is
happening that caused the values to get interchanged.
Something like this below.
Notations
------
Ri = Register i
Vi = Value i intended to be written on Register Ri.
If the PIO writes are
R1 ------- V1
R2 --------V2
R3 --------V3
The traces on the PCI analyzer shows something like this
R1 --------V2
R2--------V1
R3--------V3
The problem is seen very arbitrary and can be easily reproduced.
Has anyone observed this type of problem or have any clue why this might be
happening.
I somewhere bumped into memory fence and sync instruction. Do they help me in any
way?.
Thanks for your help
Guru
reply other threads:[~2001-10-17 19:03 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=marc-linux-ia64-105590698805362@msgid-missing \
--to=gururaj@cup.hp.com \
--cc=linux-ia64@vger.kernel.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