From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:55359) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UZEvb-0006Wl-3d for qemu-devel@nongnu.org; Mon, 06 May 2013 02:29:42 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UZEvZ-0003dJ-SV for qemu-devel@nongnu.org; Mon, 06 May 2013 02:29:39 -0400 Received: from thoth.sbs.de ([192.35.17.2]:27436) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UZEvZ-0003cr-G3 for qemu-devel@nongnu.org; Mon, 06 May 2013 02:29:37 -0400 Message-ID: <51874DCD.5020309@siemens.com> Date: Mon, 06 May 2013 08:29:33 +0200 From: Jan Kiszka MIME-Version: 1.0 References: <20130505205149.GA2032@amt.cnet> In-Reply-To: <20130505205149.GA2032@amt.cnet> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [uq/master PATCH] kvmvapic: add ioport read accessor List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Marcelo Tosatti Cc: qemu-devel , kvm-devel On 2013-05-05 22:51, Marcelo Tosatti wrote: > > Necessary since memory region accessor assumes read and write > methods are registered. Otherwise reading I/O port 0x7e segfaults. > > https://bugzilla.redhat.com/show_bug.cgi?id=954306 > > Signed-off-by: Marcelo Tosatti > > diff --git a/hw/i386/kvmvapic.c b/hw/i386/kvmvapic.c > index 5b558aa..655483b 100644 > --- a/hw/i386/kvmvapic.c > +++ b/hw/i386/kvmvapic.c > @@ -687,8 +687,14 @@ static void vapic_write(void *opaque, hwaddr addr, uint64_t data, > } > } > > +static uint64_t vapic_read(void *opaque, hwaddr addr, unsigned size) > +{ > + return 0xffffffff; > +} > + > static const MemoryRegionOps vapic_ops = { > .write = vapic_write, > + .read = vapic_read, > .endianness = DEVICE_NATIVE_ENDIAN, > }; > > Right. I'm just wondering why the guest reads from that port. Reviewed-by: Jan Kiszka -- Siemens AG, Corporate Technology, CT RTC ITP SDP-DE Corporate Competence Center Embedded Linux