From: Vitaly Kuznetsov <vkuznets@redhat.com>
To: Ian Jackson <Ian.Jackson@citrix.com>
Cc: Paul Durrant <Paul.Durrant@citrix.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: [PATCH qemu-traditional] switch to the new ioreq server API
Date: Thu, 21 Sep 2017 10:35:50 +0200 [thread overview]
Message-ID: <87lgl8o3dl.fsf@vitty.brq.redhat.com> (raw)
In-Reply-To: <54abf8a55bbe45fa9b8319889a9363cc@AMSPEX02CL03.citrite.net> (Paul Durrant's message of "Wed, 6 Sep 2017 09:36:06 +0000")
Paul Durrant <Paul.Durrant@citrix.com> writes:
>> -----Original Message-----
>> From: Vitaly Kuznetsov [mailto:vkuznets@redhat.com]
>> Sent: 06 September 2017 10:29
>> To: xen-devel@lists.xen.org
>> Cc: Paul Durrant <Paul.Durrant@citrix.com>; Ian Jackson
>> <Ian.Jackson@citrix.com>
>> Subject: [PATCH qemu-traditional] switch to the new ioreq server API
>>
>> Instead of using implicit ioreq server creation side-effect upon reading
>> HVM params switch qemu-traditional to using explicit APIs. This opens a
>> possibility for removing the above mentioned side-effect and special
>> 'default_ioreq_server' code pathes in Xen hypervisor in the future.
>>
>> This also solves an issue with soft reset when qemu-traditional is being
>> used. Xen c/s e7dabe5 ("x86/hvm: don't unconditionally create a default
>> ioreq server") disabled ioreq server creation after domain was created
>> for the first time and this is needed for soft reset.
>>
>> IOREQ_TYPE_PCI_CONFIG handling code is stolen as-is from qemu-
>> upstream.
>>
>> Signed-off-by: Vitaly Kuznetsov <vkuznets@redhat.com>
>
> Reviewed-by: Paul Durrant <paul.durrant@citrix.com>
>
Ian,
could you please have a look?
Thanks!
--
Vitaly
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
prev parent reply other threads:[~2017-09-21 8:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-06 9:28 [PATCH qemu-traditional] switch to the new ioreq server API Vitaly Kuznetsov
2017-09-06 9:36 ` Paul Durrant
2017-09-21 8:35 ` Vitaly Kuznetsov [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=87lgl8o3dl.fsf@vitty.brq.redhat.com \
--to=vkuznets@redhat.com \
--cc=Ian.Jackson@citrix.com \
--cc=Paul.Durrant@citrix.com \
--cc=xen-devel@lists.xen.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).