From: Paul Durrant <Paul.Durrant@citrix.com>
To: Andrew Cooper <Andrew.Cooper3@citrix.com>,
Jan Beulich <JBeulich@suse.com>,
xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: [PATCH v2] x86/HVM: use available linear->phys translations in REP MOVS/STOS handling
Date: Wed, 22 Jun 2016 07:00:03 +0000 [thread overview]
Message-ID: <4k1x5dwlog6e93ycol4y1n0a.1466578801924@email.android.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 942 bytes --]
On 21 June 2016, at 20:50, Andrew Cooper <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
>I/O request not read: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0
>The domain still exists, but it looks like it never gets unpaused from
>the device model request.
I think that error is normal. The first time QEMU scans the ioreq pages it sees them blank. The lack of unpause, of course, is not normal.
Paul
>~Andrew
>
[-- Attachment #1.2: Type: text/html, Size: 3453 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next reply other threads:[~2016-06-22 7:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-22 7:00 Paul Durrant [this message]
-- strict thread matches above, loose matches on Subject: below --
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
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=4k1x5dwlog6e93ycol4y1n0a.1466578801924@email.android.com \
--to=paul.durrant@citrix.com \
--cc=Andrew.Cooper3@citrix.com \
--cc=JBeulich@suse.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).