Re: [Xen-devel] Backport requests to stable for Xen ARM

2016-05-17 Thread Jan Beulich
>>> On 17.05.16 at 12:49,  wrote:
> On Tue, 17 May 2016, Jan Beulich wrote:
>> >>> On 16.05.16 at 17:40,  wrote:
>> > On Mon, 16 May 2016, Julien Grall wrote:
>> >> It has been a while without any ARM backport request. Ian Campbell
>> >> used to keep a list of backport fixes for Xen ARM and apply them
>> >> to stable. Now that he left, I am not sure who will do it.
>> >> 
>> >> I would be fine to keep the list of patches, although I am not
>> >> a committer. Stefano do you plan to apply the backport?
>> > 
>> > I would be fine with doing that, but I am not sure who is responsible
>> > for backporting commits to stable trees. Any committer can do that, or
>> > do we have a set of stable maintainers? 
>> 
>> Formally I am the stable tree maintainer, but just like for tools
>> backports (which I have always been deferring to the tools
>> maintainers, and IanJ has been taking care of those mostly),
>> ARM backports have also mostly been taken care of by an
>> ARM maintainer who is also committer (used to be IanC). I'd
>> be glad if we could transition that arrangement onto your
>> shoulders.
> 
> All right. I made the backports.

Thanks!

Jan


___
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel


Re: [Xen-devel] Backport requests to stable for Xen ARM

2016-05-17 Thread Stefano Stabellini
On Tue, 17 May 2016, Jan Beulich wrote:
> >>> On 16.05.16 at 17:40,  wrote:
> > On Mon, 16 May 2016, Julien Grall wrote:
> >> It has been a while without any ARM backport request. Ian Campbell
> >> used to keep a list of backport fixes for Xen ARM and apply them
> >> to stable. Now that he left, I am not sure who will do it.
> >> 
> >> I would be fine to keep the list of patches, although I am not
> >> a committer. Stefano do you plan to apply the backport?
> > 
> > I would be fine with doing that, but I am not sure who is responsible
> > for backporting commits to stable trees. Any committer can do that, or
> > do we have a set of stable maintainers? 
> 
> Formally I am the stable tree maintainer, but just like for tools
> backports (which I have always been deferring to the tools
> maintainers, and IanJ has been taking care of those mostly),
> ARM backports have also mostly been taken care of by an
> ARM maintainer who is also committer (used to be IanC). I'd
> be glad if we could transition that arrangement onto your
> shoulders.

All right. I made the backports.

Cheers,

Stefano

___
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel


Re: [Xen-devel] Backport requests to stable for Xen ARM

2016-05-17 Thread Jan Beulich
>>> On 16.05.16 at 17:40,  wrote:
> On Mon, 16 May 2016, Julien Grall wrote:
>> It has been a while without any ARM backport request. Ian Campbell
>> used to keep a list of backport fixes for Xen ARM and apply them
>> to stable. Now that he left, I am not sure who will do it.
>> 
>> I would be fine to keep the list of patches, although I am not
>> a committer. Stefano do you plan to apply the backport?
> 
> I would be fine with doing that, but I am not sure who is responsible
> for backporting commits to stable trees. Any committer can do that, or
> do we have a set of stable maintainers? 

Formally I am the stable tree maintainer, but just like for tools
backports (which I have always been deferring to the tools
maintainers, and IanJ has been taking care of those mostly),
ARM backports have also mostly been taken care of by an
ARM maintainer who is also committer (used to be IanC). I'd
be glad if we could transition that arrangement onto your
shoulders.

Thanks, Jan


___
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel


Re: [Xen-devel] Backport requests to stable for Xen ARM

2016-05-17 Thread Julien Grall

Hi Jan,

On 17/05/2016 08:38, Jan Beulich wrote:

xen/arm: Force broadcast of TLB and instruction cache maintenance
instructions
commit e2faa286faa36da36ee14f6bc973043013001724
up to Xen 4.4


For both of those please note that 4.4 is in security-only
maintenance mode, and hence shouldn't be getting non-security
backports anymore unless those are needed as a prereq.


They are not needed for Xen 4.4. I was not sure if the release was still 
maintained.


