public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] new ia64 kernel patch (relative to 2.5.69)
Date: Mon, 12 May 2003 18:40:18 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590723705733@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590723705721@msgid-missing>

Forgot to mention that I switched the ia64 tree from the PCI-DMA API
to the generic DMA API.  Doesn't affect device drivers, but all I/O
MMU support needs to be updated accordingly.  I already did swiotlb
and the HP SBA I/O MMU support.  I updated that machvec definitions
for all platforms, but didn't try to update the SN-specific
implementation (since I can't test it anyhow).  Updating the SN-files
should be straight-forward: you can look at swiotlb.c and
hp/common/sba_iommu.c for what needs to be done.

The one caveat is that sba_iommu.c for the moment continues to support
only PCI-devices.  This shouldn't be a problem for now, but it would
be nice if someone could fix it so it can work with any device.

While working on this, I started to wonder whether or not a DMA "sync"
operation should imply a memory barrier.  The API documentation is
definitely ambiguous on this point and I didn't go out to look whether
current practice is consistent (I suspect it isn't).  Anyone want to
argue for or against making "sync" a memory barrier?

	--david


      reply	other threads:[~2003-05-12 18:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-10 11:19 [Linux-ia64] new ia64 kernel patch (relative to 2.5.69) David Mosberger
2003-05-12 18:40 ` David Mosberger [this message]

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-105590723705733@msgid-missing \
    --to=davidm@napali.hpl.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