All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefano Stabellini <sstabellini@kernel.org>
To: Julien Grall <julien.grall@arm.com>
Cc: edgar.iglesias@xilinx.com,
	Stefano Stabellini <sstabellini@kernel.org>,
	george.dunlap@eu.citrix.com,
	Dario Faggioli <dario.faggioli@citrix.com>,
	xen-devel@lists.xen.org, nd@arm.com
Subject: Re: Xen on ARM IRQ latency and scheduler overhead
Date: Fri, 17 Feb 2017 14:55:04 -0800 (PST)	[thread overview]
Message-ID: <alpine.DEB.2.10.1702171454450.9566@sstabellini-ThinkPad-X260> (raw)
In-Reply-To: <69783c6d-1e65-3fa4-8b71-8c99d9e23eb6@arm.com>

On Fri, 17 Feb 2017, Julien Grall wrote:
> Hi Dario,
> 
> On 02/17/2017 06:40 PM, Dario Faggioli wrote:
> > On Thu, 2017-02-09 at 16:54 -0800, Stefano Stabellini wrote:
> > Actually, TSC on this box should be stable and invariant, so I guess I
> > can try with the default governor. Will do that on Monday. Does ARM
> > have frequency scaling (I did remember something on xen-devel, but I am
> > not sure whether it landed upstream)?
> 
> I guess you mean the series sent by globallogic ([1])? If so, it was never
> upstreamed.
> 
> However the frequency scaling may depend on the processor used and sometimes
> implemented using big.LITTLE (e.g the task has to switch).
> 
> I am not sure why it would matter in this case.
> 
> [1] https://lists.xenproject.org/archives/html/xen-devel/2014-10/msg00801.html

Not in this case, I have four A53s on this platform.

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

  reply	other threads:[~2017-02-17 22:55 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-10  0:54 Xen on ARM IRQ latency and scheduler overhead Stefano Stabellini
2017-02-10  8:40 ` Dario Faggioli
2017-02-10 18:32   ` Stefano Stabellini
2017-02-16 12:20     ` Dario Faggioli
2017-02-16 19:52       ` Stefano Stabellini
2017-02-16 23:07         ` Stefano Stabellini
2017-02-17 11:02           ` Dario Faggioli
2017-02-17 19:34             ` Julien Grall
2017-02-17 23:14               ` Stefano Stabellini
2017-02-18  0:02                 ` Stefano Stabellini
2017-02-18  0:47                   ` Dario Faggioli
2017-02-17 18:40 ` Dario Faggioli
2017-02-17 19:44   ` Julien Grall
2017-02-17 22:55     ` Stefano Stabellini [this message]
2017-02-18  0:59     ` Dario Faggioli
2017-02-20 12:18       ` Punit Agrawal
2017-02-18  0:41   ` Stefano Stabellini
2017-02-20 11:04     ` George Dunlap
2017-02-20 11:40       ` Dario Faggioli

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.10.1702171454450.9566@sstabellini-ThinkPad-X260 \
    --to=sstabellini@kernel.org \
    --cc=dario.faggioli@citrix.com \
    --cc=edgar.iglesias@xilinx.com \
    --cc=george.dunlap@eu.citrix.com \
    --cc=julien.grall@arm.com \
    --cc=nd@arm.com \
    --cc=xen-devel@lists.xen.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.