From: Will Deacon <will.deacon@arm.com>
To: Jon Masters <jcm@redhat.com>
Cc: Mark Salyzyn <salyzyn@android.com>,
linux-kernel@vger.kernel.org, James Morse <james.morse@arm.com>,
Russell King <linux@armlinux.org.uk>,
Catalin Marinas <catalin.marinas@arm.com>,
Andy Lutomirski <luto@amacapital.net>,
Dmitry Safonov <dsafonov@virtuozzo.com>,
John Stultz <john.stultz@linaro.org>,
Mark Rutland <mark.rutland@arm.com>,
Laura Abbott <labbott@redhat.com>,
Kees Cook <keescook@chromium.org>,
Ard Biesheuvel <ard.biesheuvel@linaro.org>,
Andy Gross <andy.gross@linaro.org>,
Kevin Brodsky <kevin.brodsky@arm.com>,
Andrew Pinski <apinski@cavium.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v4 00/12] arm+arm64: vdso unification to lib/vdso/
Date: Wed, 1 Nov 2017 09:40:16 +0000 [thread overview]
Message-ID: <20171101094015.GA14665@arm.com> (raw)
In-Reply-To: <64439dc3-909d-722f-68c3-d8e20e96ed9a@redhat.com>
On Tue, Oct 31, 2017 at 06:04:19PM -0400, Jon Masters wrote:
> On 10/31/2017 02:30 PM, Mark Salyzyn wrote:
> > Take an effort to recode the arm64 vdso code from assembler to C
> > previously submitted by Andrew Pinski <apinski@cavium.com>, rework
> > it for use in both arm and arm64, overlapping any optimizations
> > for each architecture. But instead of landing it in arm64, land the
> > result into lib/vdso and unify both implementations to simplify
> > future maintenance. This will act as the basis for implementing
> > arm64 vdso32 in the future.
>
> In the original patch series, our QE folks found a problem that lead to
> its revertion from our internal trees. I've pinged them to check this
> latest version and followup if we see the same failures now.
Could you elaborate a bit on the problem you found, please? Even if you
don't see it with this series, it doesn't mean it isn't lurking somewhere
else (potentially even in mainline!).
Will
next prev parent reply other threads:[~2017-11-01 9:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-31 18:30 [PATCH v4 00/12] arm+arm64: vdso unification to lib/vdso/ Mark Salyzyn
2017-10-31 22:04 ` Jon Masters
2017-11-01 9:40 ` Will Deacon [this message]
2017-11-01 14:45 ` Mark Salyzyn
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=20171101094015.GA14665@arm.com \
--to=will.deacon@arm.com \
--cc=andy.gross@linaro.org \
--cc=apinski@cavium.com \
--cc=ard.biesheuvel@linaro.org \
--cc=catalin.marinas@arm.com \
--cc=dsafonov@virtuozzo.com \
--cc=james.morse@arm.com \
--cc=jcm@redhat.com \
--cc=john.stultz@linaro.org \
--cc=keescook@chromium.org \
--cc=kevin.brodsky@arm.com \
--cc=labbott@redhat.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=luto@amacapital.net \
--cc=mark.rutland@arm.com \
--cc=salyzyn@android.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;
as well as URLs for NNTP newsgroup(s).