From: Wen Congyang <wencongyang@gmail.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>,
Zhang Chen <zhangchen.fnst@cn.fujitsu.com>,
Xen devel <xen-devel@lists.xenproject.org>,
Paul Durrant <Paul.Durrant@citrix.com>
Cc: "eddie . dong" <eddie.dong@intel.com>,
Changlong Xie <xiecl.fnst@cn.fujitsu.com>,
Wei Liu <wei.liu2@citrix.com>,
Ian Jackson <Ian.Jackson@eu.citrix.com>,
Yang Hongyang <imhy.yang@gmail.com>
Subject: Re: [PATCH 1/3] Don't create default ioreq server
Date: Wed, 7 Dec 2016 10:46:19 +0800 [thread overview]
Message-ID: <584777FB.2080203@gmail.com> (raw)
In-Reply-To: <100de853-dc5e-5ddc-49f7-2c77500a76ab@citrix.com>
At 2016/11/30 20:25, Andrew Cooper wrote:
> On 30/11/16 09:47, Zhang Chen wrote:
>> The ioreq server make colo run failed.
>>
>> Signed-off-by: Zhang Chen <zhangchen.fnst@cn.fujitsu.com>
>> Signed-off-by: Wen Congyang <wency@cn.fujitsu.com>
>
> Nack.
>
> You can simply "fix" a COLO issue by breaking a much more common usecase.
Yes, this patch is wrong. It is only in my git tree to let COLO work.
>
>
> What actually breaks in the COLO case here?
I have reported this BUG last year:
https://lists.xenproject.org/archives/html/xen-devel/2015-12/msg02850.html
Thanks
Wen Congyang
>
> ~Andrew
>
>> ---
>> xen/arch/x86/hvm/hvm.c | 11 -----------
>> 1 file changed, 11 deletions(-)
>>
>> diff --git a/xen/arch/x86/hvm/hvm.c b/xen/arch/x86/hvm/hvm.c
>> index 25dc759..8522852 100644
>> --- a/xen/arch/x86/hvm/hvm.c
>> +++ b/xen/arch/x86/hvm/hvm.c
>> @@ -5339,17 +5339,6 @@ static int hvmop_get_param(
>> case HVM_PARAM_IOREQ_PFN:
>> case HVM_PARAM_BUFIOREQ_PFN:
>> case HVM_PARAM_BUFIOREQ_EVTCHN:
>> - {
>> - domid_t domid;
>> -
>> - /* May need to create server. */
>> - domid = d->arch.hvm_domain.params[HVM_PARAM_DM_DOMAIN];
>> - rc = hvm_create_ioreq_server(d, domid, 1,
>> - HVM_IOREQSRV_BUFIOREQ_LEGACY, NULL);
>> - if ( rc != 0 && rc != -EEXIST )
>> - goto out;
>> - }
>> - /*FALLTHRU*/
>> default:
>> a.value = d->arch.hvm_domain.params[a.index];
>> break;
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> https://lists.xen.org/xen-devel
>
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-12-07 2:46 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-30 9:47 [PATCH 0/3] Support the latest version of qemu COLO Zhang Chen
2016-11-30 9:47 ` [PATCH 1/3] Don't create default ioreq server Zhang Chen
2016-11-30 12:25 ` Andrew Cooper
2016-12-07 2:46 ` Wen Congyang [this message]
2016-12-01 13:19 ` Wei Liu
2016-12-09 6:38 ` Zhang Chen
2016-12-09 16:13 ` Konrad Rzeszutek Wilk
2016-12-09 16:43 ` Paul Durrant
2016-12-09 17:21 ` Konrad Rzeszutek Wilk
2016-12-09 17:37 ` Paul Durrant
2016-12-12 18:03 ` Ian Jackson
2016-12-12 18:08 ` Paul Durrant
2016-11-30 9:47 ` [PATCH 2/3] Add Xen colo support for qemu-upstream colo codes Zhang Chen
2016-12-01 13:20 ` Wei Liu
2016-12-12 10:37 ` Wei Liu
2016-12-13 1:46 ` Zhang Chen
2016-11-30 9:47 ` [PATCH 3/3] Add COLO replication top-id support Zhang Chen
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=584777FB.2080203@gmail.com \
--to=wencongyang@gmail.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=Paul.Durrant@citrix.com \
--cc=andrew.cooper3@citrix.com \
--cc=eddie.dong@intel.com \
--cc=imhy.yang@gmail.com \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xenproject.org \
--cc=xiecl.fnst@cn.fujitsu.com \
--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).