+B<rdm policy> is about how to handle conflict between reserving reserved device
+memory and guest address space. "strict" means an unsolved conflict leads to
+immediate VM crash, while "relaxed" allows VM moving forward with a warning
+message thrown out. Here "strict" is default.
Surely it would be better to reject the attach attempt rather than
crashing the domain.
Yes, indeed we just fail to create this VM in the case of runtime, or to
hotplug this associated device in the case of hotplug.
I would rephrase this somewhere, the here just introduce a reference
like this as Campbell said to me,
+B<rdm policy> specifies how to handle conflicts between reserved device
memory
+space and guest address space. This is same as "reserve" option to the rdm
+option, please see L<xl.cfg(5)>.
+
Also, again, this text is not really user-focused. It needs to
explain what the risks of using `relaxed' are (or what other checks or
countermeasures the admin should use before setting `relaxed').
After make this referring to other place, please see this on another email.
Thanks
Tiejun
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
