From: Peter Zijlstra <peterz@infradead.org>
To: "Kirill A. Shutemov" <kirill@shutemov.name>
Cc: kan.liang@linux.intel.com, 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, luto@amacapital.net,
Vlastimil Babka <vbabka@suse.cz>,
Will Deacon <will.deacon@arm.com>
Subject: Re: [PATCH V4 01/13] perf/core, x86: Add PERF_SAMPLE_DATA_PAGE_SIZE
Date: Fri, 1 Feb 2019 13:43:48 +0100 [thread overview]
Message-ID: <20190201124348.GC31534@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <20190201103600.uflrwzgwj2tadhey@kshutemo-mobl1>
On Fri, Feb 01, 2019 at 01:36:00PM +0300, Kirill A. Shutemov wrote:
> On Fri, Feb 01, 2019 at 11:03:58AM +0100, Peter Zijlstra wrote:
> > Will just mentioned a lovely feature where some archs have multi entry
> > large pages.
> >
> > Possible something like:
> >
> > if (pud_large(*pud)) {
> > struct page *page = pud_page(*pud);
> > int order = PUD_SHIFT;
> >
> > if (PageHuge(page)) {
> > page = compound_head(page);
> > order += compound_order(page);
> > }
> >
> > return 1ULL << order;
> > }
> >
> > works correctly.
>
> For more fun: some compound pages can be mapped withe page table entries
> not matching it's compound size, i.e. 2M pages mapped with PTE.
Surely not for PageHuge() ?! I thought the point of hugetlbfs was to
guarantee page granularity.
How is the below?
static u64 __perf_get_page_size(struct mm_struct *mm, unsigned long addr)
{
pgd_t *pgd;
p4d_t *p4d;
pud_t *pud;
pmd_t *pmd;
pte_t *pte;
pgd = pgd_offset(mm, addr);
if (pgd_none(*pgd))
return 0;
p4d = p4d_offset(pgd, addr);
if (!p4d_present(*p4d))
return 0;
if (p4d_large(*p4d)) {
struct page *page = p4d_page(*p4d);
int shift = P4D_SHIFT;
if (PageHuge(page)) {
page = compound_head(page);
shift = PAGE_SHIFT + compound_order(page);
}
return 1ULL << shift;
}
if (!p4d_present(*p4d))
return 0;
pud = pud_offset(p4d, addr);
if (!pud_present(*pud))
return 0;
if (pud_large(*pud)) {
struct page *page = pud_page(*pud);
int shift = P4D_SHIFT;
if (PageHuge(page)) {
page = compound_head(page);
shift = PAGE_SHIFT + compound_order(page);
}
return 1ULL << shift;
}
pmd = pmd_offset(pud, addr);
if (!pmd_present(*pmd))
return 0;
if (pmd_large(*pmd)) {
struct page *page = pud_page(*pud);
int shift = P4D_SHIFT;
if (PageHuge(page)) {
page = compound_head(page);
shift = PAGE_SHIFT + compound_order(page);
}
return 1ULL << shift;
}
pte = pte_offset_map(pmd, addr);
if (!pte_present(*pte)) {
pte_unmap(pte);
return 0;
}
pte_unmap(pte);
return PAGE_SIZE;
}
next prev parent reply other threads:[~2019-02-01 12:44 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-31 20:27 [PATCH V4 01/13] perf/core, x86: Add PERF_SAMPLE_DATA_PAGE_SIZE kan.liang
2019-01-31 20:27 ` [PATCH V4 02/13] perf tools: Support new sample type for data page size kan.liang
2019-01-31 20:27 ` [PATCH V4 03/13] perf script: Support " kan.liang
2019-01-31 20:27 ` [PATCH V4 04/13] perf sort: Add sort option for " kan.liang
2019-01-31 20:27 ` [PATCH V4 05/13] perf mem: Factor out a function to generate sort order kan.liang
2019-01-31 20:27 ` [PATCH V4 06/13] perf mem: Clean up output format kan.liang
2019-01-31 20:28 ` [PATCH V4 07/13] perf mem: Support data page size kan.liang
2019-01-31 20:28 ` [PATCH V4 08/13] perf test: Add test case for PERF_SAMPLE_DATA_PAGE_SIZE kan.liang
2019-01-31 20:28 ` [PATCH V4 09/13] perf/core, x86: Add support for PERF_SAMPLE_CODE_PAGE_SIZE kan.liang
2019-01-31 20:28 ` [PATCH V4 10/13] perf tools: " kan.liang
2019-01-31 20:28 ` [PATCH V4 11/13] perf script: " kan.liang
2019-01-31 20:28 ` [PATCH V4 12/13] perf report: " kan.liang
2019-01-31 20:28 ` [PATCH V4 13/13] perf test: Add test case " kan.liang
2019-02-01 9:22 ` [PATCH V4 01/13] perf/core, x86: Add PERF_SAMPLE_DATA_PAGE_SIZE Peter Zijlstra
2019-02-01 10:03 ` Peter Zijlstra
2019-02-01 10:36 ` Kirill A. Shutemov
2019-02-01 12:43 ` Peter Zijlstra [this message]
2019-02-01 12:47 ` Peter Zijlstra
2019-02-01 16:16 ` Liang, Kan
2019-02-04 10:54 ` Peter Zijlstra
2019-02-06 20:23 ` Liang, Kan
2019-02-01 10:34 ` Kirill A. Shutemov
2019-02-01 14:45 ` Liang, Kan
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=20190201124348.GC31534@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=acme@kernel.org \
--cc=ak@linux.intel.com \
--cc=eranian@google.com \
--cc=jolsa@redhat.com \
--cc=kan.liang@linux.intel.com \
--cc=kirill@shutemov.name \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=tglx@linutronix.de \
--cc=vbabka@suse.cz \
--cc=will.deacon@arm.com \
/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