The following probes are not fired in case G1 is used:
The probes are not fired for both client and server compiler, on all solaris platforms.
The reason for the missing hotspot:::gc probes is that we don't call VM_GC_Operation::notify_gc_begin() / notify_gc_end() methods from the G1 VM operations.
Looking at the memory poo probes next.
The memory pool probes are fired by G1. Most likely the introduction of the G1 memory pools as part of 6941275: G1: The MemoryPools are incorrectly supported for G1 ensured that. So, we only seem to be missing the gc-begin / gc-end probes.
Call notify_gc_begin() / notify_gc_end() from the G1 VM Operations.
Additional note: in a departure from what's done before I'm going to call the probes from the methods that actually do the collection, not the VM operations that schedule the collection, given that the former is a more reliable way to ensure that when a probe fires the collection will indeed happen (i.e., a VM operation that's supposed to do a collection might not if say the GC locker is active).