From: mark.rutland@arm.com (Mark Rutland)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v11 5/5] xen/arm: account for stolen ticks
Date: Thu, 5 Nov 2015 16:57:43 +0000 [thread overview]
Message-ID: <20151105165743.GG32247@leverpostej> (raw)
In-Reply-To: <1446737696-9749-5-git-send-email-stefano.stabellini@eu.citrix.com>
> static void xen_percpu_init(void)
> {
> struct vcpu_register_vcpu_info info;
> @@ -104,6 +120,8 @@ static void xen_percpu_init(void)
> BUG_ON(err);
> per_cpu(xen_vcpu, cpu) = vcpup;
>
> + xen_setup_runstate_info(cpu);
Does the runstate memory area get unregsitered when a kernel tears
things down, or is kexec somehow inhibited for xen guests?
i couldn't spot either happening, but I may have missed it.
Mark.
> +
> after_register_vcpu_info:
> enable_percpu_irq(xen_events_irq, 0);
> put_cpu();
> @@ -271,6 +289,9 @@ static int __init xen_guest_init(void)
>
> register_cpu_notifier(&xen_cpu_notifier);
>
> + pv_time_ops.steal_clock = xen_stolen_accounting;
> + static_key_slow_inc(¶virt_steal_enabled);
> +
> return 0;
> }
> early_initcall(xen_guest_init);
> --
> 1.7.10.4
>
>
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
>
next prev parent reply other threads:[~2015-11-05 16:57 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
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 [this message]
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=20151105165743.GG32247@leverpostej \
--to=mark.rutland@arm.com \
--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).