From: Christian Ehrhardt <ehrhardt@linux.vnet.ibm.com>
To: kvm-ppc@vger.kernel.org
Subject: Re: [PATCH] kvmppc_init_timing_stats: fix sleep with interrupts disabled
Date: Mon, 04 Oct 2010 05:22:14 +0000 [thread overview]
Message-ID: <4CA96486.4050004@linux.vnet.ibm.com> (raw)
In-Reply-To: <20100930192850.GA16941@udp111988uds.am.freescale.net>
On 10/01/2010 12:07 AM, Alexander Graf wrote:
>
> On 30.09.2010, at 21:28, Scott Wood wrote:
>
>> It is not legal to call mutex_lock() with interrupts disabled.
>> This will assert with debug checks enabled.
>>
>> If there's a real need to disable interrupts here, it could be done
>> after the mutex is acquired -- but I don't see why it's needed at all.
>
> Christian, IIRC this code is yours. Any comments?
Yes, It should be save to drop the irq_disable.
IIRC it was without the lock in early stages of development (pre
upstream git, so you can't see it) which had some obvious races.
But the lock makes it mutually exclusive per vcpu and should ensure it
isn't running - by that it should be fine.
Reviewed-by: Christian Ehrhardt <ehrhardt@linux.vnet.ibm.com>
> Alex
>
>>
>> Signed-off-by: Scott Wood<scottwood@freescale.com>
>> ---
>> arch/powerpc/kvm/timing.c | 2 --
>> 1 files changed, 0 insertions(+), 2 deletions(-)
>>
>> diff --git a/arch/powerpc/kvm/timing.c b/arch/powerpc/kvm/timing.c
>> index 46fa04f..a021f58 100644
>> --- a/arch/powerpc/kvm/timing.c
>> +++ b/arch/powerpc/kvm/timing.c
>> @@ -35,7 +35,6 @@ void kvmppc_init_timing_stats(struct kvm_vcpu *vcpu)
>> int i;
>>
>> /* pause guest execution to avoid concurrent updates */
>> - local_irq_disable();
>> mutex_lock(&vcpu->mutex);
>>
>> vcpu->arch.last_exit_type = 0xDEAD;
>> @@ -51,7 +50,6 @@ void kvmppc_init_timing_stats(struct kvm_vcpu *vcpu)
>> vcpu->arch.timing_last_enter.tv64 = 0;
>>
>> mutex_unlock(&vcpu->mutex);
>> - local_irq_enable();
>> }
>>
>> static void add_exit_timing(struct kvm_vcpu *vcpu, u64 duration, int type)
>> --
>> 1.7.0.4
>>
>> --
>> To unsubscribe from this list: send the line "unsubscribe kvm-ppc" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
--
Grüsse / regards, Christian Ehrhardt
IBM Linux Technology Center, System z Linux Performance
next prev parent reply other threads:[~2010-10-04 5:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-30 19:28 [PATCH] kvmppc_init_timing_stats: fix sleep with interrupts Scott Wood
2010-09-30 22:07 ` [PATCH] kvmppc_init_timing_stats: fix sleep with interrupts disabled Alexander Graf
2010-10-04 5:22 ` Christian Ehrhardt [this message]
2010-10-04 8:18 ` Alexander Graf
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=4CA96486.4050004@linux.vnet.ibm.com \
--to=ehrhardt@linux.vnet.ibm.com \
--cc=kvm-ppc@vger.kernel.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.