linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: mst@redhat.com (Michael S. Tsirkin)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] virtio: Try to untangle DMA coherency
Date: Fri, 10 Feb 2017 19:16:10 +0200	[thread overview]
Message-ID: <20170210191409-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20170209183118.GI19397@arm.com>

On Thu, Feb 09, 2017 at 06:31:18PM +0000, Will Deacon wrote:
> On ARM (and other archs such as
> Power), having a mismatch between a cacheable and a non-cacheable mapping
> can result in a loss of coherency between the two (for example, if the
> non-cacheable gues accesses bypass the cache, but the cacheable host
> accesses allocate in the cache).

I guess it's an optimization to avoid cache snoops for non-cacheable accesses?

-- 
MST

  parent reply	other threads:[~2017-02-10 17:16 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-01 12:25 [PATCH] virtio: Try to untangle DMA coherency Robin Murphy
2017-02-01 14:57 ` Will Deacon
2017-02-01 17:58   ` Rob Herring
2017-02-01 18:09 ` Michael S. Tsirkin
2017-02-01 18:27   ` Will Deacon
2017-02-01 19:19     ` Michael S. Tsirkin
2017-02-02 11:26       ` Will Deacon
2017-02-02 13:34         ` Robin Murphy
2017-02-02 16:16           ` Michael S. Tsirkin
2017-02-02 16:39             ` Marc Zyngier
2017-02-02 16:44               ` Michael S. Tsirkin
2017-02-02 16:30           ` Michael S. Tsirkin
2017-02-02 16:40             ` Will Deacon
2017-02-02 16:45               ` Michael S. Tsirkin
2017-02-09 18:17               ` Michael S. Tsirkin
2017-02-09 18:31                 ` Will Deacon
2017-02-09 18:49                   ` Michael S. Tsirkin
2017-02-09 18:54                     ` Ard Biesheuvel
2017-02-09 18:56                     ` Will Deacon
2017-02-10 17:16                   ` Michael S. Tsirkin [this message]
2017-02-13 11:57                     ` Will Deacon
2017-02-08 12:58       ` Alexander Graf
2017-02-09 20:57         ` Michael S. Tsirkin
2017-02-09 22:20           ` Alexander Graf

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=20170210191409-mutt-send-email-mst@kernel.org \
    --to=mst@redhat.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).