From: Jan Kiszka <jan.kiszka@siemens.com>
To: Avi Kivity <avi@redhat.com>
Cc: KVM list <kvm@vger.kernel.org>, Marcelo Tosatti <marcelo@redhat.com>
Subject: Re: Jan Kiszka to maintain kvm-kmod
Date: Tue, 27 Oct 2009 12:20:03 +0100 [thread overview]
Message-ID: <4AE6D763.7050108@siemens.com> (raw)
In-Reply-To: <4AE6CEDD.7070603@redhat.com>
Avi Kivity wrote:
> On 10/26/2009 07:51 PM, Jan Kiszka wrote:
>> That forecast already promises the next rain
>
> That would be me. I think it's easily fixable, either by emulating user
> return notifiers using preempt notifiers (sched_out -> on_user_return),
> or by noping out user return notifiers completely and hooking the kvm
> sched_out callback to call kvm_on_user_return. Of course, we won't see
> the performance gain, but that's expected.
I was playing with such an approach already. But something goes wrong
(GPF in kvm_set_shared_msr) when booting Win7. Will check without
kvm-kmod next.
Jan
--
Siemens AG, Corporate Technology, CT SE 2
Corporate Competence Center Embedded Linux
prev parent reply other threads:[~2009-10-27 11:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-26 9:02 Jan Kiszka to maintain kvm-kmod Avi Kivity
2009-10-26 17:51 ` Jan Kiszka
2009-10-27 10:43 ` Avi Kivity
2009-10-27 11:20 ` 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=4AE6D763.7050108@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=marcelo@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.