Prev: [RFC PATCH] ARM: Assume new page cache pages have dirty D-cache
Next: [PATCH 1/1] perf archive: Don't try to collect files without a build-id
From: Peter Zijlstra on 2 Mar 2010 13:00 On Tue, 2010-03-02 at 17:26 +0100, Stephane Eranian wrote: > > @@ -37,14 +43,16 @@ static struct event_constraint intel_core2_event_constraints[] = > > INTEL_EVENT_CONSTRAINT(0x18, 0x1), /* IDLE_DURING_DIV */ > > INTEL_EVENT_CONSTRAINT(0x19, 0x2), /* DELAYED_BYPASS */ > > INTEL_EVENT_CONSTRAINT(0xa1, 0x1), /* RS_UOPS_DISPATCH_CYCLES */ > > + INTEL_EVENT_CONSTRAINT(0xc9, 0x1), /* ITLB_MISS_RETIRED (T30-9) */ > > Where does the constraint on ITLB_MISS_RETIRED come from? IntelĀ® 64 and IA-32 Architectures Software Developer's Manual Volume 3B: System Programming Guide, Part 2 Dec 2009 (253669) Section 30.4.3, Table 30-9 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ |