profiler: Actually support profiling user stack frames only.

The "-k" argument (which never did anything before) is now inverted
compared to what it used to be, i.e. now specifying it will profile
kernel frames, too, whereas by default only user frames will be
sampled.

headers/os/kernel/debugger.h

@@ -407,6 +407,7 @@ typedef struct {
 	bool				variable_stack_depth;
 										// variable number of samples per hit;
 										// cf. debug_profiler_update
+	bool				profile_kernel;	// sample kernel stack frames
 } debug_nub_start_profiler;
 
 typedef struct {

headers/private/kernel/user_debugger.h

@@ -147,6 +147,8 @@ struct thread_debug_info {
 			// the buffer
 		bool			variable_stack_depth;
 			// record a variable number of samples per hit
+		bool			profile_kernel;
+			// record samples in kernel stack frames
 		bool			buffer_full;
 			// indicates that the sample buffer is full
 		union {

headers/private/system/system_profiler_defs.h

@@ -21,6 +21,7 @@ struct system_profiler_parameters {
 	// sampling
 	bigtime_t	interval;				// interval at which to take samples
 	uint32		stack_depth;			// maximum stack depth to sample
+	bool		profile_kernel;			// sample kernel stack frames
 };