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>,
"linux@arm.linux.org.uk" <linux@arm.linux.org.uk>,
"arnd@arndb.de" <arnd@arndb.de>,
"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>,
"nico@linaro.org" <nico@linaro.org>,
"olof@lixom.net" <olof@lixom.net>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"cov@codeaurora.org" <cov@codeaurora.org>
Subject: Re: [Xen-devel] [PATCH RFC v2 2/4] arm: introduce CONFIG_PARAVIRT and pv_time_ops
Date: Tue, 7 May 2013 14:34:59 +0100 [thread overview]
Message-ID: <alpine.DEB.2.02.1305071433560.4147@kaball.uk.xensource.com> (raw)
In-Reply-To: <1367931376.26321.117.camel@zakaz.uk.xensource.com>
On Tue, 7 May 2013, Ian Campbell wrote:
> On Tue, 2013-05-07 at 13:15 +0100, Stefano Stabellini wrote:
> > On Tue, 7 May 2013, Ian Campbell wrote:
> > > On Mon, 2013-05-06 at 15:51 +0100, Stefano Stabellini wrote:
> > > > Introduce CONFIG_PARAVIRT on ARM.
> > >
> > > What about PARAVIRT_TIME_ACCOUNTING? I'm not sure what it is but it
> > > looks like a more lightweight version of pv stolen time?
> >
> > PARAVIRT_TIME_ACCOUNTING selects PARAVIRT on x86 :-)
>
> Ah, that's maybe what confused me.
>
> TBH its not at all clear to me what distinction the core code is trying
> to make with those two options, but do we not also want/need
> PARAVIRT_TIME_ACCOUNTING? Having reread the help text it seems to be
> some sort of "more accurate" accounting?
It is not clear to me either.
I think that you are right, we probably want PARAVIRT_TIME_ACCOUNTING too.
next prev parent reply other threads:[~2013-05-07 13:35 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 [this message]
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 ` [Xen-devel] " Ian Campbell
2013-05-07 11:58 ` 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=alpine.DEB.2.02.1305071433560.4147@kaball.uk.xensource.com \
--to=stefano.stabellini@eu.citrix.com \
--cc=Ian.Campbell@citrix.com \
--cc=arnd@arndb.de \
--cc=cov@codeaurora.org \
--cc=konrad.wilk@oracle.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=marc.zyngier@arm.com \
--cc=nico@linaro.org \
--cc=olof@lixom.net \
--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®