From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Tamas K Lengyel <tamas.lengyel@zentific.com>
Cc: Artem Mygaiev <artem.mygaiev@globallogic.com>,
Matt Wilson <msw@amazon.com>,
Ian Jackson <ian.jackson@eu.citrix.com>,
gross@suse.com, dongxiao.xu@intel.com, mengxu@cis.upenn.edu,
chao.p.peng@linux.intel.com, zhigang.x.wang@oracle.com,
Parth Dixit <parth.dixit@linaro.org>,
Paul.Skentzos@dornerworks.com, wency@cn.fujitsu.com,
Razvan Cojocaru <rcojocaru@bitdefender.com>,
guijianfeng@cn.fujitsu.com,
Daniel Kiper <daniel.kiper@oracle.com>,
josh.whitehead@dornerworks.com, zoltan.kiss@citrix.com,
Arianna Avanzini <avanzini.arianna@gmail.com>,
Anthony PERARD <anthony.perard@citrix.com>,
"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
Serge Broslavsky <serge.broslavsky@linaro.org>,
feng.wu@intel.com, yjhyun.yoo@samsung.com, olaf@aepfle.de,
Steve.Vande.rLeest@dornerworks.com,
Ian Campbell <ian.campbell@citrix.com>,
Vijay Kilari <vijay.kilari@gmail.com>,
Stefa
Subject: Re: Xen 4.5 development update (September update). Feature freeze slip by two weeks.
Date: Fri, 26 Sep 2014 13:42:18 -0400 [thread overview]
Message-ID: <20140926174218.GD5102@laptop.dumpdata.com> (raw)
In-Reply-To: <CAErYnsgVz75AAawdqSs_1v3tQ_Xvyshs3WNOASZyzprOw4G-UQ@mail.gmail.com>
On Wed, Sep 24, 2014 at 07:23:57PM +0200, Tamas K Lengyel wrote:
> Hi Konrad,
> I would like to ask for an exception for this feature:
>
> * ARM implement mem_access (ok)
> > v5
> > https://github.com/tklengyel/xen/tree/arm_memaccess5
> > - Tamas K Lengyel
> >
>
> The version 9 of the series will be posted tomorrow. The first half of the
> series (cleanup and relocation) is mostly acked and mergeable and there had
> been some discussion that it might be merged before the second half
> (ARM-specific bits) are finished with the review process (which are IMHO
> also very close to the finish line).
As you saw Jan already merged the mergable patches (up to 10 I believe).
The rest will take some time to review.
I need to discuss this with Tim and also look at the patches to get a feel
for:
- What is the risk of it introducing regressions for existing use-cases.
- What is the risk if these features do not make it in Xen 4.5
(What are the external impacts of this - what are the sub-projects
that depend on this).
- What is the awesomes of this. As in, how will this feature make
Xen more awesome.
- How easy is it for somebody to set this up and test it out?
Thank you!
>
> Thanks,
> Tamas
next prev parent reply other threads:[~2014-09-26 17:42 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-10 17:05 Xen 4.5 development update (September update). Feature freeze slip by two weeks konrad.wilk
2014-09-10 18:59 ` Wei Liu
2014-09-10 19:26 ` Razvan Cojocaru
2014-09-11 7:37 ` Jan Beulich
2014-09-11 8:05 ` Razvan Cojocaru
2014-09-11 9:00 ` Tamas K Lengyel
2014-09-10 19:26 ` Roy Franz
2014-09-10 21:04 ` Tamas K Lengyel
2014-09-11 9:58 ` Ian Campbell
2014-09-11 17:47 ` Stefano Stabellini
2014-09-12 6:35 ` manish jaggi
2014-09-12 9:35 ` Ian Campbell
2014-09-12 10:10 ` manish jaggi
2014-09-12 10:18 ` Ian Campbell
2014-09-23 8:26 ` Elena Ufimtseva
2014-09-24 17:23 ` Tamas K Lengyel
2014-09-26 17:42 ` Konrad Rzeszutek Wilk [this message]
2014-09-24 22:53 ` Boris Ostrovsky
2014-09-26 17:09 ` Konrad Rzeszutek Wilk
2014-09-25 9:22 ` Dave Scott
2014-09-25 9:25 ` George Dunlap
2014-09-25 21:26 ` Konrad Rzeszutek Wilk
2014-10-07 12:48 ` Dave Scott
2014-10-07 14:50 ` Konrad Rzeszutek Wilk
2014-10-08 13:42 ` Ian Campbell
2014-09-29 16:28 ` RC slip by a week. " Konrad Rzeszutek Wilk
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=20140926174218.GD5102@laptop.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=Paul.Skentzos@dornerworks.com \
--cc=Steve.Vande.rLeest@dornerworks.com \
--cc=anthony.perard@citrix.com \
--cc=artem.mygaiev@globallogic.com \
--cc=avanzini.arianna@gmail.com \
--cc=chao.p.peng@linux.intel.com \
--cc=daniel.kiper@oracle.com \
--cc=dongxiao.xu@intel.com \
--cc=feng.wu@intel.com \
--cc=gross@suse.com \
--cc=guijianfeng@cn.fujitsu.com \
--cc=ian.campbell@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=josh.whitehead@dornerworks.com \
--cc=mengxu@cis.upenn.edu \
--cc=msw@amazon.com \
--cc=olaf@aepfle.de \
--cc=parth.dixit@linaro.org \
--cc=rcojocaru@bitdefender.com \
--cc=serge.broslavsky@linaro.org \
--cc=tamas.lengyel@zentific.com \
--cc=vijay.kilari@gmail.com \
--cc=wency@cn.fujitsu.com \
--cc=xen-devel@lists.xenproject.org \
--cc=yjhyun.yoo@samsung.com \
--cc=zhigang.x.wang@oracle.com \
--cc=zoltan.kiss@citrix.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).