From: Juergen Gross <juergen.gross@ts.fujitsu.com>
To: xen-devel <xen-devel@lists.xen.org>, Jan Beulich <JBeulich@suse.com>
Subject: backport request for Xen 4.2 and 4.1 of cs 26287:127c2c47d440
Date: Fri, 25 Jan 2013 10:49:26 +0100 [thread overview]
Message-ID: <51025526.3060105@ts.fujitsu.com> (raw)
Hi,
I request backport of changeset 26287:127c2c47d440 to Xen 4.2 and Xen 4.1.
Without this change we experience Dom0 lockups when cpupool0 has all cpus but
one on a single socket and xen ticketlocks are disabled in Dom0.
Some background information:
Disabling ticketlocks in Dom0 was done to avoid lock starvation on certain
workloads with one lock in Dom0 taken at a higher frequency as ticketlock
processing would allow (the poll hypercall was much more expensive than waiting
for the lock via spinning). In our configuration Dom0 is the only domain in
cpupool0 so using xen ticketlocks shouldn't be an advantage.
The Dom0 lockup happened when one vcpu was holding the xtime_lock while all
other vcpus tried to grab it and none of the vcpus was running on the single
core on the other socket. At some time all vcpus were spinning and the one
core was idle without being considered for vcpu migration (this should be
addressed by the changeset above). As none of the vcpus would give up control
voluntarily the complete time slice is used with one vcpu of Dom0 having no
physical processor to run on. During that time the next timer interrupt will
be pending leading to another request of the xtime_lock which will trigger the
same loop over and over again.
Juergen
--
Juergen Gross Principal Developer Operating Systems
PBG 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
next reply other threads:[~2013-01-25 9:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-25 9:49 Juergen Gross [this message]
2013-02-08 8:20 ` backport request for Xen 4.2 and 4.1 of cs 26287:127c2c47d440 Juergen Gross
2013-02-08 8:38 ` Jan Beulich
2013-02-08 8:45 ` 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=51025526.3060105@ts.fujitsu.com \
--to=juergen.gross@ts.fujitsu.com \
--cc=JBeulich@suse.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.