From: Jesse Barnes <jbarnes@sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] pio barriers
Date: Tue, 11 Dec 2001 00:55:48 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590698805678@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590698805669@msgid-missing>
On Mon, Dec 10, 2001 at 04:44:42PM -0800, David Mosberger wrote:
> Yes, I realize that, but it's not the CPU that's reordering the access
> so mf doesn't help and mf.a really doesn't guarantee anything either
> (though it may on your platform).
Yeah, that's too bad. On MIPS we've got 'sync', which is implemented
to do a pio flush. Apparently IA64 doesn't have a nice way to do
something similiar though, so oh well.
> Invasive, yes. But on some platforms there may be no other way of
> enforcing order. Perhaps what would be best would be a macro that
> takes a device address as an argument. Depending on platform, you
> could then do a dummy read from this address or use a special
> instruction, such as mf.a, to enforce order.
Can you think of other platforms that might need a device argument to
a potential pio barrier macro? I was tentatively thinking of
implementing it without any arguments, but I suppose we could just
ignore any arguments for our platform...
Thanks,
Jesse
next prev parent reply other threads:[~2001-12-11 0:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-10 22:47 [Linux-ia64] pio barriers Jesse Barnes
2001-12-10 22:57 ` Jack Steiner
2001-12-10 23:00 ` Jesse Barnes
2001-12-10 23:58 ` David Mosberger
2001-12-11 0:23 ` Jesse Barnes
2001-12-11 0:44 ` David Mosberger
2001-12-11 0:55 ` Jesse Barnes [this message]
2001-12-11 5:30 ` David Mosberger
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-105590698805678@msgid-missing \
--to=jbarnes@sgi.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.