From: "Jan Beulich" <JBeulich@suse.com>
To: Stefan Bader <stefan.bader@canonical.com>
Cc: Andrew Cooper <andrew.cooper3@citrix.com>,
Ian Campbell <ian.campbell@citrix.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: Strange PVM spinlock case revisited (nailed down)
Date: Thu, 14 Feb 2013 14:48:57 +0000 [thread overview]
Message-ID: <511D076902000078000BE556@nat28.tlf.novell.com> (raw)
In-Reply-To: <511CF2D7.6090004@canonical.com>
>>> On 14.02.13 at 15:21, Stefan Bader <stefan.bader@canonical.com> wrote:
> Having more understanding now, I had a different idea. Not sure this is
> foolproof and surely is causing some more active spinning. But it looks like I
> also can keep the system from locking up (v3.2 kernel and the testcase) if I
> change xen_spin_unlock_slow to send the wakeup IPI to _all_ spinners instead
> of only the first one found.
That, afaict, is an absolute requirement with the open coded
lock that you pointed at, as otherwise the code makes a
pseudo ticket assumption in believing to know who's going to
be the next owner of the lock.
Jan
prev parent reply other threads:[~2013-02-14 14:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-08 15:33 Strange PVM spinlock case revisited Stefan Bader
2013-02-11 17:29 ` Ian Campbell
2013-02-12 13:42 ` Stefan Bader
2013-02-12 14:07 ` Ian Campbell
2013-02-12 14:50 ` Stefan Bader
2013-02-12 15:07 ` Ian Campbell
2013-02-12 15:53 ` Stefan Bader
2013-02-13 11:31 ` Stefan Bader
2013-02-13 12:16 ` Stefan Bader
2013-02-14 11:04 ` Strange PVM spinlock case revisited (nailed down) Stefan Bader
2013-02-14 11:43 ` Jan Beulich
2013-02-14 14:21 ` Stefan Bader
2013-02-14 14:48 ` Jan Beulich [this message]
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=511D076902000078000BE556@nat28.tlf.novell.com \
--to=jbeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=ian.campbell@citrix.com \
--cc=stefan.bader@canonical.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.