From: Christoph Hellwig <hch@infradead.org>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: "Jason A. Donenfeld" <Jason@zx2c4.com>,
bigeasy@linutronix.de, linux-kernel@vger.kernel.org,
dri-devel@lists.freedesktop.org,
Christoph Hellwig <hch@infradead.org>,
stable@vger.kernel.org, tglx@linutronix.de,
intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH] drm/i915: check to see if SIMD registers are available before using SIMD
Date: Mon, 4 May 2020 09:03:14 -0700 [thread overview]
Message-ID: <20200504160314.GA26373@infradead.org> (raw)
In-Reply-To: <158853721918.8377.18286963845226122104@build.alporthouse.com>
On Sun, May 03, 2020 at 09:20:19PM +0100, Chris Wilson wrote:
> > Err, why does i915 implements its own uncached memcpy instead of relying
> > on core functionality to start with?
>
> What is this core functionality that provides movntqda?
A sensible name might be memcpy_uncached or mempcy_nontemporal.
But the important point is that this should be arch code with a common
fallback rather than hacking it up in drivers.
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2020-05-04 17:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-30 22:10 [Intel-gfx] [PATCH] drm/i915: check to see if SIMD registers are available before using SIMD Jason A. Donenfeld
2020-05-01 10:42 ` Sebastian Andrzej Siewior
2020-05-01 11:34 ` David Laight
2020-05-01 21:54 ` Jason A. Donenfeld
2020-05-01 17:19 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for " Patchwork
2020-05-01 17:43 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2020-05-01 18:07 ` [Intel-gfx] [PATCH] " Christoph Hellwig
2020-05-01 21:55 ` Jason A. Donenfeld
2020-05-03 20:20 ` Chris Wilson
2020-05-04 16:03 ` Christoph Hellwig [this message]
2020-05-04 16:15 ` David Laight
2020-05-01 20:26 ` [Intel-gfx] ✓ Fi.CI.IGT: success for " Patchwork
2020-05-03 20:30 ` [Intel-gfx] [PATCH] " Chris Wilson
2020-05-03 20:35 ` Jason A. Donenfeld
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=20200504160314.GA26373@infradead.org \
--to=hch@infradead.org \
--cc=Jason@zx2c4.com \
--cc=bigeasy@linutronix.de \
--cc=chris@chris-wilson.co.uk \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=tglx@linutronix.de \
/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