From: cov@codeaurora.org (Christopher Covington)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v11 3/5] arm: introduce CONFIG_PARAVIRT, PARAVIRT_TIME_ACCOUNTING and pv_time_ops
Date: Fri, 20 Nov 2015 09:36:00 -0500 [thread overview]
Message-ID: <564F2FD0.6040905@codeaurora.org> (raw)
In-Reply-To: <alpine.DEB.2.02.1511201430200.1107@kaball.uk.xensource.com>
Hi Stefano,
On 11/20/2015 09:31 AM, Stefano Stabellini wrote:
> On Tue, 10 Nov 2015, Stefano Stabellini wrote:
>> On Thu, 5 Nov 2015, Stefano Stabellini wrote:
>>> Introduce CONFIG_PARAVIRT and PARAVIRT_TIME_ACCOUNTING on ARM.
>>>
>>> The only paravirt interface supported is pv_time_ops.steal_clock, so no
>>> runtime pvops patching needed.
>>>
>>> This allows us to make use of steal_account_process_tick for stolen
>>> ticks accounting.
>>>
>>> Signed-off-by: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
>>> Acked-by: Christopher Covington <cov@codeaurora.org>
>>> Acked-by: Ian Campbell <ian.campbell@citrix.com>
>>> CC: linux at arm.linux.org.uk
>>> CC: will.deacon at arm.com
>>> CC: nico at linaro.org
>>> CC: marc.zyngier at arm.com
>>> CC: cov at codeaurora.org
>>> CC: arnd at arndb.de
>>> CC: olof at lixom.net
>>
>>
>> Russell,
>> are you OK with this patch?
>
> Russell,
>
> I am going to drop this patch and add a small #ifdef to
> arch/arm/xen/enlighten.c to be able to use this functionality on arm64.
>
> If you change your mind let me know.
It appears to me as though he's not copied on this message.
Regards,
Christopher Covington
--
Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
a Linux Foundation Collaborative Project
next prev parent reply other threads:[~2015-11-20 14:36 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-05 15:33 [PATCH v11 0/5] xen/arm/arm64: CONFIG_PARAVIRT and stolen ticks accounting Stefano Stabellini
2015-11-05 15:34 ` [PATCH v11 1/5] xen: move xen_setup_runstate_info and get_runstate_snapshot to drivers/xen/time.c Stefano Stabellini
2015-11-05 16:48 ` Mark Rutland
2015-11-06 11:11 ` Stefano Stabellini
2015-11-06 12:00 ` Mark Rutland
2015-11-05 15:34 ` [PATCH v11 2/5] missing include asm/paravirt.h in cputime.c Stefano Stabellini
2015-11-05 16:40 ` Peter Zijlstra
2015-11-05 17:30 ` Stefano Stabellini
2015-11-09 17:36 ` Peter Zijlstra
2015-11-10 11:27 ` Stefano Stabellini
2015-11-10 12:19 ` Peter Zijlstra
2015-11-05 15:34 ` [PATCH v11 3/5] arm: introduce CONFIG_PARAVIRT, PARAVIRT_TIME_ACCOUNTING and pv_time_ops Stefano Stabellini
2015-11-10 14:12 ` Stefano Stabellini
2015-11-20 14:31 ` Stefano Stabellini
2015-11-20 14:36 ` Christopher Covington [this message]
2015-11-20 14:40 ` Stefano Stabellini
2015-11-20 16:47 ` Russell King - ARM Linux
2015-11-20 17:16 ` Stefano Stabellini
2015-11-05 15:34 ` [PATCH v11 4/5] arm64: " Stefano Stabellini
2015-11-10 14:11 ` Stefano Stabellini
2015-11-17 17:29 ` Will Deacon
2015-11-17 17:34 ` Marc Zyngier
2015-11-17 17:35 ` Will Deacon
2015-11-20 12:19 ` Stefano Stabellini
2015-11-05 15:34 ` [PATCH v11 5/5] xen/arm: account for stolen ticks Stefano Stabellini
2015-11-05 16:57 ` Mark Rutland
2015-11-06 11:39 ` Stefano Stabellini
2015-11-06 11:41 ` David Vrabel
2015-11-06 11:59 ` Mark Rutland
2015-11-06 13:25 ` Vitaly Kuznetsov
2015-11-06 13:19 ` Vitaly Kuznetsov
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=564F2FD0.6040905@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).