From: "Tian, Kevin" <kevin.tian@intel.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>,
Xen-devel <xen-devel@lists.xen.org>
Cc: Sergey Dyasli <sergey.dyasli@citrix.com>,
Wei Liu <wei.liu2@citrix.com>,
"Nakajima, Jun" <jun.nakajima@intel.com>,
Jan Beulich <JBeulich@suse.com>
Subject: Re: [PATCH 3/4] x86/vvmx: INVVPID instructions should be handled at by L1
Date: Tue, 30 Oct 2018 07:12:30 +0000 [thread overview]
Message-ID: <AADFC41AFE54684AB9EE6CBC0274A5D19BE2BBAE@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <1540481933-20666-1-git-send-email-andrew.cooper3@citrix.com>
> From: Andrew Cooper [mailto:andrew.cooper3@citrix.com]
> Sent: Thursday, October 25, 2018 11:39 PM
>
> Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com>
Acked-by: Kevin Tian <kevin.tian@intel.com>
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2018-10-30 7:12 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-25 15:36 [PATCH 0/4] x86/vvmx: XSA-278 followup fixes Andrew Cooper
2018-10-25 15:36 ` [PATCH 1/4] x86/vvmx: Unconditionally initialise vmxon_region_pa during vcpu construction Andrew Cooper
2018-10-26 9:09 ` Sergey Dyasli
2018-10-29 15:20 ` Jan Beulich
2018-10-30 7:11 ` Tian, Kevin
2018-10-25 15:38 ` [PATCH 2/4] x86/vvmx: Drop the now-obsolete vmx_inst_check_privilege() Andrew Cooper
2018-10-26 9:09 ` Sergey Dyasli
2018-10-29 15:21 ` Jan Beulich
2018-10-30 7:11 ` Tian, Kevin
2018-10-25 15:38 ` [PATCH 3/4] x86/vvmx: INVVPID instructions should be handled at by L1 Andrew Cooper
2018-10-26 8:21 ` Sergey Dyasli
2018-10-30 7:12 ` Tian, Kevin [this message]
2018-10-25 15:39 ` [PATCH 4/4] x86/vvmx: Don't handle unknown nested vmexit reasons at L0 Andrew Cooper
2018-10-26 9:05 ` Sergey Dyasli
2018-10-26 9:10 ` Andrew Cooper
2018-10-26 9:13 ` Sergey Dyasli
2018-10-26 11:09 ` Andrew Cooper
2018-10-26 11:31 ` Sergey Dyasli
2018-10-30 7:20 ` Tian, Kevin
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=AADFC41AFE54684AB9EE6CBC0274A5D19BE2BBAE@SHSMSX101.ccr.corp.intel.com \
--to=kevin.tian@intel.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=jun.nakajima@intel.com \
--cc=sergey.dyasli@citrix.com \
--cc=wei.liu2@citrix.com \
--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.