All of lore.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: Gerd Hoffmann <kraxel-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: kvm-devel <kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: [ANNOUNCE] kvm-43 release
Date: Mon, 24 Sep 2007 11:51:23 +0200	[thread overview]
Message-ID: <46F7889B.70000@qumranet.com> (raw)
In-Reply-To: <46F786DF.7020600-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>

Gerd Hoffmann wrote:
> Avi Kivity wrote:
>   
>> You can call kvm_disable_irqchip_creation() to kill in-kernel pic and
>> friends.
>>
>> (the logic is inverted -- the function should be
>> kvm_enable_irqchip_creation() so that this problem would not occur)
>>     
>
> Ok, will try, next question first though as I'm running in trouble much
> earlier in -44:  I get suspious page faults.
>
> I *think* it happens because I'm changing guest page tables from outside
> (i.e. host application), and the new intel pgtable optimization bits
> don't expect that (yes, it is a vt box).
>   

Well, the older implementation doesn't expect that either.  You can 
disable the optimization with bypass_guest_pf=0, though.

> A quick scan of kvmctl.h doesn't show anything which looks like I could
> call to tell kvm the guest page tables have been modified.  Hints how to
> handle this?
>
>   

There's a kvm_mmu_zap_all() function, but it isn't exposed.  It's very 
coarse grained, but can be used for experiments.

You could write a new ioctl that tells kvm that some pages were modified 
by the host; that's useful for guests which page out page tables (and 
so, during page in, disk dma could overwrite a page table).


-- 
error compiling committee.c: too many arguments to function


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

  parent reply	other threads:[~2007-09-24  9:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-21  5:38 [ANNOUNCE] kvm-43 release Avi Kivity
     [not found] ` <46F358D2.9000009-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-09-21 15:23   ` Gerd Hoffmann
     [not found]     ` <46F3E1E7.7010602-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2007-09-22  6:36       ` Avi Kivity
     [not found]         ` <46F4B800.20408-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-09-24  9:43           ` Gerd Hoffmann
     [not found]             ` <46F786DF.7020600-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2007-09-24  9:51               ` Avi Kivity [this message]
     [not found]                 ` <46F7889B.70000-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-09-24 10:11                   ` Gerd Hoffmann

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=46F7889B.70000@qumranet.com \
    --to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
    --cc=kraxel-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
    --cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.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 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.