From: Wei Liu <wei.liu2@citrix.com>
To: Kyle Huey <me@kylehuey.com>
Cc: Kevin Tian <kevin.tian@intel.com>, Wei Liu <wei.liu2@citrix.com>,
Jun Nakajima <jun.nakajima@intel.com>,
Andrew Cooper <andrew.cooper3@citrix.com>,
xen-devel@lists.xen.org, Jan Beulich <JBeulich@suse.com>,
Robert O'Callahan <robert@ocallahan.org>
Subject: Re: [PATCH v5] x86/Intel: virtualize support for cpuid faulting
Date: Thu, 20 Oct 2016 15:15:32 +0100 [thread overview]
Message-ID: <20161020141532.GB3543@citrix.com> (raw)
In-Reply-To: <20161020134428.28705-1-khuey@kylehuey.com>
On Thu, Oct 20, 2016 at 06:44:26AM -0700, Kyle Huey wrote:
> rr (http://rr-project.org/), a Linux userspace record-and-replay reverse-
> execution debugger, would like to trap and emulate the CPUID instruction.
> This would allow us to a) mask away certain hardware features that rr does
> not support (e.g. RDRAND) and b) enable trace portability across machines
> by providing constant results. Patches for support in the Linux kernel are in
> flight, and we'd like to be able to use this feature on virtualized Linux
> instances as well.
>
> Changes since v4:
> - Renamed cpuid_fault to cpuid_faulting across the patch.
> - Various style nits.
> - Added Reviewed-by Kevin Tian.
>
Release-acked-by: Wei Liu <wei.liu2@citrix.com>
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-10-20 14:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-20 13:44 [PATCH v5] x86/Intel: virtualize support for cpuid faulting Kyle Huey
2016-10-20 13:44 ` [PATCH v5 1/2] x86/Intel: Expose cpuid_faulting_enabled so it can be used elsewhere Kyle Huey
2016-10-20 13:44 ` [PATCH v5 2/2] x86/Intel: virtualize support for cpuid faulting Kyle Huey
2016-10-20 14:04 ` Andrew Cooper
2016-10-20 14:15 ` Wei Liu [this message]
2016-10-20 16:19 ` [PATCH v5] " Andrew Cooper
2016-10-21 15:51 ` Kyle Huey
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=20161020141532.GB3543@citrix.com \
--to=wei.liu2@citrix.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=jun.nakajima@intel.com \
--cc=kevin.tian@intel.com \
--cc=me@kylehuey.com \
--cc=robert@ocallahan.org \
--cc=xen-devel@lists.xen.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.