From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [PATCH 1/9] Don't separate registrations with IO_MEM_ROM set Date: Fri, 19 Sep 2008 16:12:45 -0700 Message-ID: <48D431ED.40901@redhat.com> References: <1221232250-9653-1-git-send-email-glommer@redhat.com> <1221232250-9653-2-git-send-email-glommer@redhat.com> <48CA8F1C.1040104@siemens.com> <20080912160432.GA3734@poweredge.glommer> <48CA983D.6060101@siemens.com> <20080912184737.GB3734@poweredge.glommer> <48CB5CFE.2030907@web.de> <20080915124449.GA5967@poweredge.glommer> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Jan Kiszka , kvm@vger.kernel.org, jes@sgi.com, aliguori@us.ibm.com To: Glauber Costa Return-path: Received: from il.qumranet.com ([212.179.150.194]:33201 "EHLO il.qumranet.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751333AbYISXMm (ORCPT ); Fri, 19 Sep 2008 19:12:42 -0400 In-Reply-To: <20080915124449.GA5967@poweredge.glommer> Sender: kvm-owner@vger.kernel.org List-ID: Glauber Costa wrote: >> >> I'm currently not aware of a practical use case where this bites, but if >> the guest maps some memory from A to B, it may expect to find the >> content of A under B as well. That is not the case so far as B remains B >> from KVM's POV. At the same time, all QEMU memory access functions see B >> as A (that caused trouble for debugging and memory sniffing monitor >> services). >> > It looks like KVM aliasing support, that (up to now), seemed completely orthogonal. > I'm looking at ways to integrate aliasing now, so if you can provide me with some use > cases of what you described above, (that seem to have happened in your debugging patches), > it would surely help. > > Aliasing/remapping can now be implemented using memory slots. Simply map the same hva to different gpas. -- I have a truly marvellous patch that fixes the bug which this signature is too narrow to contain.