From: Dario Faggioli <dario.faggioli@citrix.com>
To: Juergen Gross <jgross@suse.com>,
Boris Ostrovsky <boris.ostrovsky@oracle.com>,
<xen-devel@lists.xenproject.org>, <linux-kernel@vger.kernel.org>
Cc: <sstabellini@kernel.org>, <david.vrabel@citrix.com>,
Tony S <suokunstar@gmail.com>
Subject: Re: [Xen-devel] [PATCH] xen: add steal_clock support on x86
Date: Wed, 18 May 2016 18:10:13 +0200 [thread overview]
Message-ID: <1463587813.5851.35.camel@citrix.com> (raw)
In-Reply-To: <573C81D1.9040309@suse.com>
[-- Attachment #1: Type: text/plain, Size: 1382 bytes --]
On Wed, 2016-05-18 at 16:53 +0200, Juergen Gross wrote:
> On 18/05/16 16:46, Boris Ostrovsky wrote:
> >
> > Won't we be accounting for stolen cycles twice now --- once from
> > steal_account_process_tick()->steal_clock() and second time from
> > do_stolen_accounting()?
> Uuh, yes.
>
> I guess I should rip do_stolen_accounting() out, too? It is a
> Xen-specific hack, so I guess nobody will cry. Maybe it would be a
> good idea to select CONFIG_PARAVIRT_TIME_ACCOUNTING for XEN then?
>
So, config options aside, if I understand this correctly, it looks like
we were actually already doing steal time accounting, although in a
non-standard way.
And yet, people seem to have issues relating to lack of (proper?) steal
time accounting (Cc-ing Tony).
I guess this means that, either:
- the issue being reported is actually not caused by the lack of
steal time accounting,
- our current (Xen specific) steal time accounting solution is flawed,
- the issue is caused by the lack of the bit of steal time accounting
that we do not support yet,
- other ideas? Tony?
Dario
--
<<This happens because I choose it to happen!>> (Raistlin Majere)
-----------------------------------------------------------------
Dario Faggioli, Ph.D, http://about.me/dario.faggioli
Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK)
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-05-18 16:10 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-18 12:15 [PATCH] xen: add steal_clock support on x86 Juergen Gross
2016-05-18 14:46 ` Boris Ostrovsky
2016-05-18 14:53 ` Juergen Gross
2016-05-18 15:25 ` Boris Ostrovsky
2016-05-18 15:25 ` Boris Ostrovsky
2016-05-18 15:42 ` Juergen Gross
2016-05-18 15:42 ` Juergen Gross
2016-05-18 15:45 ` David Vrabel
2016-05-18 15:45 ` David Vrabel
2016-05-18 15:51 ` Juergen Gross
2016-05-18 15:51 ` Juergen Gross
2016-05-18 15:52 ` David Vrabel
2016-05-18 15:52 ` David Vrabel
2016-05-18 15:53 ` Boris Ostrovsky
2016-05-18 15:53 ` Boris Ostrovsky
2016-05-18 16:00 ` Juergen Gross
2016-05-18 16:00 ` Juergen Gross
2016-05-18 16:13 ` Boris Ostrovsky
2016-05-19 5:33 ` Juergen Gross
2016-05-19 5:33 ` Juergen Gross
2016-05-18 16:13 ` Boris Ostrovsky
2016-05-18 16:10 ` Dario Faggioli [this message]
2016-05-18 17:20 ` [Xen-devel] " Boris Ostrovsky
2016-05-18 17:59 ` Tony S
2016-05-18 18:03 ` Tony S
2016-05-19 3:36 ` Dario Faggioli
2016-05-19 3:36 ` Dario Faggioli
2016-05-18 18:03 ` Tony S
2016-05-18 17:59 ` Tony S
2016-05-18 17:20 ` Boris Ostrovsky
2016-05-18 16:10 ` Dario Faggioli
2016-05-18 14:53 ` Juergen Gross
2016-05-18 14:46 ` Boris Ostrovsky
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=1463587813.5851.35.camel@citrix.com \
--to=dario.faggioli@citrix.com \
--cc=boris.ostrovsky@oracle.com \
--cc=david.vrabel@citrix.com \
--cc=jgross@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sstabellini@kernel.org \
--cc=suokunstar@gmail.com \
--cc=xen-devel@lists.xenproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.