From: Stefan Bader <stefan.bader@canonical.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: Andrew Cooper <andrew.cooper3@citrix.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
Ian Campbell <Ian.Campbell@citrix.com>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Subject: Re: Xen PVM: Strange lockups when running PostgreSQL load
Date: Thu, 18 Oct 2012 09:24:58 +0200 [thread overview]
Message-ID: <507FAECA.3070506@canonical.com> (raw)
In-Reply-To: <507FC51102000078000A235E@nat28.tlf.novell.com>
[-- Attachment #1.1: Type: text/plain, Size: 886 bytes --]
On 18.10.2012 09:00, Jan Beulich wrote:
>>>> On 17.10.12 at 17:35, Andrew Cooper <andrew.cooper3@citrix.com> wrote:
>> In each case, the event channels are masked (no surprise given the
>> conversation so far on this thread), and have no pending events.
>> Therefore, I believe we are looking at the same bug.
>
> That seems very unlikely (albeit not impossible) to me, given that
> the non-pvops kernel uses ticket locks while the pvops one doesn't.
True, if classic 2.6.32 actually meant non-pvops. In my memory that was the
version that first introduced them, so I assumed we talk about the same base.
The one I am looking at seems (as much info there is available right now, but I
try to get confirmation from reporters running a non-paravirt-spinlock kernel on
a production load) to be related directly to the paravirtualized spinlock
implementation for Xen.
[-- 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-18 7:24 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
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 [this message]
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=507FAECA.3070506@canonical.com \
--to=stefan.bader@canonical.com \
--cc=Ian.Campbell@citrix.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.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.