From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: "Back,
Michael (ext)"
<michael.back.ext-kv7WeFo6aLtBDgjK7y7TUQ@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: KVM and Prempt?
Date: Mon, 22 Oct 2007 13:51:36 +0200 [thread overview]
Message-ID: <471C8EC8.8060508@qumranet.com> (raw)
In-Reply-To: <003F437218F04842B2A6976FA19368B1886D5A-EA/R+3GEQKtclD5KMHf1bFOnKfhBOm/VrE5yTffgRl4@public.gmane.org>
Back, Michael (ext) wrote:
>>>
>>>
>> Make sure CONFIG_PREEMPT_NOTIFIER is selected in your .config. You'll
>> have to adjust Kconfig or select the in-tree kvm for that.
>>
>
> Is there a possibility to check, if CONFIG_PREEMPT_NOTIFIER correct selected and compiled in the kernel/modules?
>
The external module code checks CONFIG_PREEMPT_NOTIFIER, and emulates
preempt notifiers if not present in the host kernel. But the preempt
notifier emulation has not been tested with -rt and may be broken there.
--
error compiling committee.c: too many arguments to function
-------------------------------------------------------------------------
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-10-22 11:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-19 13:32 KVM and Prempt? Back, Michael (ext)
[not found] ` <003F437218F04842B2A6976FA19368B1886A2F-EA/R+3GEQKtclD5KMHf1bFOnKfhBOm/VrE5yTffgRl4@public.gmane.org>
2007-10-19 13:57 ` Gregory Haskins
[not found] ` <1192802222.9564.4.camel-5CR4LY5GPkvLDviKLk5550HKjMygAv58XqFh9Ls21Oc@public.gmane.org>
2007-10-19 14:17 ` Back, Michael (ext)
[not found] ` <003F437218F04842B2A6976FA19368B1886A66-EA/R+3GEQKtclD5KMHf1bFOnKfhBOm/VrE5yTffgRl4@public.gmane.org>
2007-10-19 15:27 ` Gregory Haskins
[not found] ` <1192807627.9564.10.camel-5CR4LY5GPkvLDviKLk5550HKjMygAv58XqFh9Ls21Oc@public.gmane.org>
2007-10-22 6:58 ` Back, Michael (ext)
[not found] ` <003F437218F04842B2A6976FA19368B1886B92-EA/R+3GEQKtclD5KMHf1bFOnKfhBOm/VrE5yTffgRl4@public.gmane.org>
2007-10-22 7:39 ` Avi Kivity
[not found] ` <471C53B7.1040208-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-10-22 11:37 ` Back, Michael (ext)
[not found] ` <003F437218F04842B2A6976FA19368B1886D5A-EA/R+3GEQKtclD5KMHf1bFOnKfhBOm/VrE5yTffgRl4@public.gmane.org>
2007-10-22 11:51 ` Avi Kivity [this message]
[not found] ` <471C8EC8.8060508-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-10-22 14:05 ` Back, Michael (ext)
2007-10-24 14:02 ` Back, Michael (ext)
-- strict thread matches above, loose matches on Subject: below --
2007-10-19 13:16 Back, Michael (ext)
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=471C8EC8.8060508@qumranet.com \
--to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=michael.back.ext-kv7WeFo6aLtBDgjK7y7TUQ@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox