From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>
Cc: Lars Kurth <lars.kurth.xen@gmail.com>,
Elazar Leibovich <elazar.leibovich@ravellosystems.com>,
Xen-devel <xen-devel@lists.xen.org>,
Lars Kurth <lars.kurth@xenproject.org>
Subject: Re: Low-hanging fruit bugs for starting contributor
Date: Tue, 22 Nov 2016 13:00:45 -0500 [thread overview]
Message-ID: <20161122180045.GG9448@char.us.oracle.com> (raw)
In-Reply-To: <4d5ae0c8-fdf4-ce24-7ec4-4bd36f72493b@citrix.com>
On Tue, Nov 22, 2016 at 05:49:35PM +0000, Andrew Cooper wrote:
> On 22/11/16 17:42, Elazar Leibovich wrote:
> > Indeed nested virtualization, I apologize for the accidental deletion,
> > While we would like to contribute to nested virtualization eventually,
> > if there are other small bugs in other places in the hypervisor, that
> > would be a good warm up as well.
>
> Perhaps I should publish my plans for making usable nested-virt in Xen.
Yes please do.
>
> My current estimate of 2 person-years of work to get it into a state
> where upstream Xen could plausibly support nested-virt.
Two years go fast. And with more people it can go even faster..
>
> ~Andrew
>
> _______________________________________________
> 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-11-22 18:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-22 15:49 Low-hanging fruit bugs for starting contributor Elazar Leibovich
2016-11-22 16:18 ` Konrad Rzeszutek Wilk
2016-11-22 16:19 ` Lars Kurth
2016-11-22 17:00 ` Elazar Leibovich
2016-11-22 17:38 ` Lars Kurth
2016-11-22 17:42 ` Elazar Leibovich
2016-11-22 17:49 ` Andrew Cooper
2016-11-22 18:00 ` Konrad Rzeszutek Wilk [this message]
2016-11-23 19:00 ` Andrew Cooper
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=20161122180045.GG9448@char.us.oracle.com \
--to=konrad.wilk@oracle.com \
--cc=andrew.cooper3@citrix.com \
--cc=elazar.leibovich@ravellosystems.com \
--cc=lars.kurth.xen@gmail.com \
--cc=lars.kurth@xenproject.org \
--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).