From: Zachary Amsden <zamsden@redhat.com>
To: kvm <kvm@vger.kernel.org>, Jan Kiszka <jan.kiszka@web.de>,
Avi Kivity <avi@redhat.com>, Gleb Natapov <gleb@redhat.com>
Subject: Re: [PATCH 0/4] some kvm-kmod issues
Date: Tue, 25 May 2010 18:52:51 -1000 [thread overview]
Message-ID: <4BFCA923.602@redhat.com> (raw)
In-Reply-To: <4BFC956D.6070808@redhat.com>
On 05/25/2010 05:28 PM, Zachary Amsden wrote:
> I found some issues with kvm-kmod from recently pulled tree on F13
> (2.6.33) kernel. I am not 100% sure the version numbers are right in
> all of these fixes, but at least it compiles and seems to run VMs again.
>
> The FPU change and the iommu change are, well, rather scary. They
> could use some eyes and suggestions.
>
> Zach
Well, this apparently doesn't work. The module builds, load, and runs
non-paging mode fine, but things appear to go haywire just around when
paging gets activated. Any recent changes in the module (large page,
TLB contract) that might be relying on addition kernel support?
Or just too long since I pulled mainline. I'll try a bsect and see
where I get.
Zach
next prev parent reply other threads:[~2010-05-26 4:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-26 3:28 [PATCH 0/4] some kvm-kmod issues Zachary Amsden
2010-05-26 4:52 ` Zachary Amsden [this message]
2010-05-26 7:10 ` Jan Kiszka
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=4BFCA923.602@redhat.com \
--to=zamsden@redhat.com \
--cc=avi@redhat.com \
--cc=gleb@redhat.com \
--cc=jan.kiszka@web.de \
--cc=kvm@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).