From: "Liang, Kan" <kan.liang@linux.intel.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: acme@kernel.org, tglx@linutronix.de, mingo@redhat.com,
linux-kernel@vger.kernel.org, eranian@google.com,
jolsa@redhat.com, namhyung@kernel.org, ak@linux.intel.com,
Andy Lutomirski <luto@amacapital.net>
Subject: Re: [PATCH V3 01/13] perf/core, x86: Add PERF_SAMPLE_DATA_PAGE_SIZE
Date: Thu, 31 Jan 2019 09:58:09 -0500 [thread overview]
Message-ID: <6ecaa29b-af17-938d-8638-acb9de5454be@linux.intel.com> (raw)
In-Reply-To: <20190131123725.GB31516@hirez.programming.kicks-ass.net>
On 1/31/2019 7:37 AM, Peter Zijlstra wrote:
> On Wed, Jan 30, 2019 at 06:23:42AM -0800, kan.liang@linux.intel.com wrote:
>> diff --git a/arch/x86/events/core.c b/arch/x86/events/core.c
>> index 374a197..03bf45d 100644
>> --- a/arch/x86/events/core.c
>> +++ b/arch/x86/events/core.c
>> @@ -2578,3 +2578,45 @@ void perf_get_x86_pmu_capability(struct x86_pmu_capability *cap)
>> cap->events_mask_len = x86_pmu.events_mask_len;
>> }
>> EXPORT_SYMBOL_GPL(perf_get_x86_pmu_capability);
>> +
>> +/*
>> + * map x86 page levels to perf page sizes
>> + */
>> +static const enum perf_page_size perf_page_size_map[PG_LEVEL_NUM] = {
>> + [PG_LEVEL_NONE] = PERF_PAGE_SIZE_NONE,
>> + [PG_LEVEL_4K] = PERF_PAGE_SIZE_4K,
>> + [PG_LEVEL_2M] = PERF_PAGE_SIZE_2M,
>> + [PG_LEVEL_1G] = PERF_PAGE_SIZE_1G,
>> + [PG_LEVEL_512G] = PERF_PAGE_SIZE_512G,
>> +};
>> +
>> +u64 perf_get_page_size(u64 virt)
>> +{
>> + unsigned long flags;
>> + unsigned int level;
>> + pte_t *pte;
>> +
>> + if (!virt)
>> + return 0;
>> +
>> + /*
>> + * Interrupts are disabled, so it prevents any tear down
>> + * of the page tables.
>> + * See the comment near struct mmu_table_batch.
>> + */
>> + local_irq_save(flags);
>> + if (virt >= TASK_SIZE)
>> + pte = lookup_address(virt, &level);
>> + else {
>> + if (current->mm)
>> + pte = lookup_address_in_pgd(pgd_offset(current->mm, virt),
>> + virt, &level);
>
> Aside from all the missin {}, I'm fairly sure this is broken since this
> happens from NMI context. This can interrupt switch_mm() and things like
> use_temporary_mm().
>
> Also; why does this live in the x86 code and not in the generic code?
>
This is x86 implementation.
In generic code, there is a __weak function. I'll make it clear in the
change log in v4.
+/* Return page size of given virtual address. IRQ-safe required. */
+u64 __weak perf_get_page_size(u64 virt)
+{
+ return PERF_PAGE_SIZE_NONE;
+}
>> + else
>> + level = PG_LEVEL_NUM;
>> + }
>> + local_irq_restore(flags);
>> + if (level >= PG_LEVEL_NUM)
>> + return PERF_PAGE_SIZE_NONE;
>> +
>> + return (u64)perf_page_size_map[level];
>> +}
>
>> diff --git a/include/uapi/linux/perf_event.h b/include/uapi/linux/perf_event.h
>> index 7198ddd..79daacd 100644
>> --- a/include/uapi/linux/perf_event.h
>> +++ b/include/uapi/linux/perf_event.h
>> @@ -141,8 +141,9 @@ enum perf_event_sample_format {
>> PERF_SAMPLE_TRANSACTION = 1U << 17,
>> PERF_SAMPLE_REGS_INTR = 1U << 18,
>> PERF_SAMPLE_PHYS_ADDR = 1U << 19,
>> + PERF_SAMPLE_DATA_PAGE_SIZE = 1U << 20,
>>
>> - PERF_SAMPLE_MAX = 1U << 20, /* non-ABI */
>> + PERF_SAMPLE_MAX = 1U << 21, /* non-ABI */
>>
>> __PERF_SAMPLE_CALLCHAIN_EARLY = 1ULL << 63, /* non-ABI; internal use */
>> };
>> @@ -863,6 +864,7 @@ enum perf_event_type {
>> * { u64 abi; # enum perf_sample_regs_abi
>> * u64 regs[weight(mask)]; } && PERF_SAMPLE_REGS_INTR
>> * { u64 phys_addr;} && PERF_SAMPLE_PHYS_ADDR
>> + * { u64 data_page_size;} && PERF_SAMPLE_DATA_PAGE_SIZE
>> * };
>> */
>> PERF_RECORD_SAMPLE = 9,
>> @@ -1150,6 +1152,18 @@ union perf_mem_data_src {
>> #define PERF_MEM_S(a, s) \
>> (((__u64)PERF_MEM_##a##_##s) << PERF_MEM_##a##_SHIFT)
>>
>> +
>> +enum perf_page_size {
>> + PERF_PAGE_SIZE_NONE,
>> + PERF_PAGE_SIZE_4K,
>> + PERF_PAGE_SIZE_8K,
>> + PERF_PAGE_SIZE_16K,
>> + PERF_PAGE_SIZE_64K,
>> + PERF_PAGE_SIZE_2M,
>> + PERF_PAGE_SIZE_1G,
>> + PERF_PAGE_SIZE_512G,
>> +};
>
> Since you have a u64 to store this in, WTH do you use this limited enum?
> Are you very sure this covers all the possible page sizes for all
> architectures?
>
> Why not simply report the page size in bytes?
>
I will use the page size instead in V4.
Thanks,
Kan
next prev parent reply other threads:[~2019-01-31 14:58 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-30 14:23 [PATCH V3 01/13] perf/core, x86: Add PERF_SAMPLE_DATA_PAGE_SIZE kan.liang
2019-01-30 14:23 ` [PATCH V3 02/13] perf tools: Support new sample type for data page size kan.liang
2019-01-30 14:23 ` [PATCH V3 03/13] perf script: Support " kan.liang
2019-01-30 14:23 ` [PATCH V3 04/13] perf sort: Add sort option for " kan.liang
2019-01-30 14:23 ` [PATCH V3 05/13] perf mem: Factor out a function to generate sort order kan.liang
2019-01-30 14:23 ` [PATCH V3 06/13] perf mem: Clean up output format kan.liang
2019-01-30 14:23 ` [PATCH V3 07/13] perf mem: Support data page size kan.liang
2019-01-30 14:23 ` [PATCH V3 08/13] perf test: Add test case for PERF_SAMPLE_DATA_PAGE_SIZE kan.liang
2019-01-30 14:23 ` [PATCH V3 09/13] perf/core, x86: Add support for PERF_SAMPLE_CODE_PAGE_SIZE kan.liang
2019-01-30 14:23 ` [PATCH V3 10/13] perf tools: " kan.liang
2019-01-30 14:23 ` [PATCH V3 11/13] perf script: " kan.liang
2019-01-30 14:23 ` [PATCH V3 12/13] perf report: " kan.liang
2019-01-30 14:23 ` [PATCH V3 13/13] perf test: Add test case " kan.liang
2019-01-31 12:37 ` [PATCH V3 01/13] perf/core, x86: Add PERF_SAMPLE_DATA_PAGE_SIZE Peter Zijlstra
2019-01-31 12:59 ` Peter Zijlstra
2019-01-31 13:10 ` Andi Kleen
2019-01-31 14:58 ` Liang, Kan [this message]
2019-02-08 10:39 ` Thomas Gleixner
2019-02-08 13:35 ` Liang, Kan
2019-02-01 5:02 ` Will Deacon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6ecaa29b-af17-938d-8638-acb9de5454be@linux.intel.com \
--to=kan.liang@linux.intel.com \
--cc=acme@kernel.org \
--cc=ak@linux.intel.com \
--cc=eranian@google.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).