From: Yang Weijiang <weijiang.yang@intel.com>
To: qemu-devel@nongnu.org, pbonzini@redhat.com, rkrcmar@redhat.com,
linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
mst@redhat.com, yu-cheng.yu@intel.com, yi.z.zhang@intel.com,
hjl.tools@gmail.com
Cc: Yang Weijiang <weijiang.yang@intel.com>
Subject: [Qemu-devel] [PATCH 0/4] This patch-set is to enable Guest CET support.
Date: Wed, 26 Dec 2018 16:25:16 +0800 [thread overview]
Message-ID: <cover.1545806972.git.weijiang.yang@intel.com> (raw)
Control-flow Enforcement Technology (CET) provides protection against
return/jump-oriented programming (ROP) attacks. To make kvm Guest OS
own the capability, this patch-set is required. It enables CET related
CPUID report and xsaves/xrstors support etc in qemu.
Yang Weijiang (4):
Add CET xsaves/xrstors related macros and structures.
Add CET SHSTK and IBT CPUID feature-word definitions.
Add hepler functions for CPUID xsave area size calculation.
Report CPUID xsave area support for CET.
target/i386/cpu.c | 67 ++++++++++++++++++++++++++++++++++++++++++++---
target/i386/cpu.h | 36 ++++++++++++++++++++++++-
2 files changed, 99 insertions(+), 4 deletions(-)
--
2.17.1
next reply other threads:[~2018-12-26 8:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-26 8:25 Yang Weijiang [this message]
2018-12-26 8:25 ` [Qemu-devel] [PATCH 1/4] Add CET xsaves/xrstors related macros and structures Yang Weijiang
2018-12-26 8:25 ` [Qemu-devel] [PATCH 2/4] Add CET SHSTK and IBT CPUID feature-word definitions Yang Weijiang
2018-12-28 14:25 ` Paolo Bonzini
2018-12-29 15:26 ` Yang Weijiang
2018-12-26 8:25 ` [Qemu-devel] [PATCH 3/4] Add hepler functions for CPUID xsave area size calculation Yang Weijiang
2019-01-08 16:11 ` Christophe de Dinechin
2018-12-26 8:25 ` [Qemu-devel] [PATCH 4/4] Report CPUID xsave area support for CET Yang Weijiang
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=cover.1545806972.git.weijiang.yang@intel.com \
--to=weijiang.yang@intel.com \
--cc=hjl.tools@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rkrcmar@redhat.com \
--cc=yi.z.zhang@intel.com \
--cc=yu-cheng.yu@intel.com \
/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).