From: steve.capper@linaro.org (Steve Capper)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC/PATCH v2] ARM: vDSO gettimeofday using generic timer architecture
Date: Tue, 11 Feb 2014 08:44:03 +0000 [thread overview]
Message-ID: <20140211084402.GA928@linaro.org> (raw)
In-Reply-To: <20140210171200.GE26684@n2100.arm.linux.org.uk>
On Mon, Feb 10, 2014 at 05:12:00PM +0000, Russell King - ARM Linux wrote:
> On Mon, Feb 10, 2014 at 04:51:16PM +0000, Steve Capper wrote:
> > Hi Russell,
> >
> > On Sun, Feb 09, 2014 at 10:20:23AM +0000, Russell King - ARM Linux wrote:
> > > On Fri, Feb 07, 2014 at 05:05:49PM -0600, Nathan Lynch wrote:
> > > > + /* Grab the vDSO code pages. */
> > > > + for (i = 0; i < vdso_pages; i++) {
> > > > + pg = virt_to_page(&vdso_start + i*PAGE_SIZE);
> > > > + ClearPageReserved(pg);
> > > > + get_page(pg);
> > > > + vdso_pagelist[i] = pg;
> > > > + }
> > >
> > > Why do we want to clear the reserved status? This looks over complicated
> > > to me.
> > >
> >
> > This looks like it was inherited from the PowerPC code where the
> > behaviour of set_pte_at would change dependent on whether or not the
> > page was reserved (set_pte_at->set_pte_filter->maybe_pte_to_page). I
> > think we can safely remove this from ARM and ARM64.
>
> Great, so we can get rid of that and the get_page() on the vdso data
> page below.
>
> > > > +
> > > > + /* Sanity check the shared object header. */
> > > > + vbase = vmap(vdso_pagelist, 1, 0, PAGE_KERNEL);
> > > > + if (vbase == NULL) {
> > > > + pr_err("Failed to map vDSO pagelist!\n");
> > > > + return -ENOMEM;
> > > > + } else if (memcmp(vbase, "\177ELF", 4)) {
> > > > + pr_err("vDSO is not a valid ELF object!\n");
> > > > + ret = -EINVAL;
> > > > + goto unmap;
> > > > + }
> > >
> > > Why do we need to vmap() pages which are already accessible - vdso_start
> > > must be part of the kernel image, and therefore will be accessible via
> > > standard mappings.
> > >
> >
> > This is a dress rehersal for install_special_mapping more than anything.
> > If we map the page, and look at the first 4 bytes, are they what we
> > expect?
>
> My point is that we can already view this page directly by dereferencing
> vdso_start - do we really need to perform this apparant test of the MMU?
> If the MMU isn't working in this way, we have much bigger and more
> fundamental problems...
>
I see, yes I think people would notice the MMU not working :-).
This code also tests the alignment of vdso_start in a roundabout way.
I'm not sure whether or not an explicit alignment check to PAGE_SIZE
would be beneficial instead of the test mapping.
Cheers,
--
Steve
next prev parent reply other threads:[~2014-02-11 8:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-07 23:05 [RFC/PATCH v2] ARM: vDSO gettimeofday using generic timer architecture Nathan Lynch
2014-02-09 10:20 ` Russell King - ARM Linux
2014-02-10 16:51 ` Steve Capper
2014-02-10 17:12 ` Russell King - ARM Linux
2014-02-11 8:44 ` Steve Capper [this message]
2014-02-10 23:57 ` Nathan Lynch
2014-02-11 10:45 ` Will Deacon
2014-02-11 16:23 ` Nathan Lynch
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=20140211084402.GA928@linaro.org \
--to=steve.capper@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.