From: Avi Kivity <avi@redhat.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: Thomas Gleixner <tglx@linutronix.de>, KVM <kvm@vger.kernel.org>
Subject: Re: [patch] x86: kvm: Convert i8254/i8259 locks to raw_spinlocks
Date: Thu, 18 Feb 2010 11:20:35 +0200 [thread overview]
Message-ID: <4B7D0663.70807@redhat.com> (raw)
In-Reply-To: <4B7D0466.2030700@siemens.com>
On 02/18/2010 11:12 AM, Jan Kiszka wrote:
> Thomas Gleixner wrote:
>
>> The i8254/i8259 locks need to be real spinlocks on preempt-rt. Convert
>> them to raw_spinlock. No change for !RT kernels.
>>
> Last time I ran KVM over RT, I also had to convert requests_lock (struct
> kvm): make_all_cpus_request assumes that this lock prevents migration.
>
>
True. Will commit something to that effect.
Meanwhile, if anyone has any idea how to kill this lock, I'd love to see it.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2010-02-18 9:20 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-17 14:00 [patch] x86: kvm: Convert i8254/i8259 locks to raw_spinlocks Thomas Gleixner
2010-02-18 9:12 ` Jan Kiszka
2010-02-18 9:20 ` Avi Kivity [this message]
2010-02-18 9:40 ` Jan Kiszka
2010-02-18 9:45 ` Avi Kivity
2010-02-18 9:49 ` Jan Kiszka
2010-02-18 9:53 ` Avi Kivity
2010-02-18 9:50 ` Avi Kivity
2010-02-18 10:05 ` Jan Kiszka
2010-02-18 10:18 ` Avi Kivity
2010-02-19 1:14 ` Marcelo Tosatti
2010-02-18 9:19 ` Avi Kivity
2010-02-23 19:18 ` Jan Kiszka
2010-02-23 22:23 ` Thomas Gleixner
2010-02-24 9:41 ` [PATCH] KVM: x86: Kick VCPU outside PIC lock again Jan Kiszka
2010-02-24 9:48 ` Avi Kivity
2010-02-24 9:54 ` Jan Kiszka
2010-02-24 10:04 ` Avi Kivity
2010-02-24 10:13 ` Jan Kiszka
2010-02-24 10:17 ` Avi Kivity
2010-02-24 10:22 ` Jan Kiszka
2010-02-24 10:27 ` Avi Kivity
2010-02-24 10:31 ` Jan Kiszka
2010-02-24 10:28 ` Jan Kiszka
2010-02-24 10:41 ` Avi Kivity
2010-02-24 11:42 ` Jan Kiszka
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=4B7D0663.70807@redhat.com \
--to=avi@redhat.com \
--cc=jan.kiszka@siemens.com \
--cc=kvm@vger.kernel.org \
--cc=tglx@linutronix.de \
/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.