From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: xen-devel <xen-devel@lists.xenproject.org>,
Keir Fraser <keir@xen.org>,
Aravind Gopalakrishnan <aravind.gopalakrishnan@amd.com>,
suravee.suthikulpanit@amd.com
Subject: Re: [PATCH] x86emul: support clzero
Date: Thu, 24 Sep 2015 12:59:01 +0100 [thread overview]
Message-ID: <5603E585.2010907@citrix.com> (raw)
In-Reply-To: <5603CA4C02000078000A51F3@prv-mh.provo.novell.com>
On 24/09/15 09:02, Jan Beulich wrote:
>>>> On 23.09.15 at 19:37, <andrew.cooper3@citrix.com> wrote:
>> On 22/09/15 14:06, Jan Beulich wrote:
>>> ... in anticipation of this possibly going to get used by guests for
>>> basic thinks like memset() or clearing or pages.
>>>
>>> Since the emulation doesn't use clzero itself, checking the guest's
>>> CPUID for the feature to be exposed is (intentionally) being avoided
>>> here. All that's required is sensible guest side data for the clflush
>>> line size.
>>>
>>> Signed-off-by: Jan Beulich <jbeulich@suse.com>
>> Where have you found this instruction? Googling, I have found a
>> presentation talking about it being new in the new AMD Zen cores, but I
>> still can't locate any technical documentation on the matter.
> Sadly no technical documentation so far, despite me pinging for it
> after the respective binutils patch
> (https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;a=commitdiff;h=029f3522619e8b77a7b848be23f4c13e50087d8b)
> got posted and went in.
While I don't see an obvious issue with your patch, I can't claim to
have reviewed it without some documentation to refer to.
Aravind/Suravee: Any ideas when the AMD manuals might be updated to
include this?
~Andrew
next prev parent reply other threads:[~2015-09-24 11:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-22 13:06 [PATCH] x86emul: support clzero Jan Beulich
2015-09-23 17:37 ` Andrew Cooper
2015-09-24 8:02 ` Jan Beulich
2015-09-24 11:59 ` Andrew Cooper [this message]
2015-09-24 12:13 ` Jan Beulich
2015-10-08 10:26 ` Jan Beulich
2016-01-11 15:55 ` Aravind Gopalakrishnan
2016-01-13 15:10 ` Andrew Cooper
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=5603E585.2010907@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=JBeulich@suse.com \
--cc=aravind.gopalakrishnan@amd.com \
--cc=keir@xen.org \
--cc=suravee.suthikulpanit@amd.com \
--cc=xen-devel@lists.xenproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.