From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Michael S. Tsirkin" Subject: Re: qemu/hw/device-assignment: questions about msix_table_page Date: Tue, 5 May 2009 12:51:36 +0300 Message-ID: <20090505095136.GA12797@redhat.com> References: <20090427104117.GB29082@redhat.com> <200904272203.59909.sheng@linux.intel.com> <20090427141504.GC2504@redhat.com> <200904272230.18253.sheng@linux.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Avi Kivity , Marcelo Tosatti , kvm@vger.kernel.org To: Sheng Yang Return-path: Received: from mx2.redhat.com ([66.187.237.31]:53692 "EHLO mx2.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752007AbZEEJwf (ORCPT ); Tue, 5 May 2009 05:52:35 -0400 Content-Disposition: inline In-Reply-To: <200904272230.18253.sheng@linux.intel.com> Sender: kvm-owner@vger.kernel.org List-ID: On Mon, Apr 27, 2009 at 10:30:17PM +0800, Sheng Yang wrote: > > > > > If guest can write to the real device MSI-X table directly, it would > > > > > cause chaos on interrupt delivery, for what guest see is totally > > > > > different with what's host see... > > > > > > > > Obviously. > > > > > > > > Thanks, > What's the reason that this page is unmapped from the qemu memory space? Specifically what do these lines do: int offset = r_dev->msix_table_addr - real_region->base_addr; ret = munmap(region->u.r_virtbase + offset, TARGET_PAGE_SIZE); -- MST