From: Olaf Hering <olaf@aepfle.de>
To: Keir Fraser <keir@xen.org>
Cc: xen-devel@lists.xensource.com
Subject: Re: Need help with fixing the Xen waitqueue feature
Date: Tue, 22 Nov 2011 18:36:18 +0100 [thread overview]
Message-ID: <20111122173618.GA1304@aepfle.de> (raw)
In-Reply-To: <CAF172FF.34839%keir@xen.org>
On Tue, Nov 22, Keir Fraser wrote:
> I have a new theory, which is that if we go round the for-loop in
> wait_event() more than once, the vcpu's pause counter gets messed up and
> goes negative, condemning it to sleep forever.
I have added a check for that, its not negative.
> I have *just* pushed a change to the debug 'q' key (ignore the changeset
> comment referring to 'd' key, I got that wrong!) which will print per-vcpu
> and per-domain pause_count values. Please get the system stuck again, and
> send the output from 'q' key with that new changeset (c/s 24178).
To me it looks like dom0 gets paused, perhaps due to some uneven pause/unpause calls.
I will see if I can figure it out.
Olaf
(XEN) 'q' pressed -> dumping domain info (now=0xA1:4BC733CC)
(XEN) General information for domain 0:
(XEN) refcnt=3 dying=0 pause_count=0
(XEN) nr_pages=5991502 xenheap_pages=5 dirty_cpus={} max_pages=4294967295
(XEN) handle=00000000-0000-0000-0000-000000000000 vm_assist=00000004
(XEN) Rangesets belonging to domain 0:
(XEN) I/O Ports { 0-1f, 22-3f, 44-60, 62-9f, a2-3f7, 400-407, 40c-cfb, d00-ffff }
(XEN) Interrupts { 0-303 }
(XEN) I/O Memory { 0-febff, fec01-fec8f, fec91-fedff, fee01-ffffffffffffffff }
(XEN) Memory pages belonging to domain 0:
(XEN) DomPage list too long to display
(XEN) XenPage 000000000036ff8d: caf=c000000000000002, taf=7400000000000002
(XEN) XenPage 000000000036ff8c: caf=c000000000000001, taf=7400000000000001
(XEN) XenPage 000000000036ff8b: caf=c000000000000001, taf=7400000000000001
(XEN) XenPage 000000000036ff8a: caf=c000000000000001, taf=7400000000000001
(XEN) XenPage 000000000008befd: caf=c000000000000002, taf=7400000000000002
(XEN) VCPU information and callbacks for domain 0:
(XEN) VCPU0: CPU0 [has=F] poll=0 upcall_pend = 01, upcall_mask = 00 dirty_cpus={} cpu_affinity={0}
(XEN) pause_count=1 pause_flags=0
(XEN) 250 Hz periodic timer (period 4 ms)
(XEN) General information for domain 1:
(XEN) refcnt=3 dying=0 pause_count=0
(XEN) nr_pages=17549 xenheap_pages=6 dirty_cpus={} max_pages=131328
(XEN) handle=5499728e-7f38-dbb0-b6cc-22866a6864f3 vm_assist=00000000
(XEN) paging assistance: hap refcounts translate external
(XEN) Rangesets belonging to domain 1:
(XEN) I/O Ports { }
(XEN) Interrupts { }
(XEN) I/O Memory { }
(XEN) Memory pages belonging to domain 1:
(XEN) DomPage list too long to display
(XEN) PoD entries=0 cachesize=0
(XEN) XenPage 0000000000200b7c: caf=c000000000000001, taf=7400000000000001
(XEN) XenPage 0000000000203bfe: caf=c000000000000001, taf=7400000000000001
(XEN) XenPage 0000000000200b48: caf=c000000000000001, taf=7400000000000001
(XEN) XenPage 000000000021291d: caf=c000000000000001, taf=7400000000000001
(XEN) XenPage 000000000003ebfc: caf=c000000000000001, taf=7400000000000001
(XEN) XenPage 0000000000202ef4: caf=c000000000000001, taf=7400000000000001
(XEN) VCPU information and callbacks for domain 1:
(XEN) VCPU0: CPU0 [has=F] poll=0 upcall_pend = 00, upcall_mask = 00 dirty_cpus={} cpu_affinity={0}
(XEN) pause_count=0 pause_flags=4
(XEN) paging assistance: hap, 4 levels
(XEN) No periodic timer
(XEN) Notifying guest 0:0 (virq 1, port 0, stat 0/-1/-1)
(XEN) Notifying guest 1:0 (virq 1, port 0, stat 0/0/0)
next prev parent reply other threads:[~2011-11-22 17:36 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20111122150755.GA18727@aepfle.de>
2011-11-22 15:40 ` Need help with fixing the Xen waitqueue feature Keir Fraser
2011-11-22 15:54 ` Keir Fraser
2011-11-22 17:36 ` Olaf Hering [this message]
2011-11-22 17:42 ` Keir Fraser
2011-11-22 18:04 ` Olaf Hering
2011-11-22 21:15 ` Olaf Hering
2011-11-22 21:53 ` Keir Fraser
2011-11-23 17:00 ` Olaf Hering
2011-11-23 17:16 ` Keir Fraser
2011-11-23 18:06 ` Olaf Hering
2011-11-23 18:23 ` Keir Fraser
2011-11-23 18:18 ` Keir Fraser
2011-11-23 18:31 ` Olaf Hering
2011-11-23 19:21 ` Keir Fraser
2011-11-23 21:03 ` Keir Fraser
2011-11-23 22:30 ` Olaf Hering
2011-11-23 23:12 ` Keir Fraser
2011-11-24 10:00 ` Olaf Hering
2011-11-25 12:56 ` Olaf Hering
2011-11-25 18:26 ` Olaf Hering
2011-11-25 19:35 ` Keir Fraser
2011-11-24 9:15 ` Jan Beulich
2011-11-24 9:51 ` Keir Fraser
2011-11-24 9:58 ` Keir Fraser
[not found] <20111108224414.83985CF73A@homiemail-mx7.g.dreamhost.com>
2011-11-09 3:52 ` Andres Lagar-Cavilla
2011-11-09 7:09 ` Olaf Hering
2011-11-09 21:21 ` Andres Lagar-Cavilla
2011-11-22 14:34 ` George Dunlap
2011-11-09 21:30 ` Andres Lagar-Cavilla
2011-11-09 22:11 ` Olaf Hering
2011-11-10 4:29 ` Andres Lagar-Cavilla
2011-11-10 9:20 ` Jan Beulich
2011-11-10 9:26 ` Keir Fraser
2011-11-10 10:18 ` Olaf Hering
2011-11-10 12:05 ` Olaf Hering
[not found] <20111108214540.EAEBB72C4A1@homiemail-mx8.g.dreamhost.com>
2011-11-09 3:37 ` Andres Lagar-Cavilla
2011-11-09 7:02 ` Olaf Hering
2011-11-08 21:20 Olaf Hering
2011-11-08 22:05 ` Keir Fraser
2011-11-08 22:20 ` Olaf Hering
2011-11-08 22:54 ` Keir Fraser
2011-11-11 22:56 ` Olaf Hering
2011-11-12 7:00 ` Keir Fraser
2011-11-22 11:40 ` Olaf Hering
2011-11-22 13:04 ` Keir Fraser
2011-11-22 13:54 ` Olaf Hering
2011-11-22 14:24 ` Keir Fraser
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=20111122173618.GA1304@aepfle.de \
--to=olaf@aepfle.de \
--cc=keir@xen.org \
--cc=xen-devel@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.