Re: xen/arm: Domain not fully destroyed when using credit2

[Dario Faggioli <dario.faggioli@citrix.com>]

[-- Attachment #1.1: Type: text/plain, Size: 1405 bytes --]

On Tue, 2017-01-24 at 13:24 +0000, Julien Grall wrote:
> On 24/01/17 13:19, Dario Faggioli wrote:
> > How are Dom0 vCPUs pinned, exclusively (i.e., there are 2 pCPUs on
> > which _only_ Dom0 and _no_ DomU can run)?
> 
> I have dom0_vcpu_pins on Xen command line option (so I guess only 
> pinned?), no further configuration for DOM0.
> 
Ok, thanks. Yeah, that means Dom0 vCPU 0 is pinned to pCPU 0, and vCPU
1 is pinned to pCPU 1. And it's not excluside, i.e., other domains can
run on pCPUs 0 and 1, if the scheduler decides so (because they're
free, because the scheduler decides to preempt Dom0, etc).

This is of course fine, I just wanted to make sure I was understanding
the setup.

> > So, when you say "no interrupt traffic", do you perhaps mean that
> > SCHEDULE_SOFTIRQ is rarely (never!) raised for idle pCPUs? Or are
> > you
> > really talking about actual interrupts (either inter-processor or
> > not)?
> 
> I am talking about actual physical interrupts. The traffic is reduced
> to 
> none with credit2 on idle pCPU.
> 
Ah, wow... And how --forgive my naiveness-- do you measure / check
that?

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 #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

[-- Attachment #2: Type: text/plain, Size: 127 bytes --]

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