[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.02.1305061532310.4756@kaball.uk.xensource.com>
Date: Mon, 6 May 2013 15:50:22 +0100
From: Stefano Stabellini <stefano.stabellini@...citrix.com>
To: "xen-devel@...ts.xensource.com" <xen-devel@...ts.xensource.com>
CC: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
Konrad Rzeszutek Wilk <konrad.wilk@...cle.com>,
"marc.zyngier@....com" <marc.zyngier@....com>,
Will Deacon <will.deacon@....com>,
Stefano Stabellini <Stefano.Stabellini@...citrix.com>
Subject: [PATCH RFC v2 0/4] xen/arm: CONFIG_PARAVIRT and stolen ticks
accounting
Hi all,
this patch series introduces stolen ticks accounting for Xen on ARM.
Stolen ticks are clocksource ticks that have been "stolen" from the cpu,
typically because Linux is running in a virtual machine and the vcpu has
been descheduled.
To account for these ticks we introduce CONFIG_PARAVIRT and pv_time_ops
so that we can make use of:
kernel/sched/cputime.c:steal_account_process_tick
Stefano Stabellini (4):
xen: move xen_setup_runstate_info and get_runstate_snapshot to drivers/xen/time.c
arm: introduce CONFIG_PARAVIRT and pv_time_ops
kernel: missing include in cputime.c
xen/arm: account for stolen ticks
arch/arm/Kconfig | 9 ++++
arch/arm/include/asm/paravirt.h | 19 ++++++++
arch/arm/kernel/Makefile | 1 +
arch/arm/kernel/paravirt.c | 32 ++++++++++++++
arch/arm/xen/enlighten.c | 23 ++++++++++
arch/ia64/xen/time.c | 48 +++------------------
arch/x86/xen/time.c | 76 +--------------------------------
drivers/xen/Makefile | 2 +-
drivers/xen/time.c | 91 +++++++++++++++++++++++++++++++++++++++
include/xen/xen-ops.h | 5 ++
kernel/sched/cputime.c | 1 +
11 files changed, 189 insertions(+), 118 deletions(-)
create mode 100644 arch/arm/include/asm/paravirt.h
create mode 100644 arch/arm/kernel/paravirt.c
create mode 100644 drivers/xen/time.c
Cheers,
Stefano
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists