From: cov@codeaurora.org (Christopher Covington)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/3] Bunch of vdso cleanups following feedback from x86
Date: Thu, 24 Jul 2014 14:20:45 -0400 [thread overview]
Message-ID: <53D14E7D.3070706@codeaurora.org> (raw)
In-Reply-To: <1404930133-30324-1-git-send-email-will.deacon@arm.com>
Hi Will,
On 07/09/2014 02:22 PM, Will Deacon wrote:
> Hi all,
>
> Following useful discussions with Andy (thanks!), I've put together the
> following (lightly tested) series for arm64 which attempts to address
> issues with our current vdso code.
>
> Please take a look. Cheers,
With appropriate updates to Checkpoint and Restore In Userspace (CRIU) [1] and
some finishing touches to its AArch64 port that I hope to publish very soon, I
see no regressions running its VDSO test cases, which exercise basic
discovery, use, and remapping.
Tested-by: Christopher Covington <cov@codeaurora.org>
1. http://lists.openvz.org/pipermail/criu/2014-July/015138.html
Christopher
--
Employee of Qualcomm Innovation Center, Inc.
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
hosted by the Linux Foundation.
prev parent reply other threads:[~2014-07-24 18:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-09 18:22 [PATCH 0/3] Bunch of vdso cleanups following feedback from x86 Will Deacon
2014-07-09 18:22 ` [PATCH 1/3] arm64: vdso: put vdso datapage in a separate vma Will Deacon
2014-07-09 19:44 ` Nathan Lynch
2014-07-09 19:48 ` Andy Lutomirski
2014-07-09 18:22 ` [PATCH 2/3] arm64: vdso: move to _install_special_mapping and remove arch_vma_name Will Deacon
2014-07-09 18:22 ` [PATCH 3/3] arm64: vdso: move data page before code pages Will Deacon
2014-07-24 18:20 ` Christopher Covington [this message]
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=53D14E7D.3070706@codeaurora.org \
--to=cov@codeaurora.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 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).