public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@web.de>
To: Zachary Amsden <zamsden@redhat.com>
Cc: kvm@vger.kernel.org, Avi Kivity <avi@redhat.com>
Subject: Re: kvm-kmod broken with user-return-notifiers
Date: Thu, 29 Oct 2009 08:30:14 +0100	[thread overview]
Message-ID: <4AE94486.7040403@web.de> (raw)
In-Reply-To: <4AE8D984.3030906@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 847 bytes --]

Zachary Amsden wrote:
> With current upstream changes, VMX operation now relies on have the
> user-notifiers infrastructure.  This makes kvm-kmod use on older kernels
> untenable.
> 
> I looked a bit at fixing the underlying problem by simulating the
> user-return callback when we context switch, but it is uglier than I
> would like.
> 
> Is anyone currently working on a fix?  This is blocking my development
> work, so if there is no action it looks like I will have to fix it myself.

You are welcome to test kvm-kmod next and also give feedback on the
approach I applied.

Jan

PS: Just like Avi and Marcelo are posting their work-in-progress to the
next branches of kvm.git and qemu-kvm.git, I will do the same with
kvm-kmod. I'm just still struggling with the sometimes terrible update
latency of korg's public git.


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 257 bytes --]

      reply	other threads:[~2009-10-29  7:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-28 23:53 kvm-kmod broken with user-return-notifiers Zachary Amsden
2009-10-29  7:30 ` Jan Kiszka [this message]

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=4AE94486.7040403@web.de \
    --to=jan.kiszka@web.de \
    --cc=avi@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=zamsden@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox