linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Becky Bruce <beckyb@kernel.crashing.org>
Cc: linuxppc-dev list <linuxppc-dev@ozlabs.org>
Subject: Re: [PATCH] powerpc: Fix swiotlb ops for ppc64
Date: Tue, 13 Dec 2011 15:27:07 +1100	[thread overview]
Message-ID: <1323750427.19891.59.camel@pasglop> (raw)
In-Reply-To: <4BCA9D4A-4284-4DE8-95B9-D5DBA9254CC1@kernel.crashing.org>

On Mon, 2011-12-12 at 21:55 -0600, Becky Bruce wrote:
> 1) dma_direct_alloc_coherent strips GFP_HIGHMEM out of the flags field
> when calling the actual allocator and the iotlb version does not.  I
> don't know how much this matters - I did a quick grep and I don't see
> any users that specify that, but somebody went through the trouble of
> putting it in there in the first place and without knowing why I
> wasn't willing to get rid of it.  Now, since my patch it looks like
> someone added a VM_BUG_ON into __get_free_pages() if GFP_HIGHMEM so
> this would get caught.  However, I don't know if we really want to
> throw a bug there.
> 
> 2)  The iotlb code doesn't deal with the !coherent parts like 8xx.  We
> can work around that by setting up the dma_ops differently for that
> case instead.

Does the rest of it handle them ? I mean swiotlb_map_sg_attrs etc...

If not then it's broken anyway so may as well not care for now.

Cheers,
Ben.

  reply	other threads:[~2011-12-13  4:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-07 17:19 [PATCH] powerpc: Fix swiotlb ops for ppc64 Kumar Gala
2011-12-08  3:23 ` Benjamin Herrenschmidt
2011-12-08  5:46   ` Kumar Gala
2011-12-13  3:55     ` Becky Bruce
2011-12-13  4:27       ` Benjamin Herrenschmidt [this message]
2011-12-14  2:53         ` Becky Bruce
2011-12-14  3:00           ` Benjamin Herrenschmidt

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=1323750427.19891.59.camel@pasglop \
    --to=benh@kernel.crashing.org \
    --cc=beckyb@kernel.crashing.org \
    --cc=linuxppc-dev@ozlabs.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;
as well as URLs for NNTP newsgroup(s).