On 11/07/18 13:10, Jan Beulich wrote: > Shared resources (L1 cache and TLB in particular) present a risk of > information leak via side channels. Don't use hyperthreads in such > cases, but allow independent control of their use at the same time. > > Signed-off-by: Jan Beulich <jbeul...@suse.com> > --- > An option to avoid the up/down cycle would be to avoid clearing the > sibling (and then perhaps also core) map of parked CPUs, allowing to > bail early from cpu_up_helper(). > > TBD: How to prevent the CPU from transiently becoming available for > scheduling when being onlined at runtime?
This looks like an argument for cancelling at call-in time, no? > --- a/docs/misc/xen-command-line.markdown > +++ b/docs/misc/xen-command-line.markdown > @@ -1040,6 +1040,13 @@ identical to the boot CPU will be parked > ### hpetbroadcast (x86) > > `= <boolean>` > > +### ht (x86) I'd suggest smt rather than ht here. SMT is the technical term, while HT is Intel's marketing name. ~Andrew _______________________________________________ Xen-devel mailing list Xen-devel@lists.xenproject.org https://lists.xenproject.org/mailman/listinfo/xen-devel
