linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: ray.jui@broadcom.com (Ray Jui)
To: linux-arm-kernel@lists.infradead.org
Subject: Device address specific mapping of arm,mmu-500
Date: Tue, 6 Jun 2017 23:20:03 -0700	[thread overview]
Message-ID: <41f12daa-b46c-83f1-9c9f-51de1cadf14f@broadcom.com> (raw)
In-Reply-To: <bc636388-9388-3582-23b0-9f4271cae4b2@arm.com>

Hi Robin,


On 6/6/2017 3:02 AM, Robin Murphy wrote:
> I've currently got some experimental patches pushed out here:
>
>      git://linux-arm.org/linux-rm  iommu/pgtable
>
> So far, there's still one silly bug (which doesn't affect DMA ops usage)
> and an awkward race for non-coherent table walks which will need
> resolving before I have anything to post properly, which I hope will be
> within the next couple of weeks. In the meantime, though, it already
> seems to work well enough in practice, so any feedback is welcome!
>
> Robin.
Excellent! I'm going to find time to test it out (likely next week). 
I'll report back the test result after that.

Thanks,

Ray

  reply	other threads:[~2017-06-07  6:20 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-30  1:18 Device address specific mapping of arm,mmu-500 Ray Jui
2017-05-30 15:14 ` Will Deacon
2017-05-30 16:49   ` Ray Jui
2017-05-30 16:59     ` Marc Zyngier
2017-05-30 17:16       ` Ray Jui
2017-05-30 17:27         ` Marc Zyngier
2017-05-30 22:06           ` Ray Jui
2017-05-31  6:13             ` Ray Jui
2017-05-31 12:44               ` Will Deacon
2017-05-31 17:32                 ` Ray Jui
2017-06-05 18:03                   ` Ray Jui
2017-06-06 10:02                     ` Robin Murphy
2017-06-07  6:20                       ` Ray Jui [this message]
2017-05-30 17:27     ` Robin Murphy

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=41f12daa-b46c-83f1-9c9f-51de1cadf14f@broadcom.com \
    --to=ray.jui@broadcom.com \
    --cc=linux-arm-kernel@lists.infradead.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).