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: Sat, 22 Sep 2007 08:36:48 +0200	[thread overview]
Message-ID: <46F4B800.20408@qumranet.com> (raw)
In-Reply-To: <46F3E1E7.7010602-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>

Gerd Hoffmann wrote:
> Avi Kivity wrote:
>   
>> Only one fix, but an important one.  It fixes booting of newer Linux
>> versions, which experienced disk and keyboard problems without
>> -no-kvm-irqchip.
>>
>> As usual, if you have an issue please try with -no-kvm-irqchip and report.
>>     
>
> Updated from -41.  Now my libkvm-using-tool's
> kvm_callbacks->try_push_interrupts() callback isn't called any more.
> Hmm.  Guess due to the lapic/irqchip changes.  Are there any additional
> initializations I have to do now?
>
> As there isn't any real pic-like hardware emulated maybe using
> try_to_push_interrupts is a bad idea anyway and I should better move the
> code (checks state and calls kvm_inject_irq() if needed) to the
> pre_kvm_run() callback?
>
> hints anyone?
>   

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)

-- 
Any sufficiently difficult bug is indistinguishable from a feature.


-------------------------------------------------------------------------
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-22  6:36 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 [this message]
     [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
     [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=46F4B800.20408@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.