Re: [Xen-devel] 4.6.2 preparations

2016-05-17 Thread Wei Liu 
On Tue, May 17, 2016 at 07:35:16AM -0600, Jan Beulich wrote:
> >>> On 17.05.16 at 15:23,  wrote:
> > I would like to propose backporting some mini-os patches to mini-os.git
> > stable-4.6 branch and update Config.mk in 4.6.
> 
> On top of the recently backported ones?

Yes.

> 
> > I guess I will bring that up with Samuel and then post patch here?
> 
> Yes please.
> 

OK. Will do.

Wei.

> Jan
> 

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

Re: [Xen-devel] 4.6.2 preparations

2016-05-17 Thread Jan Beulich 
>>> On 17.05.16 at 15:23,  wrote:
> I would like to propose backporting some mini-os patches to mini-os.git
> stable-4.6 branch and update Config.mk in 4.6.

On top of the recently backported ones?

> I guess I will bring that up with Samuel and then post patch here?

Yes please.

Jan


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

Re: [Xen-devel] 4.6.2 preparations

2016-05-17 Thread Wei Liu 
On Tue, May 17, 2016 at 05:33:48AM -0600, Jan Beulich wrote:
> All,
> 
> with this due in about three weeks, please indicate backports you find
> missing from its staging tree but you deem necessary in the release.
> I already have commit 556c69f4ef ("x86/PoD: skip eager reclaim when
> possible") queued, and I'm undecided about af07377007 ("IOMMU/x86:
> per-domain control structure is not HVM-specific") as well as the
> SMEP/SMAP fix (which first needs at least one more adjustment on
> master anyway).
> 
> Thanks, Jan
> 

I would like to propose backporting some mini-os patches to mini-os.git
stable-4.6 branch and update Config.mk in 4.6.

I guess I will bring that up with Samuel and then post patch here?

Wei.

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

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

Re: [Xen-devel] 4.6.2 preparations

2016-05-17 Thread Jan Beulich 
>>> On 17.05.16 at 14:45,  wrote:
> Should we backport something like
> 013396f93ee2d4ec416f701ae420c683b7327230 to help users avoid the
> deadlock present when using a domU with a Linux kernel 3.14 or newer?
> 
> If yes then you might want the init script fixes to make the daemons use
> that as well which were 1367e9e5ba4d1612e303123ec0bbf961100fcfa1 and
> 9ec6859322fc148742d9aa85596e03c3c2be.

Both tools side changes, so I'll defer to Ian.

Jan


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

Re: [Xen-devel] 4.6.2 preparations

2016-05-17 Thread Doug Goldstein 
On 5/17/16 6:33 AM, Jan Beulich wrote:
> All,
> 
> with this due in about three weeks, please indicate backports you find
> missing from its staging tree but you deem necessary in the release.
> I already have commit 556c69f4ef ("x86/PoD: skip eager reclaim when
> possible") queued, and I'm undecided about af07377007 ("IOMMU/x86:
> per-domain control structure is not HVM-specific") as well as the
> SMEP/SMAP fix (which first needs at least one more adjustment on
> master anyway).
> 
> Thanks, Jan
> 

Should we backport something like
013396f93ee2d4ec416f701ae420c683b7327230 to help users avoid the
deadlock present when using a domU with a Linux kernel 3.14 or newer?

If yes then you might want the init script fixes to make the daemons use
that as well which were 1367e9e5ba4d1612e303123ec0bbf961100fcfa1 and
9ec6859322fc148742d9aa85596e03c3c2be.

A no is ok.
-- 
Doug Goldstein



signature.asc
Description: OpenPGP digital signature
___
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

[Xen-devel] 4.6.2 preparations

2016-05-17 Thread Jan Beulich 
All,

with this due in about three weeks, please indicate backports you find
missing from its staging tree but you deem necessary in the release.
I already have commit 556c69f4ef ("x86/PoD: skip eager reclaim when
possible") queued, and I'm undecided about af07377007 ("IOMMU/x86:
per-domain control structure is not HVM-specific") as well as the
SMEP/SMAP fix (which first needs at least one more adjustment on
master anyway).

Thanks, Jan


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