From: Stefan Bader <stefan.bader@canonical.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: Andrew Cooper <Andrew.Cooper3@citrix.com>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
Ian Campbell <Ian.Campbell@citrix.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: Xen PVM: Strange lockups when running PostgreSQL load
Date: Fri, 19 Oct 2012 09:10:30 +0200 [thread overview]
Message-ID: <5080FCE6.906@canonical.com> (raw)
In-Reply-To: <50806C0B.1060504@canonical.com>
[-- Attachment #1.1: Type: text/plain, Size: 833 bytes --]
On 18.10.2012 22:52, Stefan Bader wrote:
> On 18.10.2012 14:43, Stefan Bader wrote:
> So I tried below approach and that seems to be surviving the previously breaking
> testcase for much longer than anything I tried before.
>
> -Stefan
>
> From f2ebb6626f3e3a00932bf1f4f75265f826c7fba9 Mon Sep 17 00:00:00 2001
> From: Stefan Bader <stefan.bader@canonical.com>
> Date: Thu, 18 Oct 2012 21:40:37 +0200
> Subject: [PATCH 1/2] xen/pv-spinlock: Never enable interrupts in
> xen_spin_lock_slow()
>
Testcase ran the whole night without problems. Now re-started it with a cleaner
kernel (only the patch above applied and no debugging and it has again passed
the threshold it would have broken before.
-Stefan
Oh, just in case this *is* the solution, it should very definitely be marked
with a cc: stable.
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 897 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2012-10-19 7:10 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-17 13:10 Xen PVM: Strange lockups when running PostgreSQL load Stefan Bader
2012-10-17 13:28 ` Andrew Cooper
2012-10-17 13:45 ` Stefan Bader
2012-10-17 13:55 ` Ian Campbell
2012-10-17 15:21 ` Stefan Bader
2012-10-17 15:35 ` Andrew Cooper
2012-10-17 16:27 ` Stefan Bader
2012-10-17 17:46 ` Andrew Cooper
2012-10-18 7:00 ` Jan Beulich
2012-10-18 7:08 ` Jan Beulich
2012-10-18 7:38 ` Stefan Bader
2012-10-18 7:48 ` Ian Campbell
2012-10-18 10:20 ` Stefan Bader
2012-10-18 10:47 ` Jan Beulich
2012-10-18 12:43 ` Stefan Bader
2012-10-18 20:52 ` Stefan Bader
2012-10-19 7:10 ` Stefan Bader [this message]
2012-10-19 8:06 ` Jan Beulich
2012-10-19 8:33 ` Stefan Bader
2012-10-19 9:24 ` Jan Beulich
2012-10-19 14:03 ` Stefan Bader
2012-10-19 14:49 ` Jan Beulich
2012-10-19 14:57 ` Stefan Bader
2012-10-19 15:08 ` Jan Beulich
2012-10-19 15:21 ` Stefan Bader
2012-10-19 15:33 ` Jan Beulich
2012-10-18 7:24 ` Stefan Bader
2012-10-17 14:51 ` Jan Beulich
2012-10-17 15:12 ` Andrew Cooper
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=5080FCE6.906@canonical.com \
--to=stefan.bader@canonical.com \
--cc=Andrew.Cooper3@citrix.com \
--cc=Ian.Campbell@citrix.com \
--cc=JBeulich@suse.com \
--cc=konrad.wilk@oracle.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.