Jes Sorensen wrote: >>>>>> "Jes" == Jes Sorensen <jes@xxxxxxx> writes: > > Jes> Hi, Does anyone remember how far back it was for KVM on ia64 to > Jes> still work with more than 3GB of memory assigned to the virtual > Jes> machine? > > Hi, > > I have done some more investiation on this problem and found that > things go wrong the moment we try and register any memory outside the > 4GB window. > > In addition I noticed that even though I register the > 4GB memory > from say 0x400000000 the firmware image still seems to think it starts > at 0x100000000 - anyone can tell me how the firmware gets it's > addresses? Hi, Jes Seems I missed some mails from kvm/ia64 list, because my mailing address is unsubscribed by unknow reason days ago. For guest's physical address space, 0-3G is conventional ram, 3G-3.5G is allocated for mmio address sapce. 4G- higher address is also ram. The memory size is transferred to firmware at creating guest time. In firmware, it also has the knowledge about guest memory layout from memory size, so it will know where is ram and where is mmio... I have a fix about this issue, and you should can get it in mailing list. :) Thanks Xiantao -- To unsubscribe from this list: send the line "unsubscribe kvm-ia64" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
