From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: xen-devel <xen-devel@lists.xenproject.org>,
Paul Durrant <paul.durrant@citrix.com>
Subject: Re: [PATCH v2] x86/HVM: use available linear->phys translations in REP MOVS/STOS handling
Date: Thu, 23 Jun 2016 10:56:05 +0100 [thread overview]
Message-ID: <5247fb65-21d5-0cd0-d1e7-c62f235ee2a6@citrix.com> (raw)
In-Reply-To: <576A583402000078000F7768@prv-mh.provo.novell.com>
On 22/06/16 08:19, Jan Beulich wrote:
>>>> On 21.06.16 at 21:50, <andrew.cooper3@citrix.com> wrote:
>> On 20/06/16 12:29, Jan Beulich wrote:
>>> If we have the translation result available already, we should also use
>>> it here. In my tests with Linux guests this eliminates all calls to
>>> hvmemul_linear_to_phys() from the STOS path and most from the MOVS one.
>>>
>>> Also record the translation for re-use at least during response
>>> processing.
>>>
>>> Signed-off-by: Jan Beulich <jbeulich@suse.com>
>> This patch is still broken. All XenServer HVM guests (both windows and
>> linux) are dying, with Qemu citing
> _All_? That contradicts both my own testing and osstest's smoke
> one having succeeded.
Apologies for the noise. This was actually caused by the DOMCTL
interface bump, but manifests itself as hvmloader getting stuck while
performing IO to Qemu.
After fixing up a local change we have, everything is back to full
working order.
~Andrew
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-06-23 9:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-20 11:29 [PATCH v2] x86/HVM: use available linear->phys translations in REP MOVS/STOS handling Jan Beulich
2016-06-20 12:22 ` Paul Durrant
2016-06-21 19:50 ` Andrew Cooper
2016-06-22 7:19 ` Jan Beulich
2016-06-23 9:56 ` Andrew Cooper [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-06-22 7:00 Paul Durrant
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=5247fb65-21d5-0cd0-d1e7-c62f235ee2a6@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=JBeulich@suse.com \
--cc=paul.durrant@citrix.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).