From: Jan Blunck <jblunck@suse.de>
To: rt-users <linux-rt-users@vger.kernel.org>
Cc: kvm@vger.kernel.org
Subject: [patch 2/3] kvm: convert spin-locks to raw_spinlock_t
Date: Wed, 08 Apr 2009 01:58:55 +0200 [thread overview]
Message-ID: <20090407235902.400480759@suse.de> (raw)
In-Reply-To: 20090407235853.309888494@suse.de
[-- Attachment #1: patches.rt/kvm-pic.diff --]
[-- Type: text/plain, Size: 953 bytes --]
This patch converts some KVM spin-locks to be of type raw_spinlock_t.
Signed-off-by: Jan Blunck <jblunck@suse.de>
---
arch/x86/kvm/i8254.h | 2 +-
arch/x86/kvm/irq.h | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
Index: b/arch/x86/kvm/i8254.h
===================================================================
--- a/arch/x86/kvm/i8254.h
+++ b/arch/x86/kvm/i8254.h
@@ -33,7 +33,7 @@ struct kvm_kpit_state {
u32 speaker_data_on;
struct mutex lock;
struct kvm_pit *pit;
- spinlock_t inject_lock;
+ raw_spinlock_t inject_lock;
unsigned long irq_ack;
struct kvm_irq_ack_notifier irq_ack_notifier;
};
Index: b/arch/x86/kvm/irq.h
===================================================================
--- a/arch/x86/kvm/irq.h
+++ b/arch/x86/kvm/irq.h
@@ -60,7 +60,7 @@ struct kvm_kpic_state {
};
struct kvm_pic {
- spinlock_t lock;
+ raw_spinlock_t lock;
bool wakeup_needed;
unsigned pending_acks;
struct kvm *kvm;
next prev parent reply other threads:[~2009-04-07 23:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-07 23:58 [patch 0/3] Patches for KVM & RT Jan Blunck
2009-04-07 23:58 ` [patch 1/3] Make rt_down_read_trylock() behave like down_read_trylock() Jan Blunck
2009-04-09 13:47 ` Thomas Gleixner
2009-04-07 23:58 ` Jan Blunck [this message]
2009-04-09 9:21 ` [patch 2/3] kvm: convert spin-locks to raw_spinlock_t Marcelo Tosatti
2009-04-09 13:48 ` Thomas Gleixner
2009-04-07 23:58 ` [patch 3/3] kvm: wake up waitqueue before calling get_cpu() Jan Blunck
2009-04-09 9:24 ` Marcelo Tosatti
2009-04-09 13:48 ` Thomas Gleixner
2009-04-09 21:44 ` [patch 0/3] Patches for KVM & RT Carsten Emde
2009-04-10 7:23 ` Thomas Gleixner
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=20090407235902.400480759@suse.de \
--to=jblunck@suse.de \
--cc=kvm@vger.kernel.org \
--cc=linux-rt-users@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox