From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [RFC PATCH 0/3] Real mode interrupt injection Date: Sun, 15 Aug 2010 15:23:27 +0300 Message-ID: <4C67DC3F.9080509@redhat.com> References: <1281295456-11114-1-git-send-email-m.gamal005@gmail.com> <4C60BF08.2050704@redhat.com> <4C61DA6B.60904@redhat.com> <4C6283A5.8040602@redhat.com> <4C62876F.1080709@redhat.com> <4C6292C7.4000106@redhat.com> <4C6344FB.1030005@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: mtosatti@redhat.com, kvm@vger.kernel.org To: Mohammed Gamal Return-path: Received: from mx1.redhat.com ([209.132.183.28]:31773 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757658Ab0HOPfG (ORCPT ); Sun, 15 Aug 2010 11:35:06 -0400 In-Reply-To: Sender: kvm-owner@vger.kernel.org List-ID: On 08/12/2010 04:07 AM, Mohammed Gamal wrote: >>> >>> I was playing around with the non-atomic-injection branch. I decided >>> to use e_i_g_s=1, and it's worth noting that I never experienced these >>> faults with the switch enabled. > Hate to spoil it. I did experience the faults again with e_i_g_s=1, > although much less frequently. > > What is rather really strange, is that I could get a Linux guest to > boot up completely both with e_i_g_s=1 and without it with the real > mode interrupt patch enabled. It looks to me like the problem mainly > happens when the BIOS tranfers control to the boot loader. Other > guests usually fail. > > Would you like me to attach a trace? It will be much too big, upload it somewhere or send it to be privately. But, use the code with the interrupt injection setup fixed (see my comment to patch 2). -- error compiling committee.c: too many arguments to function