On 03/19/2015 02:38 PM, Juergen Gross wrote:
On 03/19/2015 12:34 PM, Daniel Kiper wrote:
On Thu, Mar 19, 2015 at 10:55:37AM +0100, Juergen Gross wrote:
On 03/18/2015 04:14 PM, Daniel Kiper wrote:
[...]
I have checked new p2m code and I think that this is reasonable
solution too.
Do I need any patches for xl to be able to test this? I did:
xl mem-max 2 4096
xl mem-set 2 4096
Yep. I started work on it but I was not able to finish it.
Here you can find some old patches for this issue:
http://lists.xen.org/archives/html/xen-devel/2013-04/msg03072.html
Bob and I will work on it sooner or later (probably a bit later).
Hmmm... Boris, David, how did you manage to get this memory hotplug
stuff working. Did you use xm instead of xl?
Whoever can test this - what about the attached patch?
Already succeeded in testing. :-)
Rather easy via:
Dom0: xl mem-max <domain> <size>
DomU: echo <size_in_kb>
>/sys/devices/system/xen_memory/xen_memory0/target_kb
On my system udev is set up to add the memory automatically, so no
further action required for me.
David, you said:
This one can be trivially fixed by setting the new sections in the p2m
to INVALID_P2M_ENTRY before calling add_memory().
Are you preparing a patch for this, or do you want me to do it?
I've already got a patch working, I'll send it soon.
Juergen
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
