From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [PATCH] slow_map: minor improvements to ROM BAR handling Date: Tue, 22 Dec 2009 17:39:22 +0200 Message-ID: <4B30E82A.5030702@redhat.com> References: <20091222111044.GA16000@redhat.com> <4B30B603.8080707@suse.de> <20091222124311.GD16165@redhat.com> <4B30CAF2.4040409@suse.de> <20091222151911.GC18541@redhat.com> <4B30E470.2030001@redhat.com> <4B30E4BB.8000507@suse.de> <20091222152806.GA18676@redhat.com> <4B30E783.7080903@suse.de> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: "Michael S. Tsirkin" , kvm@vger.kernel.org To: Alexander Graf Return-path: Received: from mx1.redhat.com ([209.132.183.28]:62187 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750948AbZLVPj1 (ORCPT ); Tue, 22 Dec 2009 10:39:27 -0500 In-Reply-To: <4B30E783.7080903@suse.de> Sender: kvm-owner@vger.kernel.org List-ID: On 12/22/2009 05:36 PM, Alexander Graf wrote: > >> Is there a way to trap this and fprintf something? >> > I don't think so. KVM will just trap on execution outside of RAM and > either fail badly or throw something bad into the guest. MMIO access > works by analyzing the instruction that accesses the MMIO address. That > just doesn't work when we don't have an instruction to analyze. > We could certainly extend emulate.c to fetch instruction bytes from userspace. It uses ->read_std() now, so we'd need to switch to ->read_emulated() and add appropriate buffering. -- error compiling committee.c: too many arguments to function