From: Mark Rutland <mark.rutland@arm.com>
To: Rob Clark <robdclark@chromium.org>
Cc: Christoph Hellwig <hch@lst.de>, Rob Clark <robdclark@gmail.com>,
dri-devel <dri-devel@lists.freedesktop.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <maxime.ripard@bootlin.com>,
Sean Paul <sean@poorly.run>, David Airlie <airlied@linux.ie>,
Daniel Vetter <daniel@ffwll.ch>,
Allison Randal <allison@lohutok.net>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Thomas Gleixner <tglx@linutronix.de>,
linux-arm-kernel@lists.infradead.org,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/2] drm: add cache support for arm64
Date: Tue, 6 Aug 2019 15:34:57 +0100 [thread overview]
Message-ID: <20190806143457.GF475@lakrids.cambridge.arm.com> (raw)
In-Reply-To: <CAJs_Fx6eh1w7c=crMoD5XyEOMzP6orLhqUewErE51cPGYmObBQ@mail.gmail.com>
On Tue, Aug 06, 2019 at 07:11:41AM -0700, Rob Clark wrote:
> On Tue, Aug 6, 2019 at 1:48 AM Christoph Hellwig <hch@lst.de> wrote:
> >
> > This goes in the wrong direction. drm_cflush_* are a bad API we need to
> > get rid of, not add use of it. The reason for that is two-fold:
> >
> > a) it doesn't address how cache maintaince actually works in most
> > platforms. When talking about a cache we three fundamental operations:
> >
> > 1) write back - this writes the content of the cache back to the
> > backing memory
> > 2) invalidate - this remove the content of the cache
> > 3) write back + invalidate - do both of the above
>
> Agreed that drm_cflush_* isn't a great API. In this particular case
> (IIUC), I need wb+inv so that there aren't dirty cache lines that drop
> out to memory later, and so that I don't get a cache hit on
> uncached/wc mmap'ing.
Is there a cacheable alias lying around (e.g. the linear map), or are
these addresses only mapped uncached/wc?
If there's a cacheable alias, performing an invalidate isn't sufficient,
since a CPU can allocate a new (clean) entry at any point in time (e.g.
as a result of prefetching or arbitrary speculation).
Thanks,
Mark.
next prev parent reply other threads:[~2019-08-06 14:35 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-05 21:14 [PATCH 1/2] drm: add cache support for arm64 Rob Clark
2019-08-05 21:14 ` [PATCH 2/2] drm/msm: use drm_cache when available Rob Clark
2019-08-06 8:48 ` [PATCH 1/2] drm: add cache support for arm64 Christoph Hellwig
2019-08-06 9:38 ` Daniel Vetter
2019-08-06 11:38 ` Christoph Hellwig
2019-08-06 14:11 ` Rob Clark
2019-08-06 14:34 ` Mark Rutland [this message]
2019-08-06 16:31 ` Rob Clark
2019-08-07 12:38 ` Mark Rutland
2019-08-07 16:15 ` Rob Clark
2019-08-07 16:49 ` Mark Rutland
2019-08-07 17:30 ` Rob Clark
2019-08-08 7:59 ` Christoph Hellwig
2019-08-08 16:44 ` Rob Clark
2019-08-09 8:18 ` Christoph Hellwig
2019-08-08 7:58 ` Christoph Hellwig
2019-08-08 10:20 ` Mark Rutland
2019-08-08 10:24 ` Mark Rutland
2019-08-08 10:32 ` Will Deacon
2019-08-08 7:53 ` Christoph Hellwig
2019-08-06 15:50 ` Christoph Hellwig
2019-08-06 16:23 ` Rob Clark
2019-08-06 16:26 ` Rob Clark
2019-08-07 6:25 ` Christoph Hellwig
2019-08-07 8:48 ` Daniel Vetter
2019-08-08 9:55 ` Christoph Hellwig
2019-08-08 11:58 ` Daniel Vetter
2019-08-09 8:14 ` Christoph Hellwig
2019-08-07 16:09 ` Rob Clark
2019-08-08 10:00 ` Christoph Hellwig
2019-08-08 16:32 ` Rob Clark
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=20190806143457.GF475@lakrids.cambridge.arm.com \
--to=mark.rutland@arm.com \
--cc=airlied@linux.ie \
--cc=allison@lohutok.net \
--cc=catalin.marinas@arm.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=gregkh@linuxfoundation.org \
--cc=hch@lst.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=maxime.ripard@bootlin.com \
--cc=robdclark@chromium.org \
--cc=robdclark@gmail.com \
--cc=sean@poorly.run \
--cc=tglx@linutronix.de \
--cc=will@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;
as well as URLs for NNTP newsgroup(s).