From: Grant Grundler <grundler@parisc-linux.org>
To: rubisher <rubisher@scarlet.be>
Cc: linux-parisc <linux-parisc@vger.kernel.org>,
Grant Grundler <grundler@parisc-linux.org>
Subject: Re: ccio_clear_io_tlb() and __raw_write() more question?
Date: Sat, 19 Jan 2008 10:07:05 -0700 [thread overview]
Message-ID: <20080119170705.GC11553@colo.lackof.org> (raw)
In-Reply-To: <JUQMH1$0E837D5F7A1526B30DCF5BF1A8BE2816@scarlet.be>
On Wed, Jan 16, 2008 at 01:53:25PM +0100, rubisher wrote:
> Without doc I guess that this call to WRITE_U32() is supposed to do what it
> name says: i.e purge a TLB entry?
...
> puting all those stuff togther: for CPU, WRITE_U32 (aka __raw_writel), just
> write something at some virtual address, right?
>
> So my worry is that this data write could be cached and btw the actual
> CMD_TLB_PURGE operation could be delay untill this entry would be purged?
Willy is correct - writes to this IO space (0xf0000000) address is uncached.
While the write is "posted", it's a fairly short path to the IOMMU (1 hop).
Since this is the "unmap path" I don't expect any race conditions since
we would have to call map using the same mapping right away in order to
pickup the stale IOTLB entry. We avoid this race by allocating IO Pdir
entries in a "circular" fashion (start at bottom and work through
the entire resource bit map).
hth,
grant
next prev parent reply other threads:[~2008-01-19 17:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-16 12:53 ccio_clear_io_tlb() and __raw_write() more question? rubisher
2008-01-16 13:03 ` Matthew Wilcox
2008-01-19 17:07 ` Grant Grundler [this message]
2008-01-20 10:06 ` rubisher
2008-01-20 19:06 ` Grant Grundler
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=20080119170705.GC11553@colo.lackof.org \
--to=grundler@parisc-linux.org \
--cc=linux-parisc@vger.kernel.org \
--cc=rubisher@scarlet.be \
/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.