From: Jesse <jdutton@neuraliq.com>
To: Marcelo Tosatti <mtosatti@redhat.com>
Cc: kvm@vger.kernel.org
Subject: Re: [PATCH]: pointer to vmcs getting lost
Date: Sat, 02 Aug 2008 17:11:54 -0700 [thread overview]
Message-ID: <4894F7CA.1040901@neuraliq.com> (raw)
In-Reply-To: <20080802163144.GB17170@dmt.cnet>
Marcelo Tosatti wrote:
> Do you have preempt notifiers enabled in your host kernel?
>
No. And it looks like this is the real issue then. (Thank you for
reading between the lines and figuring out what was really wrong).
I compile the module apart from the kernel, so kvm support was not
enabled when compiling the kernel. In 2.6.24, the PREEMPT_NOTIFIER
option is not user selectable in make config, but is selected for you
when kvm support is selected. IMO, this makes building modules apart
from kernel source unadvised; however, there seems to be no alternative
with the pace of kvm development relative to the kernel release schedule.
next prev parent reply other threads:[~2008-08-03 0:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-01 22:18 [PATCH]: pointer to vmcs getting lost Jesse
2008-08-01 23:24 ` Marcelo Tosatti
2008-08-01 23:36 ` Jesse
2008-08-02 16:31 ` Marcelo Tosatti
2008-08-03 0:11 ` Jesse [this message]
2008-08-11 11:48 ` Avi Kivity
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=4894F7CA.1040901@neuraliq.com \
--to=jdutton@neuraliq.com \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@redhat.com \
/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.