From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Xen-devel List <xen-devel@lists.xen.org>,
Keir Fraser <keir@xen.org>, Jan Beulich <JBeulich@suse.com>,
Tim Deegan <tim@xen.org>
Subject: Re: Was: Request complete reversion of XSA-60 patches
Date: Thu, 14 Nov 2013 12:43:23 +0000 [thread overview]
Message-ID: <5284C56B.2080804@citrix.com> (raw)
In-Reply-To: <5283E511.6000004@citrix.com>
Following a long discussion with Tim, it appears that despite the AMD
codepath being changed, there appear to be no relevant side effects as a
result, which reduces my main concern with the series.
However, in the process we identified more areas which need a cache flush.
vmx_ctxt_switch_from() needs a wbinvd() for the case where we service a
vmexit but get descheduled before returning. There are also the
previously indicated areas which also need more cache invalidation.
There is also a wider problem with cached mappings from dom0, which are
identified but not introduced by this series. Fixing this is still an
oustanding problem, with no sensible solution being apparent.
~Andrew
next prev parent reply other threads:[~2013-11-14 12:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-13 20:46 Request complete reversion of XSA-60 patches Andrew Cooper
2013-11-14 12:43 ` Andrew Cooper [this message]
2013-11-15 8:12 ` Was: " 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=5284C56B.2080804@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=JBeulich@suse.com \
--cc=keir@xen.org \
--cc=tim@xen.org \
--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 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).