[Bug translator/9967] New: raise MAXSKIPPED for -DINTERRUPTIBLE!=0 case

["fche at redhat dot com" <sourceware-bugzilla at sourceware dot org>]

With -DINTERRUPTIBLE=1 being the recent default, we can get probe reentrancy
due to interrupt handlers or other factors.  These don't represent a worry
beyond lost events for those interrupting events.

I propose that for -DINTERRUPTIBLE=0, we leave MAXSKIPPED roughly where it is,
but for -DINTERRUPTIBLE!=0 (the default), MAXSKIPPED could get much increased
or perhaps even partially compiled out.  ("partially" because we skip probes
not just for reentrancy but for reasons such as global variable timeouts.)

-- 
           Summary: raise MAXSKIPPED for -DINTERRUPTIBLE!=0 case
           Product: systemtap
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: translator
        AssignedTo: systemtap at sources dot redhat dot com
        ReportedBy: fche at redhat dot com


http://sourceware.org/bugzilla/show_bug.cgi?id=9967

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.