From: Stefan Bader <stefan.bader@canonical.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: stefano.stabellini@eu.citrix.com, xen-devel@lists.xensource.com,
linux-kernel@vger.kernel.org
Subject: Re: [Xen-devel] [PATCH] xen: disable PV spinlocks on HVM
Date: Tue, 06 Sep 2011 10:18:08 -0700 [thread overview]
Message-ID: <4E6655D0.2080606@canonical.com> (raw)
In-Reply-To: <20110906170255.GA29839@dumpdata.com>
On 06.09.2011 10:02, Konrad Rzeszutek Wilk wrote:
> On Tue, Sep 06, 2011 at 05:41:47PM +0100, stefano.stabellini@eu.citrix.com wrote:
>> From: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
>>
>> PV spinlocks cannot possibly work with the current code because they are
>> enabled after pvops patching has already been done, and because PV
>> spinlocks use a different data structure than native spinlocks so we
>> cannot switch between them dynamically. A spinlock that has been taken
>> once by the native code (__ticket_spin_lock) cannot be taken by
>> __xen_spin_lock even after it has been released.
>
> Let me stick it on my 3.1-rc5 bug-fix list and add stable@kernel.org to it.
>
> Stefan, if you have some time this week, and can test it - I can also
> stick 'Tested-by' if you would like.
>
> Thinking to send the patches on Friday.
>
>>
>> Reported-by: Stefan Bader <stefan.bader@canonical.com>
>> Signed-off-by: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
>> ---
>> arch/x86/xen/smp.c | 1 -
>> 1 files changed, 0 insertions(+), 1 deletions(-)
>>
>> diff --git a/arch/x86/xen/smp.c b/arch/x86/xen/smp.c
>> index e79dbb9..51339b4 100644
>> --- a/arch/x86/xen/smp.c
>> +++ b/arch/x86/xen/smp.c
>> @@ -522,7 +522,6 @@ static void __init xen_hvm_smp_prepare_cpus(unsigned int max_cpus)
>> WARN_ON(xen_smp_intr_init(0));
>>
>> xen_init_lock_cpu(0);
>> - xen_init_spinlocks();
>> }
>>
>> static int __cpuinit xen_hvm_cpu_up(unsigned int cpu)
>> --
>> 1.7.2.3
>>
>>
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@lists.xensource.com
>> http://lists.xensource.com/xen-devel
I'll try. Currently I only got a version tested that takes out the
xen_init_lock_cpu calls as well.
-Stefan
next prev parent reply other threads:[~2011-09-06 17:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-06 16:41 [PATCH] xen: disable PV spinlocks on HVM stefano.stabellini
2011-09-06 17:02 ` [Xen-devel] " Konrad Rzeszutek Wilk
2011-09-06 17:18 ` Stefan Bader [this message]
2011-09-07 20:22 ` Stefan Bader
2011-09-07 21:24 ` Jeremy Fitzhardinge
2011-09-08 12:45 ` Stefano Stabellini
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=4E6655D0.2080606@canonical.com \
--to=stefan.bader@canonical.com \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stefano.stabellini@eu.citrix.com \
--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).