From: Xin Li <xin3.li@intel.com>
To: qemu-devel@nongnu.org
Cc: kvm@vger.kernel.org, richard.henderson@linaro.org,
pbonzini@redhat.com, eduardo@habkost.net, seanjc@google.com,
chao.gao@intel.com, hpa@zytor.com, xiaoyao.li@intel.com,
weijiang.yang@intel.com
Subject: [PATCH v2 0/4] target/i386: add support for FRED
Date: Mon, 2 Oct 2023 00:23:09 -0700 [thread overview]
Message-ID: <20231002072313.17603-1-xin3.li@intel.com> (raw)
This patch set adds support for the Intel flexible return and event delivery
(FRED) architecture to allow Qemu to run KVM guests with FRED enabled.
The FRED architecture defines simple new transitions that change privilege
level (ring transitions). The FRED architecture was designed with the
following goals:
1) Improve overall performance and response time by replacing event delivery
through the interrupt descriptor table (IDT event delivery) and event
return by the IRET instruction with lower latency transitions.
2) Improve software robustness by ensuring that event delivery establishes
the full supervisor context and that event return establishes the full
user context.
Search for the latest FRED spec in most search engines with this search pattern:
site:intel.com FRED (flexible return and event delivery) specification
---
Changelog
v2:
- Add VMX nested-exception support to scripts/kvm/vmxcap (Paolo Bonzini).
- Move FRED MSRs from basic x86_cpu part to .subsections part (Weijiang Yang).
Xin Li (4):
target/i386: add support for FRED in CPUID enumeration
target/i386: mark CR4.FRED not reserved
target/i386: enumerate VMX nested-exception support
target/i386: Add get/set/migrate support for FRED MSRs
scripts/kvm/vmxcap | 1 +
target/i386/cpu.c | 7 +++++-
target/i386/cpu.h | 43 +++++++++++++++++++++++++++++++++-
target/i386/kvm/kvm.c | 54 +++++++++++++++++++++++++++++++++++++++++++
target/i386/machine.c | 29 +++++++++++++++++++++++
5 files changed, 132 insertions(+), 2 deletions(-)
--
2.34.1
next reply other threads:[~2023-10-02 7:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-02 7:23 Xin Li [this message]
2023-10-02 7:23 ` [PATCH v2 1/4] target/i386: add support for FRED in CPUID enumeration Xin Li
2023-10-02 7:23 ` [PATCH v2 2/4] target/i386: mark CR4.FRED not reserved Xin Li
2023-10-02 7:23 ` [PATCH v2 3/4] target/i386: enumerate VMX nested-exception support Xin Li
2023-10-02 7:23 ` [PATCH v2 4/4] target/i386: Add get/set/migrate support for FRED MSRs Xin Li
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=20231002072313.17603-1-xin3.li@intel.com \
--to=xin3.li@intel.com \
--cc=chao.gao@intel.com \
--cc=eduardo@habkost.net \
--cc=hpa@zytor.com \
--cc=kvm@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=seanjc@google.com \
--cc=weijiang.yang@intel.com \
--cc=xiaoyao.li@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).