From: Dario Faggioli <raistlin@linux.it>
To: Jan Beulich <JBeulich@suse.com>,
xen-devel <xen-devel@lists.xenproject.org>
Cc: Igor Druzhinin <igor.druzhinin@citrix.com>,
Julien Grall <julien.grall@arm.com>,
Kevin Tian <kevin.tian@intel.com>,
Jun Nakajima <jun.nakajima@intel.com>
Subject: Re: [PATCH] VMX: sync CPU state upon vCPU destruction
Date: Thu, 09 Nov 2017 16:02:08 +0100 [thread overview]
Message-ID: <1510239728.4517.226.camel@linux.it> (raw)
In-Reply-To: <5A04791A020000780018D9F4@prv-mh.provo.novell.com>
[-- Attachment #1.1: Type: text/plain, Size: 489 bytes --]
On Thu, 2017-11-09 at 07:49 -0700, Jan Beulich wrote:
> See the code comment being added for why we need this.
>
> Reported-by: Igor Druzhinin <igor.druzhinin@citrix.com>
> Signed-off-by: Jan Beulich <jbeulich@suse.com>
>
Reviewed-by: Dario Faggioli <raistlin@linux.it>
Regards,
Dario
--
<<This happens because I choose it to happen!>> (Raistlin Majere)
-----------------------------------------------------------------
Dario Faggioli, Ph.D, http://about.me/dario.faggioli
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
[-- Attachment #2: Type: text/plain, Size: 127 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-11-09 15:02 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-09 14:49 [PATCH] VMX: sync CPU state upon vCPU destruction Jan Beulich
2017-11-09 15:02 ` Dario Faggioli [this message]
2017-11-10 8:41 ` Sergey Dyasli
2017-11-10 9:50 ` Dario Faggioli
2017-11-10 10:30 ` Jan Beulich
2017-11-10 14:46 ` Igor Druzhinin
2017-11-13 9:51 ` Jan Beulich
2017-11-21 13:22 ` Ping: " Jan Beulich
2017-11-21 14:07 ` Igor Druzhinin
2017-11-21 15:29 ` Jan Beulich
2017-11-21 16:00 ` Igor Druzhinin
2017-11-21 16:42 ` Dario Faggioli
2017-11-21 16:58 ` George Dunlap
2017-11-21 17:00 ` Sergey Dyasli
2017-11-21 17:26 ` Jan Beulich
2017-11-21 16:08 ` George Dunlap
2017-11-21 16:26 ` Igor Druzhinin
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=1510239728.4517.226.camel@linux.it \
--to=raistlin@linux.it \
--cc=JBeulich@suse.com \
--cc=igor.druzhinin@citrix.com \
--cc=julien.grall@arm.com \
--cc=jun.nakajima@intel.com \
--cc=kevin.tian@intel.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 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).