Re: [PATCH 1/1] perf tools: Add missing user space support forconfig1/config2

[Ingo Molnar]

* Vince Weaver <vweaver1@xxxxxxxxxxxx> wrote:

> On Wed, 27 Apr 2011, Ingo Molnar wrote:
> 
> > Secondly, you are still quite wrong even with your revised opinion. Being able 
> > to type '-e cycles' and '-e instructions' in perf and get ... cycles and 
> > instructions counts/events, and the kernel helping that kind of approach is not 
> > 'abstraction to the extreme', it's called 'common sense'.
> 
> by your logic I should be able to delete a file by saying
>
>   echo "delete /tmp/tempfile" > /dev/sdc1

> because using unlink() is too low of an abstraction and confusing to the 
> user.

Erm, unlink() does not pass magic hexa constants to the disk controller.

unlink() is a high level interface that works across a vast range of disk 
controllers, disks, network mounted filesystems, in-RAM filesystems, in-ROM 
filesystems, clustered filesystems and other mediums.

Just like that we can tell perf to count 'cycles', 'branches' or 
'branch-misses' - all of these are relatively high level concepts (in the scope 
of CPUs) that work across a vast range of CPU types and models.

Similarly, for offcore we want to introduce the concept of 'node local' versus 
'remote' memory - perhaps with some events for inter-CPU traffic as well - 
because that probably covers most of the NUMA related memory profiling needs.

Raw events are to perf what ioctls are to the VFS: small details nobody felt 
worth generalizing. My point in this discussion is that we do not offer new 
filesystems that support *only* ioctl calls ... Is this simple concept so hard 
to understand?

Thanks,

	Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/