From mboxrd@z Thu Jan  1 00:00:00 1970
From: Wei Liu <wei.liu2@citrix.com>
Subject: Re: Requesting for freeze exception for RMRR
Date: Fri, 17 Jul 2015 10:30:41 +0100
Message-ID: <20150717093041.GI12455@zion.uk.xensource.com>
References: <55A35B5E.3000805@intel.com>
	<20150713114145.GF4108@zion.uk.xensource.com>
	<55A46575.5020607@intel.com>
	<20150714092915.GC4152@zion.uk.xensource.com>
	<55A85758.2010702@intel.com>
	<20150717091726.GG12455@zion.uk.xensource.com>
	<55A8C9E7.7080702@intel.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xen.org>
Content-Disposition: inline
In-Reply-To: <55A8C9E7.7080702@intel.com>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xen.org>
List-Help: <mailto:xen-devel-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=subscribe>
Sender: xen-devel-bounces@lists.xen.org
Errors-To: xen-devel-bounces@lists.xen.org
To: "Chen, Tiejun" <tiejun.chen@intel.com>
Cc: Kevin <kevin.tian@intel.com>, Wei Liu <wei.liu2@citrix.com>, "ian.campbell@citrix.com" <ian.campbell@citrix.com>, George Dunlap <George.Dunlap@eu.citrix.com>, Andrew Cooper <andrew.cooper3@citrix.com>, "ian.jackson@eu.citrix.com" <ian.jackson@eu.citrix.com>, "Wang,
	Yong Y" <yong.y.wang@intel.com>, "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>, Jan Beulich <jbeulich@suse.com>
List-Id: xen-devel@lists.xenproject.org

On Fri, Jul 17, 2015 at 05:24:55PM +0800, Chen, Tiejun wrote:
> >>* On hvmloader side, there three patches now:
> >>   patch #5 is reviewed by George and Acked by Jan;
> >>   patch #6 is reviewed just for code implementation but that solution can't
> >>convince all maintainers. Honestly, this is a rare possibility of collision
> >>in real world and the original pci allocation is not good so its hard to
> >>reshape the original mechanism in one week. But actually we also have some
> >>other solutions but we need a little time to figure out how to step forward
> >>but I just think any solution wouldn't bring any change to other stuffs.
> >>   patch #7 is pretty close to be Acked.
> >>
> >>So what's your final determination?
> >>
> >
> >If you and maintainers can work out a solution for hvmloader bits today
> >then yes, otherwise no.
> >
> 
> Based on my understanding, we already have some solutions but we need some
> time to put one into practice. I think its possible to work out this next
> week. As you see other stuffs are almost closed so we can put our all effort
> just on this bit.
> 

Jan, Andrew and George, can you provide some insight? If that's the case
we may be able to get that done within next week?

Wei.

> Thanks
> Tiejun