Regards,

--
Julien Grall

___
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel


Re: [Xen-devel] Backport requests to stable for Xen ARM

2016-05-17 Thread Jan Beulich
>>> On 16.05.16 at 16:28,  wrote:
> It has been a while without any ARM backport request. Ian Campbell
> used to keep a list of backport fixes for Xen ARM and apply them
> to stable. Now that he left, I am not sure who will do it.
> 
> I would be fine to keep the list of patches, although I am not
> a committer. Stefano do you plan to apply the backport?

That would be my preference, but I could take care of such if Stefano
can't (but of course provided with actual backports in case the original
patches don't apply cleanly).

> I would like to request backport for the following patches:
> 
> xen/arm: traps: Correctly interpret the content of the register HPFAR_EL2 
> commit c0516182ff86d77375c35517036535c0df61c7e1 and depends on commit 
> edd429c9cc2af99df9dda10002cc59011edf0cac
> up to Xen 4.4
> 
> xen/arm: Force broadcast of TLB and instruction cache maintenance 
> instructions
> commit e2faa286faa36da36ee14f6bc973043013001724
> up to Xen 4.4

For both of those please note that 4.4 is in security-only
maintenance mode, and hence shouldn't be getting non-security
backports anymore unless those are needed as a prereq.

Jan

> arm: Fix asynchronous aborts (SError exceptions) due to bogus PTE
> commit 0ebb6832f043ecfc6a3dcab8a7ba5c4070901ab7
> up to Xen 4.5
> 
> xen/arm: ignore writes to GICD_ICACTIVER ... GICD_ICACTIVERN
> commit 68778eeaa3babedba9677400f63f1e7564bba561
> up to Xen 4.6
> 
> xen/arm64: ensure that the correct SP is used for exceptions
> commit b7e5aee0a36487d6205c1633add25fd430d3b6d7
> 
> Note that whilst it would be nice to get
> "xen/arm64: correctly emulate the {w, x}zr registers" backported,
> the patch depends on lots of IO emulation rework. So I have
> not included it in the backport request.
> 
> Regards,
> 
> -- 
> Julien Grall




___
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel


Re: [Xen-devel] Backport requests to stable for Xen ARM

2016-05-16 Thread Stefano Stabellini
On Mon, 16 May 2016, Julien Grall wrote:
> Hello,
> 
> It has been a while without any ARM backport request. Ian Campbell
> used to keep a list of backport fixes for Xen ARM and apply them
> to stable. Now that he left, I am not sure who will do it.
> 
> I would be fine to keep the list of patches, although I am not
> a committer. Stefano do you plan to apply the backport?

I would be fine with doing that, but I am not sure who is responsible
for backporting commits to stable trees. Any committer can do that, or
do we have a set of stable maintainers? 


> I would like to request backport for the following patches:
> 
> xen/arm: traps: Correctly interpret the content of the register HPFAR_EL2 
> commit c0516182ff86d77375c35517036535c0df61c7e1 and depends on commit 
> edd429c9cc2af99df9dda10002cc59011edf0cac
> up to Xen 4.4
> 
> xen/arm: Force broadcast of TLB and instruction cache maintenance instructions
> commit e2faa286faa36da36ee14f6bc973043013001724
> up to Xen 4.4
> 
> arm: Fix asynchronous aborts (SError exceptions) due to bogus PTE
> commit 0ebb6832f043ecfc6a3dcab8a7ba5c4070901ab7
> up to Xen 4.5
> 
> xen/arm: ignore writes to GICD_ICACTIVER ... GICD_ICACTIVERN
> commit 68778eeaa3babedba9677400f63f1e7564bba561
> up to Xen 4.6
> 
> xen/arm64: ensure that the correct SP is used for exceptions
> commit b7e5aee0a36487d6205c1633add25fd430d3b6d7
> 
> Note that whilst it would be nice to get
> "xen/arm64: correctly emulate the {w, x}zr registers" backported,
> the patch depends on lots of IO emulation rework. So I have
> not included it in the backport request.
> 
> Regards,
> 
> -- 
> Julien Grall
> 

___
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel