From: Yu Zhang <yu.c.zhang@linux.intel.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: Andrew Cooper <andrew.cooper3@citrix.com>,
xen-devel@lists.xenproject.org
Subject: Re: about fully UMIP support in Xen
Date: Thu, 20 Apr 2017 18:10:09 +0800 [thread overview]
Message-ID: <cd16569f-7fee-96e7-781d-b0a25dac54fb@linux.intel.com> (raw)
In-Reply-To: <58F8A33302000078001524E6@prv-mh.provo.novell.com>
On 4/20/2017 6:01 PM, Jan Beulich wrote:
>>>> On 20.04.17 at 11:53, <yu.c.zhang@linux.intel.com> wrote:
>> On 4/20/2017 5:47 PM, Jan Beulich wrote:
>>>>>> On 20.04.17 at 09:15, <yu.c.zhang@linux.intel.com> wrote:
>>>> And back to the schedule of this feature, are you working on it? Or any
>>>> specific plan?
>>> Well, the HVM side is basically ready (as said, the single hunk needed
>>> to support UMIP when hardware supports it could be easily split off of
>>> my emulation patch). For the PV side I don't currently have any plans
>>> to do any work.
>> Thanks, Jan. So do you have plan to push the HVM support in Xen 4.10?
> We're moving in circles, it feels. My patch depends on Andrew
> making progress. Breaking out the one mentioned hunk could
> of course be done at any time, if we have indication that UMIP
> hardware support will actually arrive and it becomes unlikely
> for the patch to be able to go in as a whole in time for 4.10.
I can understand. And please let me know if there's any help we can
offer here in Intel. :-)
Yu
> Jan
>
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-04-20 10:10 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-19 8:48 about fully UMIP support in Xen Yu Zhang
2017-04-19 9:18 ` Jan Beulich
2017-04-19 9:48 ` Yu Zhang
2017-04-19 9:59 ` Andrew Cooper
2017-04-19 11:16 ` Yu Zhang
2017-04-19 11:19 ` Jan Beulich
2017-04-19 11:44 ` Yu Zhang
2017-04-19 13:34 ` Jan Beulich
2017-04-19 13:49 ` Andrew Cooper
2017-04-19 14:06 ` Jan Beulich
2017-04-19 14:17 ` Andrew Cooper
2017-04-19 14:27 ` Jan Beulich
2017-04-19 14:35 ` Andrew Cooper
2017-04-19 13:50 ` Yu Zhang
2017-04-19 13:58 ` Andrew Cooper
2017-04-19 14:07 ` Jan Beulich
2017-04-19 14:09 ` Andrew Cooper
2017-04-20 7:15 ` Yu Zhang
2017-04-20 9:47 ` Jan Beulich
2017-04-20 9:53 ` Yu Zhang
2017-04-20 10:01 ` Jan Beulich
2017-04-20 10:10 ` Yu Zhang [this message]
2017-04-20 10:23 ` Andrew Cooper
2017-04-20 10:38 ` Yu Zhang
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=cd16569f-7fee-96e7-781d-b0a25dac54fb@linux.intel.com \
--to=yu.c.zhang@linux.intel.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@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.