From: Boris Ostrovsky <boris.ostrovsky@oracle.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>,
Paul Durrant <paul.durrant@citrix.com>,
Jan Beulich <jbeulich@suse.com>, Juergen Gross <jgross@suse.com>,
xen-devel <xen-devel@lists.xen.org>
Cc: zhangchen.fnst@cn.fujitsu.com
Subject: Re: ioreq server regression
Date: Mon, 12 Dec 2016 13:03:41 -0500 [thread overview]
Message-ID: <5423519c-cbb5-ec4c-93f2-c2a80a5e8594@oracle.com> (raw)
In-Reply-To: <87f6246c-c973-7e09-3542-6d54c7a62b6a@citrix.com>
On 12/12/2016 11:36 AM, Andrew Cooper wrote:
> On 12/12/16 16:01, Boris Ostrovsky wrote:
>> Looks like commit e7dabe59c ("x86/hvm: don't unconditionally create a
>> default ioreq server") breaks restore for HVM guests.
>>
>> I see "qemu: hardware error: Invalid ioreq type 0x53" in qemu log.
>>
>> -boris
>>
> Does this help? The current creation_finished logic is wrong if a 2nd
> toolstack component performs a pause/unpause pair on the domain.
Yes, this seems to work.
-boris
>
> diff --git a/xen/common/domain.c b/xen/common/domain.c
> index 3abaca9..6043f89 100644
> --- a/xen/common/domain.c
> +++ b/xen/common/domain.c
> @@ -1004,13 +1004,6 @@ int domain_unpause_by_systemcontroller(struct
> domain *d)
> {
> int old, new, prev = d->controller_pause_count;
>
> - /*
> - * We record this information here for populate_physmap to figure out
> - * that the domain has finished being created. In fact, we're only
> - * allowed to set the MEMF_no_tlbflush flag during VM creation.
> - */
> - d->creation_finished = true;
> -
> do
> {
> old = prev;
> @@ -1022,6 +1015,14 @@ int domain_unpause_by_systemcontroller(struct
> domain *d)
> prev = cmpxchg(&d->controller_pause_count, old, new);
> } while ( prev != old );
>
> + /*
> + * We record this information here for populate_physmap to figure out
> + * that the domain has finished being created. In fact, we're only
> + * allowed to set the MEMF_no_tlbflush flag during VM creation.
> + */
> + if ( prev == 0 )
> + d->creation_finished = true;
> +
> domain_unpause(d);
>
> return 0;
>
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
prev parent reply other threads:[~2016-12-12 18:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-12 16:01 ioreq server regression Boris Ostrovsky
2016-12-12 16:21 ` Jan Beulich
2016-12-12 16:28 ` Boris Ostrovsky
2016-12-12 16:22 ` Paul Durrant
2016-12-12 16:27 ` Andrew Cooper
2016-12-12 16:28 ` Paul Durrant
2016-12-12 16:33 ` Paul Durrant
2016-12-12 16:36 ` Andrew Cooper
2016-12-12 18:03 ` Boris Ostrovsky [this message]
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=5423519c-cbb5-ec4c-93f2-c2a80a5e8594@oracle.com \
--to=boris.ostrovsky@oracle.com \
--cc=andrew.cooper3@citrix.com \
--cc=jbeulich@suse.com \
--cc=jgross@suse.com \
--cc=paul.durrant@citrix.com \
--cc=xen-devel@lists.xen.org \
--cc=zhangchen.fnst@cn.fujitsu.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).