On Tue, May 19, 2015 at 01:32:27AM +0000, Tian, Kevin wrote: > > From: Wei Liu [mailto:wei.l...@citrix.com] > > Sent: Tuesday, May 19, 2015 4:00 AM > >
[...] > > > > Yes, but this policy is hardcoded in code (as in, you bail when > > detecting conflict in highmem region). I don't think we have the > > expertise to un-hardcode it in the future (it might require x86 specific > > insider information and specific hardware to test). So I would like to > > make it as future proof as possible. > > > > I know you're limited by hvm_info. I would accept this hardcoded policy > > as short term solution, but I would like commitment from Intel to > > maintain this piece of code and properly work out a flexible solution to > > deal with >4G case. > > > > We made this simplification by balancing implementation complexity and > real-world possibility. Yes Intel will commit to maintain it if future > platform > does break this assumption. > Thanks. This is what I need at this stage. I'm fine with the way going forward. Wei. > Thanks > Kevin _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
