All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@web.de>
To: Zachary Amsden <zamsden@redhat.com>
Cc: kvm <kvm@vger.kernel.org>, Avi Kivity <avi@redhat.com>,
	Gleb Natapov <gleb@redhat.com>
Subject: Re: [PATCH 0/4] some kvm-kmod issues
Date: Wed, 26 May 2010 09:10:19 +0200	[thread overview]
Message-ID: <4BFCC95B.6060301@web.de> (raw)
In-Reply-To: <4BFCA923.602@redhat.com>

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

Zachary Amsden wrote:
> 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

Thanks a lot for the patches! Just yesterday, I finally started hacking
on this as well. I have some FPU wrapper running (see next branch) that
seems to run fine - but is in some parts also more complicated as
required (and has a build problem on very old kernels).

Will comment on individual patches.

Jan


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

      reply	other threads:[~2010-05-26  7:10 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
2010-05-26  7:10   ` 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=4BFCC95B.6060301@web.de \
    --to=jan.kiszka@web.de \
    --cc=avi@redhat.com \
    --cc=gleb@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 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.