>>> On 30.05.17 at 08:41, <o...@aepfle.de> wrote: > On Mon, May 29, Jan Beulich wrote: > >> Finally I don't think a host wide option will do. If it is to be of use >> (considering that it used wrong may break applications), it needs >> to be per-domain, and its value needs to be migrated (perhaps >> in the form of a low/high pair of TSC frequency values). > > How is it supposed to be propagated from one host to another? > > With the global option one can unconditionally receive a domU and > preserve "native performance" in case of tsc_mode=default. With a > per-domU option one has to know upfront.
I don't understand: If the incoming stream tells you the acceptable clock range, what else do you need to know (upfront or later)? Jan _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org https://lists.xen.org/xen-devel
