linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: hch@infradead.org (Christoph Hellwig)
To: linux-arm-kernel@lists.infradead.org
Subject: [Linaro-mm-sig] noveau vs arm dma ops
Date: Thu, 26 Apr 2018 02:24:22 -0700	[thread overview]
Message-ID: <20180426092422.GA26825@infradead.org> (raw)
In-Reply-To: <CAKMK7uG9R6paoP4BmvqDVUP_4Db4Dz8MSXeLwUBMYaORa5-kVw@mail.gmail.com>

On Thu, Apr 26, 2018 at 11:20:44AM +0200, Daniel Vetter wrote:
> The above is already what we're implementing in i915, at least
> conceptually (it all boils down to clflush instructions because those
> both invalidate and flush).

The clwb instruction that just writes back dirty cache lines might
be very interesting for the x86 non-coherent dma case.  A lot of
architectures use their equivalent to prepare to to device transfers.

> One architectural guarantee we're exploiting is that prefetched (and
> hence non-dirty) cachelines will never get written back, but dropped
> instead.

And to make this work you'll need exactly this guarantee.

  reply	other threads:[~2018-04-26  9:24 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <f1100bd6-dd98-55a9-a92f-1cad919f235f@amd.com>
     [not found] ` <20180420124625.GA31078@infradead.org>
     [not found]   ` <20180420152111.GR31310@phenom.ffwll.local>
     [not found]     ` <20180424184847.GA3247@infradead.org>
     [not found]       ` <CAKMK7uFL68pu+-9LODTgz+GQYvxpnXOGhxfz9zorJ_JKsPVw2g@mail.gmail.com>
     [not found]         ` <20180425054855.GA17038@infradead.org>
     [not found]           ` <CAKMK7uEFitkNQrD6cLX5Txe11XhVO=LC4YKJXH=VNdq+CY=DjQ@mail.gmail.com>
     [not found]             ` <CAKMK7uFx=KB1vup=WhPCyfUFairKQcRR4BEd7aXaX1Pj-vj3Cw@mail.gmail.com>
     [not found]               ` <20180425064335.GB28100@infradead.org>
     [not found]                 ` <20180425074151.GA2271@ulmo>
2018-04-25  8:54                   ` noveau vs arm dma ops Christoph Hellwig
2018-04-25  9:25                     ` Russell King - ARM Linux
2018-04-25 10:04                     ` Daniel Vetter
2018-04-25 15:33                       ` Christoph Hellwig
2018-04-25 21:35                         ` Daniel Vetter
2018-04-25 23:26                           ` Russell King - ARM Linux
2018-04-26  9:17                             ` Daniel Vetter
2018-04-26  9:09                           ` Christoph Hellwig
2018-04-26  9:45                             ` Daniel Vetter
2018-04-26 11:12                             ` Russell King - ARM Linux
2018-04-25 22:54                         ` Russell King - ARM Linux
2018-04-26  9:13                           ` Christoph Hellwig
2018-04-26  9:20                           ` [Linaro-mm-sig] " Daniel Vetter
2018-04-26  9:24                             ` Christoph Hellwig [this message]
2018-04-26  9:39                               ` Daniel Vetter

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=20180426092422.GA26825@infradead.org \
    --to=hch@infradead.org \
    --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).