From: Ian Campbell <Ian.Campbell@citrix.com>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
"marc.zyngier@arm.com" <marc.zyngier@arm.com>,
"konrad.wilk@oracle.com" <konrad.wilk@oracle.com>,
"will.deacon@arm.com" <will.deacon@arm.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [Xen-devel] [PATCH RFC v2 4/4] xen/arm: account for stolen ticks
Date: Tue, 7 May 2013 10:17:50 +0100 [thread overview]
Message-ID: <1367918270.26321.39.camel@zakaz.uk.xensource.com> (raw)
In-Reply-To: <1367851878-21629-4-git-send-email-stefano.stabellini@eu.citrix.com>
On Mon, 2013-05-06 at 15:51 +0100, Stefano Stabellini wrote:
> Register the runstate_memory_area with the hypervisor.
> Use pv_time_ops.steal_clock to account for stolen ticks.
>
> Signed-off-by: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
> ---
> arch/arm/xen/enlighten.c | 23 +++++++++++++++++++++++
> 1 files changed, 23 insertions(+), 0 deletions(-)
>
> diff --git a/arch/arm/xen/enlighten.c b/arch/arm/xen/enlighten.c
> index ee86bfa..2a5cc82 100644
> --- a/arch/arm/xen/enlighten.c
> +++ b/arch/arm/xen/enlighten.c
> @@ -14,7 +14,10 @@
> #include <xen/xen-ops.h>
> #include <asm/xen/hypervisor.h>
> #include <asm/xen/hypercall.h>
> +#include <asm/arch_timer.h>
> #include <asm/system_misc.h>
> +#include <asm/paravirt.h>
> +#include <linux/jump_label.h>
> #include <linux/interrupt.h>
> #include <linux/irqreturn.h>
> #include <linux/module.h>
> @@ -152,6 +155,20 @@ int xen_unmap_domain_mfn_range(struct vm_area_struct *vma,
> }
> EXPORT_SYMBOL_GPL(xen_unmap_domain_mfn_range);
>
> +unsigned long long xen_stolen_accounting(int cpu)
> +{
> + struct vcpu_runstate_info state;
> +
> + if (cpu != get_cpu())
get_cpu disables preempt, so you need a matching put_cpu.
But actually I think you just want smp_processor_id and you probably
want the BUG_ON form to get unlikely etc.
That said, you don't use cpu for anything else, so why not drop it
entirely?
> + BUG();
> +
> + xen_get_runstate_snapshot(&state);
> +
> + WARN_ON(state.state != RUNSTATE_running);
> +
> + return state.time[RUNSTATE_runnable] + state.time[RUNSTATE_offline];
> +}
> +
> static void __init xen_percpu_init(void *unused)
> {
> struct vcpu_register_vcpu_info info;
> @@ -170,6 +187,8 @@ static void __init xen_percpu_init(void *unused)
> BUG();
> per_cpu(xen_vcpu, cpu) = vcpup;
>
> + xen_setup_runstate_info(cpu);
> +
> enable_percpu_irq(xen_events_irq, 0);
> }
>
> @@ -301,6 +320,10 @@ static int __init xen_init_events(void)
>
> on_each_cpu(xen_percpu_init, NULL, 0);
>
> + pv_time_ops.steal_clock = xen_stolen_accounting;
> + static_key_slow_inc(¶virt_steal_enabled);
> + static_key_slow_inc(¶virt_steal_rq_enabled);
We don't seem to do this on x86 -- is that a bug on x86 on Xen?
> +
> return 0;
> }
> postcore_initcall(xen_init_events);
next prev parent reply other threads:[~2013-05-07 9:17 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-06 14:50 [PATCH RFC v2 0/4] xen/arm: CONFIG_PARAVIRT and stolen ticks accounting Stefano Stabellini
2013-05-06 14:51 ` [PATCH RFC v2 1/4] xen: move xen_setup_runstate_info and get_runstate_snapshot to drivers/xen/time.c Stefano Stabellini
2013-05-06 14:51 ` [PATCH RFC v2 2/4] arm: introduce CONFIG_PARAVIRT and pv_time_ops Stefano Stabellini
2013-05-07 9:23 ` [Xen-devel] " Ian Campbell
2013-05-07 12:15 ` Stefano Stabellini
2013-05-07 12:56 ` Ian Campbell
2013-05-07 13:34 ` Stefano Stabellini
2013-05-06 14:51 ` [PATCH RFC v2 3/4] kernel: missing include in cputime.c Stefano Stabellini
2013-05-06 14:51 ` [PATCH RFC v2 4/4] xen/arm: account for stolen ticks Stefano Stabellini
2013-05-07 9:17 ` Ian Campbell [this message]
2013-05-07 11:58 ` [Xen-devel] " Stefano Stabellini
2013-05-07 12:56 ` Ian Campbell
2013-05-07 13:49 ` Stefano Stabellini
2013-05-07 13:33 ` Konrad Rzeszutek Wilk
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=1367918270.26321.39.camel@zakaz.uk.xensource.com \
--to=ian.campbell@citrix.com \
--cc=konrad.wilk@oracle.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marc.zyngier@arm.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=will.deacon@arm.com \
--cc=xen-devel@lists.xensource.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
all inboxes | Powered by JetHome®