From: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: Stefano Stabellini <Stefano.Stabellini@eu.citrix.com>,
"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 3/3] xen/arm: account for stolen ticks
Date: Thu, 2 May 2013 11:38:12 +0100 [thread overview]
Message-ID: <alpine.DEB.2.02.1305021134160.5398@kaball.uk.xensource.com> (raw)
In-Reply-To: <1367482862.21869.28.camel@zakaz.uk.xensource.com>
On Thu, 2 May 2013, Ian Campbell wrote:
> On Wed, 2013-05-01 at 20:27 +0100, Stefano Stabellini wrote:
> > diff --git a/arch/arm/xen/enlighten.c b/arch/arm/xen/enlighten.c
> > index d30042e..8f040a0 100644
> > --- a/arch/arm/xen/enlighten.c
> > +++ b/arch/arm/xen/enlighten.c
> > @@ -14,6 +14,7 @@
> > #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 <linux/interrupt.h>
> > #include <linux/irqreturn.h>
> > @@ -172,6 +173,8 @@ static int __init xen_secondary_init(unsigned int cpu)
> > later ones fail to. */
> > per_cpu(xen_vcpu, cpu) = vcpup;
> > }
> > +
> > + xen_setup_runstate_info(cpu);
>
> Is this called for the boot processor too?
Yep.
> (do you have a linux-next branch where I can easily find the baseline
> for this series?)
git://git.kernel.org/pub/scm/linux/kernel/git/sstabellini/xen.git lost_ticks_1
It's based on my 3.9-rc3-smp-6 branch currently in linux-next (that is
based on 3.9-rc3).
However lost_ticks_1 is not in linux-next yet.
next prev parent reply other threads:[~2013-05-02 10:38 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-01 19:27 [PATCH 0/3] xen/arm: account for stolen ticks Stefano Stabellini
2013-05-01 19:27 ` [PATCH 1/3] arm_arch_timer: introduce arch_timer_stolen_ticks Stefano Stabellini
2013-05-01 20:36 ` Christopher Covington
2013-05-02 8:19 ` [Xen-devel] " Ian Campbell
2013-05-02 21:33 ` Christopher Covington
2013-05-03 10:43 ` Stefano Stabellini
2013-05-03 10:54 ` Marc Zyngier
2013-05-05 16:47 ` Stefano Stabellini
2013-05-06 14:55 ` Christopher Covington
2013-05-06 14:35 ` Konrad Rzeszutek Wilk
2013-05-07 16:17 ` Christopher Covington
2013-05-08 11:19 ` Stefano Stabellini
2013-05-08 11:48 ` Christopher Covington
2013-05-01 19:27 ` [PATCH 2/3] xen: move do_stolen_accounting to drivers/xen/time.c Stefano Stabellini
2013-05-02 8:19 ` [Xen-devel] " Ian Campbell
2013-05-02 18:49 ` Christopher Covington
2013-05-03 8:26 ` [Xen-devel] " Ian Campbell
2013-05-03 10:29 ` Stefano Stabellini
2013-05-01 19:27 ` [PATCH 3/3] xen/arm: account for stolen ticks Stefano Stabellini
2013-05-02 8:21 ` [Xen-devel] " Ian Campbell
2013-05-02 10:38 ` Stefano Stabellini [this message]
2013-05-02 10:48 ` Ian Campbell
2013-05-02 10:54 ` Stefano Stabellini
2013-05-02 11:02 ` Ian Campbell
2013-05-02 11:04 ` Stefano Stabellini
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=alpine.DEB.2.02.1305021134160.5398@kaball.uk.xensource.com \
--to=stefano.stabellini@eu.citrix.com \
--cc=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=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;
as well as URLs for NNTP newsgroup(s).