On Tue, Mar 16, 2021 at 04:07:05PM -0400, Peter Xu wrote: > I think what I'm missing is why we had such a restriction. Quotting from the > commit ID: IIRC, the current behavior allows the process to be placed into a cgroup with a subset of CPUs and you just can do 'cyclictest -a -t'. Process should not ignore external configuration. That's my whole point here. > So I'm not sure I understand the word "runtime environment". > > If it's defined as "the set of cores that this process is allowed to > run", I am trying to say is, the tests should not assume they have the full control of the placement as this is not what I would expect. If I as 'admin' limits the sched mask then cyclictest should not overwrite it. If you insist removing this code, please add a section in the documentation explaining why the tools ignore it. > John and I had some discussion offlist about this last time on oslat, As I said, I think this behavior is wrong. Anyway, I stopped caring.
