All of lore.kernel.org
 help / color / mirror / Atom feed
From: Juergen Gross <juergen.gross@ts.fujitsu.com>
To: andrewpitman@comcast.net, George Dunlap <george.dunlap@eu.citrix.com>
Cc: xen-devel@lists.xensource.com, xen-users@lists.xensource.com
Subject: Re: Re: [Xen-users] Xen 4.1.1 crash when manipulating cpupools.
Date: Mon, 14 Nov 2011 10:58:18 +0100	[thread overview]
Message-ID: <4EC0E63A.6050707@ts.fujitsu.com> (raw)
In-Reply-To: <4EC0DD6A.7040007@ts.fujitsu.com>


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

On 11/14/2011 10:20 AM, Juergen Gross wrote:
> On 11/11/2011 10:18 PM, andrewpitman@comcast.net wrote:
>> Juergen,
>>
>> It doesn't look like this has been fixed.  I managed to get my 4.1.2 server 
>> to crash when setting the weight of Domain-0 (running in Pool-0 using 
>> credit2) and again when moving some cpus into a new cpupool which was set 
>> up to use the credit2 scheduler.
>
> Yeah, I could reproduce your problems on my machine.
>
> George, I see two problems in credit2:
>
> - when setting the weight of dom0, vcpu_schedule_lock_irq(current) will be
>   taken in sched_adjust() of schedule.c and again in csched_dom_cntl() of
>   sched_credit2.c resulting in a deadlock.
>
> - removing a cpu from a cpupool seems not to work for credit2. I removed all
>   but cpu 0 from Pool-0 and the dom0 vcpus were all active on cpus 1-3. It
>   took some time until they moved to cpu 0 (verified via 'r' hotkey on the
>   xen console).

IMO the problem is choose_cpu() not using CSCHED_CPUONLINE(). The comment

         /* Leave it where it is for now.  When we actually pay attention
          * to affinity we'll have to figure something out... */

suggests the solution isn't too easy...


Juergen

-- 
Juergen Gross                 Principal Developer Operating Systems
PDG ES&S SWE OS6                       Telephone: +49 (0) 89 3222 2967
Fujitsu Technology Solutions              e-mail: juergen.gross@ts.fujitsu.com
Domagkstr. 28                           Internet: ts.fujitsu.com
D-80807 Muenchen                 Company details: ts.fujitsu.com/imprint.html


[-- Attachment #1.2: Type: text/html, Size: 2935 bytes --]

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

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

  reply	other threads:[~2011-11-14  9:58 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <95606920.636453.1310736697756.JavaMail.root@sz0032a.westchester.pa.mail.comcast.net>
     [not found] ` <1324163226.639762.1310740209589.JavaMail.root@sz0032a.westchester.pa.mail.comcast.net>
2011-07-21 12:58   ` [Xen-users] Xen 4.1.1 crash when manipulating cpupools Pasi Kärkkäinen
2011-07-21 13:15     ` [Xen-devel] " Juergen Gross
2011-07-21 13:47       ` Re: [Xen-users] " George Dunlap
2011-08-02 19:44         ` [Xen-devel] " andrewpitman
2011-08-03 18:09           ` Re: [Xen-users] " George Dunlap
2011-11-08 16:14             ` [Xen-devel] " andrewpitman
2011-11-09  9:55               ` Re: [Xen-users] " Juergen Gross
2011-11-11 21:18                 ` andrewpitman
2011-11-14  9:20                   ` Juergen Gross
2011-11-14  9:58                     ` Juergen Gross [this message]
2011-11-14 11:13                     ` George Dunlap
2011-11-14 11:27                       ` Juergen Gross

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=4EC0E63A.6050707@ts.fujitsu.com \
    --to=juergen.gross@ts.fujitsu.com \
    --cc=andrewpitman@comcast.net \
    --cc=george.dunlap@eu.citrix.com \
    --cc=xen-devel@lists.xensource.com \
    --cc=xen-users@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 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.