From: "Jan Beulich" <JBeulich@novell.com>
To: Ian Campbell <Ian.Campbell@eu.citrix.com>
Cc: "salvet@ics.muni.cz" <salvet@ics.muni.cz>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: [PATCH] linux/x86: eliminate nesting of run-queue locks inside xtime_lock
Date: Tue, 10 Aug 2010 15:41:01 +0100 [thread overview]
Message-ID: <4C61811D020000780000F149@vpn.id2.novell.com> (raw)
In-Reply-To: <1281450319.24292.3945.camel@zakaz.uk.xensource.com>
>>> On 10.08.10 at 16:25, Ian Campbell <Ian.Campbell@eu.citrix.com> wrote:
> On Tue, 2010-08-10 at 15:10 +0100, Jan Beulich wrote:
>> From: Zdenek Salvet <salvet@ics.muni.cz>
>>
>> According to Debian bug 591362 this has been causing problems. While
>> no proof was given that the inverse lock order does actually occur
>> anywhere (with interrupts enabled), it is plain unnecessary to take
>> the risk.
>>
>> Signed-off-by: Jan Beulich <jbeulich@novell.com>
>
> I'm right in thinking this is for traditional Xen/Linux kernel only,
> aren't I?
Yes, absolutely.
Jan
prev parent reply other threads:[~2010-08-10 14:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-10 14:10 [PATCH] linux/x86: eliminate nesting of run-queue locks inside xtime_lock Jan Beulich
2010-08-10 14:25 ` Ian Campbell
2010-08-10 14:41 ` 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=4C61811D020000780000F149@vpn.id2.novell.com \
--to=jbeulich@novell.com \
--cc=Ian.Campbell@eu.citrix.com \
--cc=salvet@ics.muni.cz \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).