From: "H. Peter Anvin" <h.peter.anvin@intel.com>
To: Ross Zwisler <ross.zwisler@linux.intel.com>,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
Ingo Molnar <mingo@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH] drm: Missed clflushopt in drm_clflush_virt_range
Date: Thu, 15 May 2014 07:37:32 -0700 [thread overview]
Message-ID: <5374D12C.9030400@intel.com> (raw)
In-Reply-To: <20140515123846.GQ8790@phenom.ffwll.local>
On 05/15/2014 05:38 AM, Daniel Vetter wrote:
> On Wed, May 14, 2014 at 09:41:12AM -0600, Ross Zwisler wrote:
>> With this commit:
>>
>> 2a0788dc9bc4 x86: Use clflushopt in drm_clflush_virt_range
>>
>> If clflushopt is available on the system, we use it instead of clflush
>> in drm_clflush_virt_range. There were two calls to clflush in this
>> function, but only one was changed to clflushopt. This patch changes
>> the other clflush call to clflushopt.
>>
>> Signed-off-by: Ross Zwisler <ross.zwisler@linux.intel.com>
>> Reported-by: Matthew Wilcox <matthew.r.wilcox@intel.com>
>>
>> Cc: David Airlie <airlied@linux.ie>
>> Cc: dri-devel@lists.freedesktop.org
>> Cc: H Peter Anvin <h.peter.anvin@intel.com>
>> Cc: Ingo Molnar <mingo@kernel.org>
>> Cc: Thomas Gleixner <tglx@linutronix.de>
>
> Picked to my topic/core-stuff drm branch so it doesn't get lost.
> -Daniel
>
Does this mean you're picking this up, or do you want me to put it into
-tip?
-hpa
next prev parent reply other threads:[~2014-05-15 14:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-14 15:41 [PATCH] drm: Missed clflushopt in drm_clflush_virt_range Ross Zwisler
2014-05-15 12:38 ` Daniel Vetter
2014-05-15 14:37 ` H. Peter Anvin [this message]
2014-05-15 20:40 ` 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=5374D12C.9030400@intel.com \
--to=h.peter.anvin@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=ross.zwisler@linux.intel.com \
--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