From: "André Przywara" <andre.przywara@arm.com>
To: Julien Grall <julien.grall@arm.com>,
Stefano Stabellini <sstabellini@kernel.org>
Cc: "xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
Vijay Kilari <vijay.kilari@gmail.com>,
Shanker Donthineni <shankerd@codeaurora.org>
Subject: Re: Code freeze exception for Xen 4.9 ARM ITS emulation?
Date: Thu, 13 Apr 2017 23:26:36 +0100 [thread overview]
Message-ID: <f8b8e765-0e50-114d-09fe-409fe2a9fb1e@arm.com> (raw)
In-Reply-To: <7e91f07e-24a1-cbdd-04b0-60bc1016eee5@arm.com>
On 13/04/17 14:29, Julien Grall wrote:
Hi Julien,
>> The development of the ARM ITS emulation support has taken more time
>> than anticipated and I won't be able to address and fix all outstanding
>> comments until the official code freeze date.
>>
>> However the first part of the series is in a good shape and should be
>> ready to be merged in time.
>>
>> I was wondering if I could be granted a brief code freeze exception for
>> the remaining part of the series?
>
> Thank you for your contributions. I spent yesterday reviewing the latest
> version (v8) and discovered potential locking issues in the series.
I see and honestly don't know an easy solution for this nasty problem.
> My understanding is they are not easily solvable and would require some
> rework of the vGIC. So I am afraid to say that ITS will not get merged
> for Xen 4.9. But keep in mind you can continue to work on this series
> and get it applied once next development window opens.
OK, thanks for your and Stefano's massive efforts in this matter anyway
and for your support and help.
I am looking forward to getting this code in the right shape in the next
weeks.
Cheers,
Andre.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
prev parent reply other threads:[~2017-04-13 22:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-07 17:34 Code freeze exception for Xen 4.9 ARM ITS emulation? Andre Przywara
2017-04-07 22:30 ` Stefano Stabellini
2017-04-13 13:29 ` Julien Grall
2017-04-13 22:26 ` André Przywara [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=f8b8e765-0e50-114d-09fe-409fe2a9fb1e@arm.com \
--to=andre.przywara@arm.com \
--cc=julien.grall@arm.com \
--cc=shankerd@codeaurora.org \
--cc=sstabellini@kernel.org \
--cc=vijay.kilari@gmail.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 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).