On 17-04-25 02:24:40, Jan Beulich wrote: > >>> On 25.04.17 at 09:15, <yi.y....@linux.intel.com> wrote: > > Sorry, this may cause potential issue and is not a good example. But from SW > > view, there is another case where the per-socket supporting is important in > > real-time scenarios. You may have a real-time domain on one socket that > > requires > > different masks (especially for code/data) to guarantee its performance vs. > > other general-purpose domains run on a different socket. In that case it’s a > > heterogeneous software usage model (rather than heterogeneous hardware). > > And, > > we should not force same masks setting on different sockets in such case. > > I don't follow: The COS IDs for the real-time and general purpose > domains would be different, wouldn't they? Thus there would be > different masks in use, as intended. > Yes, you are right. But as above case, the real-time domain only runs on one socket. If per-socket supporting is enabled, we can allocate this COS ID to other domains on other sockets. This can help to improve the scarce cache utilization.
> Jan _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org https://lists.xen.org/xen-devel
