Search Options

Results per page
Sort
Preferred Languages
Advance

Results 1 - 3 of 3 for syscallingP (0.41 sec)

  1. src/internal/trace/summary.go

    	tasks map[TaskID]*UserTaskSummary
    
    	// syscallingP and syscallingG represent a binding between a P and G in a syscall.
    	// Used to correctly identify and clean up after syscalls (blocking or otherwise).
    	syscallingP map[ProcID]GoID
    	syscallingG map[GoID]ProcID
    
    	// rangesP is used for optimistic tracking of P-based ranges for goroutines.
    	//
    Registered: Wed Jun 12 16:32:35 UTC 2024
    - Last Modified: Thu May 23 01:00:11 UTC 2024
    - 20.7K bytes
    - Viewed (0)
  2. src/internal/trace/order.go

    				// for multiple generations since trace start, we would have seen
    				// a previous GoStatus event that bound the goroutine to an M.
    				return curCtx, false, fmt.Errorf("inconsistent thread for syscalling goroutine %d: thread has goroutine %d", gid, curCtx.G)
    			}
    			newCtx.G = gid
    			break
    		}
    		// Now we're talking about a thread and goroutine that have been
    Registered: Wed Jun 12 16:32:35 UTC 2024
    - Last Modified: Mon Jun 03 14:56:25 UTC 2024
    - 52.4K bytes
    - Viewed (0)
  3. src/runtime/trace.go

    	// with no opportunity to transition.
    	//
    	// The exception to this rule are goroutines that are concurrently exiting a syscall.
    	// Those will all be forced into the syscalling slow path, and we'll just make sure
    	// that we don't observe any goroutines in that critical section before starting
    	// the world again.
    	//
    Registered: Wed Jun 12 16:32:35 UTC 2024
    - Last Modified: Wed May 22 21:17:41 UTC 2024
    - 37.1K bytes
    - Viewed (0)
Back to top