From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Wei Liu <wei.liu2@citrix.com>, xen-devel@lists.xenproject.org
Cc: Paul Durrant <Paul.Durrant@citrix.com>, Jan Beulich <JBeulich@suse.com>
Subject: Re: Regression in OSSTest Windows install test case
Date: Wed, 15 Jul 2015 15:43:09 +0100 [thread overview]
Message-ID: <55A6717D.9070900@citrix.com> (raw)
In-Reply-To: <20150715144029.GC12455@zion.uk.xensource.com>
On 15/07/15 15:40, Wei Liu wrote:
> Hi all
>
> The Windows install test case has been failing reliably in OSSTest for
> the last 6 runs.
>
> The issue manifest as Windows hit blue screen with garbled text that
> cannot be recognised when booting. Xen doesn't complain about any
> failures.
>
> I bisected that and found this commit is to be blamed.
>
> commit 3bbaaec09b1b942f5624dee176da6e416d31f982
> Author: Paul Durrant <paul.durrant@citrix.com>
> Date: Thu Jul 9 19:04:00 2015 +0200
>
> x86/hvm: unify stdvga mmio intercept with standard mmio intercept
>
> It's clear from the following check in hvmemul_rep_movs:
>
> if ( sp2mt == p2m_mmio_direct || dp2mt == p2m_mmio_direct ||
> (sp2mt == p2m_mmio_dm && dp2mt == p2m_mmio_dm) )
> return X86EMUL_UNHANDLEABLE;
>
> that mmio <-> mmio copy is not handled. This means the code in the
> stdvga mmio intercept that explicitly handles mmio <-> mmio copy when
> hvm_copy_to/from_guest_phys() fails is never going to be executed.
>
> This patch therefore adds a check in hvmemul_do_io_addr() to make sure
> mmio <-> mmio is disallowed and then registers standard mmio intercept ops
> in stdvga_init().
>
> With this patch all mmio and portio handled within Xen now goes through
> process_io_intercept().
>
> Signed-off-by: Paul Durrant <paul.durrant@citrix.com>
> Reviewed-by: Andrew Cooper <andrew.cooper3@citrix.com>
>
> Tell me if you need more information or want me to test a patch. I do
> have test environment at hand.
Given the nature of the patch, I would not be unduly surprised that the
text is garbled.
Which windows and qemu are you using? We have not encountered a single
failure like this in XenServer testing.
~Andrew
next prev parent reply other threads:[~2015-07-15 14:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-15 14:40 Regression in OSSTest Windows install test case Wei Liu
2015-07-15 14:43 ` Andrew Cooper [this message]
2015-07-15 14:46 ` Wei Liu
2015-07-15 14:47 ` Paul Durrant
2015-07-15 14:49 ` Paul Durrant
2015-07-15 14:54 ` Wei Liu
2015-07-15 14:55 ` Paul Durrant
2015-07-15 14:57 ` Wei Liu
2015-07-15 15:26 ` Fabio Fantoni
2015-07-16 8:39 ` Paul Durrant
2015-07-16 9:03 ` Wei Liu
2015-07-16 9:06 ` Paul Durrant
2015-07-16 9:11 ` Wei Liu
2015-07-16 9:12 ` 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=55A6717D.9070900@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=JBeulich@suse.com \
--cc=Paul.Durrant@citrix.com \
--cc=wei.liu2@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.