From: James Clark <james.clark@arm.com>
To: Will Deacon <will@kernel.org>
Cc: catalin.marinas@arm.com, kernel-team@android.com,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org,
acme@kernel.org, john.garry@huawei.com,
Jonathan Corbet <corbet@lwn.net>,
leo.yan@linaro.org, broonie@kernel.org,
linux-doc@vger.kernel.org, Mark Rutland <mark.rutland@arm.com>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v3 0/2] perf: arm64: Kernel support for Dwarf unwinding through SVE functions
Date: Fri, 23 Sep 2022 13:43:20 +0100 [thread overview]
Message-ID: <c8f9d6d2-4397-3bbd-da97-865cca56d73a@arm.com> (raw)
In-Reply-To: <20220923123633.GC13942@willie-the-truck>
On 23/09/2022 13:36, Will Deacon wrote:
> On Fri, Sep 23, 2022 at 10:32:15AM +0100, James Clark wrote:
>>
>>
>> On 22/09/2022 21:33, Will Deacon wrote:
>>> On Thu, 1 Sep 2022 14:26:56 +0100, James Clark wrote:
>>>> I'm resubmitting this with a few of the changes suggested by Will on V2.
>>>>
>>>> I haven't made any changes regarding the open questions about the
>>>> discoverability or saving the new reg and passing to output_sample()
>>>> because I think it's best to be consistent with the implementations on
>>>> other platforms first. I have explained in more detail on v2 [1].
>>>>
>>>> [...]
>>>
>>> Applied to will (for-next/perf), thanks!
>>>
>>> [1/2] perf: arm64: Add SVE vector granule register to user regs
>>> https://git.kernel.org/will/c/cbb0c02caf4b
>>> [2/2] arm64/sve: Add Perf extensions documentation
>>> https://git.kernel.org/will/c/1f2906d1e10a
>>>
>>> Cheers,
>>
>> Thanks Will. Sorry about the build, I will fix my config for next time.
>
> No problem. For some reason, I was unable to repro the failure locally.
> Maybe it's a GCC thing?
For me I needed CONFIG_HEADERS_INSTALL and CONFIG_UAPI_HEADER_TEST to
reproduce it. I was already using gcc, so not sure if it's depends on
that or not.
>
> Will
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2022-09-23 12:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-01 13:26 [PATCH v3 0/2] perf: arm64: Kernel support for Dwarf unwinding through SVE functions James Clark
2022-09-01 13:26 ` [PATCH v3 1/2] perf: arm64: Add SVE vector granule register to user regs James Clark
2022-09-01 13:26 ` [PATCH v3 2/2] arm64/sve: Add Perf extensions documentation James Clark
2022-09-01 13:33 ` Mark Brown
2022-09-20 10:28 ` James Clark
2022-09-22 14:04 ` [PATCH v3 0/2] perf: arm64: Kernel support for Dwarf unwinding through SVE functions Will Deacon
2022-09-22 14:31 ` James Clark
2022-09-22 20:57 ` Will Deacon
2022-09-22 20:33 ` Will Deacon
2022-09-23 9:32 ` James Clark
2022-09-23 12:36 ` Will Deacon
2022-09-23 12:43 ` James Clark [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=c8f9d6d2-4397-3bbd-da97-865cca56d73a@arm.com \
--to=james.clark@arm.com \
--cc=acme@kernel.org \
--cc=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=corbet@lwn.net \
--cc=john.garry@huawei.com \
--cc=kernel-team@android.com \
--cc=leo.yan@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=will@kernel.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