xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: George Dunlap <george.dunlap@eu.citrix.com>
To: Jan Beulich <JBeulich@suse.com>,
	xen-devel <xen-devel@lists.xenproject.org>
Cc: Jinsong Liu <jinsong.liu@intel.com>, Keir Fraser <keir@xen.org>,
	Andrew Cooper <andrew.cooper3@citrix.com>,
	Zhenzhong Duan <zhenzhong.duan@oracle.com>,
	Donald D Dugger <donald.d.dugger@intel.com>,
	Jun Nakajima <jun.nakajima@intel.com>
Subject: Re: XSA-60 - how to get back to a sane state
Date: Mon, 2 Dec 2013 19:43:17 +0000	[thread overview]
Message-ID: <529CE2D5.7030805@eu.citrix.com> (raw)
In-Reply-To: <529CA7250200007800108CB8@nat28.tlf.novell.com>

On 12/02/2013 02:28 PM, Jan Beulich wrote:
> All,
>
> Jinsong's patches having been in for nearly a month now, but not
> being in a shape that would make releasing in 4.4 or backporting to
> the older trees desirable, we need to come to a conclusion on
> which way to go. Currently it looks like we have three options, but
> of course I'll be happy to see other (better!) ones proposed.
>
> 1) Stay with what we have.
>
> 2) Revert 86d60e85 ("VMX: flush cache when vmentry back to UC
> guest") in its entirety plus, perhaps, the change 62652c00 ("VMX:
> fix cr0.cd handling") did to vmx_ctxt_switch_to().
>
> 3) Apply the attached patch that Andrew and I have been putting
> together, with the caveat that it's still incomplete (see below).
>
> The latter two are based on the observation that the amount of
> cache flushing we do with what is in the master tree right now is
> more than what we did prior to that patch series but still
> insufficient. Hence the revert would get us back to the earlier
> state (and obviously eliminate the performance problems that
> were observed when doing too eager flushing), whereas
> applying the extra 5th patch would get us closer to a proper
> solution.

What's missing is a description of the pros and cons of 1 and 2.  Do you 
have any links to threads describing the problem?

  -George

  reply	other threads:[~2013-12-02 19:43 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-02 14:28 XSA-60 - how to get back to a sane state Jan Beulich
2013-12-02 19:43 ` George Dunlap [this message]
2013-12-03  2:21   ` Andrew Cooper
2013-12-03  3:06     ` Liu, Jinsong
2013-12-03  8:00       ` Jan Beulich
2013-12-03 14:30         ` Liu, Jinsong
2013-12-03 15:09           ` Jan Beulich
2013-12-03 15:14             ` George Dunlap
2013-12-04 12:04             ` Liu, Jinsong
2013-12-04 12:16               ` Jan Beulich
2013-12-04 15:55                 ` George Dunlap
2013-12-04 16:09                   ` Jan Beulich
2013-12-04 16:03                 ` Liu, Jinsong
2013-12-04 16:14                   ` Jan Beulich
2013-12-04 16:23                     ` Liu, Jinsong
2013-12-03  7:57     ` Jan Beulich

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=529CE2D5.7030805@eu.citrix.com \
    --to=george.dunlap@eu.citrix.com \
    --cc=JBeulich@suse.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=donald.d.dugger@intel.com \
    --cc=jinsong.liu@intel.com \
    --cc=jun.nakajima@intel.com \
    --cc=keir@xen.org \
    --cc=xen-devel@lists.xenproject.org \
    --cc=zhenzhong.duan@oracle.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).