changeset 4fb5223f1e0c in /z/repo/gem5
details: http://repo.gem5.org/gem5?cmd=changeset;node=4fb5223f1e0c
description:
        syscall_emul: [patch 7/22] remove numCpus method

        The numCpus method is misleading in that it's not really a measure of
        how many CPUs might be executing a process, but how many thread contexts
        are assigned to the process at any given point in time.

        It's nice to highlight this distinction because thread contexts are 
never
        reused in the same way that a CPU can be reused for multiple processes.
        The reason that there is no reuse is that there is no CPU scheduler for 
SE.

        The tru64 code intends to use this method and the accompanying 
contextIDs
        field to support SMT and track the number of threads with some system 
calls.
        With the up coming clone and exec patches, this paradigm must change. 
There
        needs to be a 1:1 mapping between the thread contexts and processes so 
that
        the process state between threads is allowed to vary when needed by 
Linux.
        This should not break SMT for tru64 if the Process class is refactored 
so that
        multiple Processes can share state between themselves. The following 
patches
        will do the refactoring incrementally as features are added.

diffstat:

 src/sim/process.hh |  3 ---
 1 files changed, 0 insertions(+), 3 deletions(-)

diffs (13 lines):

diff -r df43a146a38a -r 4fb5223f1e0c src/sim/process.hh
--- a/src/sim/process.hh        Wed Nov 09 14:27:41 2016 -0600
+++ b/src/sim/process.hh        Wed Nov 09 14:27:41 2016 -0600
@@ -79,9 +79,6 @@
     // thread contexts associated with this process
     std::vector<ContextID> contextIds;
 
-    // number of CPUs (esxec contexts, really) assigned to this process.
-    unsigned int numCpus() { return contextIds.size(); }
-
     // record of blocked context
     struct WaitRec
     {
_______________________________________________
gem5-dev mailing list
[email protected]
http://m5sim.org/mailman/listinfo/gem5-dev

Reply via email to