From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: Gregory Haskins <ghaskins-Et1tbQHTxzrQT0dZR+AlfA@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: KVM and RT
Date: Wed, 01 Aug 2007 09:56:32 +0300 [thread overview]
Message-ID: <46B02EA0.7080100@qumranet.com> (raw)
In-Reply-To: <1185910192.9513.57.camel-5CR4LY5GPkvLDviKLk5550HKjMygAv58XqFh9Ls21Oc@public.gmane.org>
Gregory Haskins wrote:
> Hi Team,
> I don't know if anyone here also subscribes to linux-rt-users, but it
> seems as though Ingo et. al. rejected my modifications which ran the
> smp_call() in a thread (VFCIPI).
It's not surprising. 650 lines including a custom memory allocator is
excessive.
> So FYI: KVM is still broken on RT and
> needs to be addressed.
>
> In a nutshell, kvm_lock cannot be used as it us today. It either needs
> to be a raw_spinlock_t, or the locking needs to be done differently.
> The code currently blows up when you shut down a VM running on top of
> PREEMPT_RT. Just thought you might want to know.
>
What about hoisting the lock outside the IPI as I suggested earlier?
--
Do not meddle in the internals of kernels, for they are subtle and quick to panic.
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
next prev parent reply other threads:[~2007-08-01 6:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-31 19:29 KVM and RT Gregory Haskins
[not found] ` <1185910192.9513.57.camel-5CR4LY5GPkvLDviKLk5550HKjMygAv58XqFh9Ls21Oc@public.gmane.org>
2007-08-01 6:56 ` Avi Kivity [this message]
[not found] ` <46B02EA0.7080100-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-08-01 11:51 ` Gregory Haskins
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=46B02EA0.7080100@qumranet.com \
--to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
--cc=ghaskins-Et1tbQHTxzrQT0dZR+AlfA@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.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.