From: Jesse Barnes <jbarnes@sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] pio barriers
Date: Mon, 10 Dec 2001 23:00:12 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590698805672@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590698805669@msgid-missing>
Actually, I was thinking that for most platforms, mf.a should do a
'flushbus' (i.e. act as a barrier for all previous pio reads/writes).
Of course, for SN, we'll need to do other stuff too, so I'd like to
make a machine vector.
Jesse
On Mon, Dec 10, 2001 at 04:57:33PM -0600, Jack Steiner wrote:
> There is a macro in io.h
>
> #define __ia64_mf_a() __asm__ __volatile__ ("mf.a" ::: "memory")
>
>
> However, it is not clear to me when a mf.a is actually required?? Does
> anyone have an opinion?? I dont see any clear need for it. Seems like places
> where we might want to use it actually require a flushbus().
next prev parent reply other threads:[~2001-12-10 23:00 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 [this message]
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
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-105590698805672@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.