Willy, On Thu, Oct 19, 2006 at 03:21:37PM -0600, Matthew Wilcox wrote: > On Thu, Oct 19, 2006 at 02:05:19PM -0700, Stephane Eranian wrote: > > I don't think this is going to work for the simple reason that perfmon supports per-thread > > monitoring. As a thread migrates from one CPU to another, its PMU state migrates with it. > > So you cannot reload a full Montecito state onto a Madison PMU. You will not crash, because > > write to unimplemented PMD are ignored but you will get false results. Even in system-wide > > tools are not prepare to cope with mixed configurations. > > I suppose you could lock a thread to running only on the kind of CPU it > started running on. It's not a great solution though. > The problem is that some jobs, especially in scientific computing, rely on setting their own affinity to achieve best performance. You don't know to affect this from within the kernel. Monitoring may start at the first user level instruction of a program. The scheduler may pick a first CPU that may be different than the one that the application will want to go with sched_affinity(). -- -Stephane - To unsubscribe from this list: send the line "unsubscribe linux-ia64" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
|