From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([140.186.70.92]:37650)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <avi@redhat.com>) id 1R3vt4-0002L2-13
	for qemu-devel@nongnu.org; Wed, 14 Sep 2011 16:16:50 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <avi@redhat.com>) id 1R3vt3-0004rw-5T
	for qemu-devel@nongnu.org; Wed, 14 Sep 2011 16:16:49 -0400
Received: from mx1.redhat.com ([209.132.183.28]:24383)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <avi@redhat.com>) id 1R3vt2-0004rB-SC
	for qemu-devel@nongnu.org; Wed, 14 Sep 2011 16:16:49 -0400
Message-ID: <4E710BAB.6060705@redhat.com>
Date: Wed, 14 Sep 2011 23:16:43 +0300
From: Avi Kivity <avi@redhat.com>
MIME-Version: 1.0
References: <cover.1314033132.git.jan.kiszka@siemens.com>
	<3d9d904a1e4939a147f8954c9e0d4cdaf3d44c31.1314033132.git.jan.kiszka@siemens.com>
	<4E6E2329.9050109@suse.de> <4E6E2631.4060300@siemens.com>
	<4E6E28FD.7070907@web.de> <4E6E2A06.8010900@siemens.com>
	<4E6E2BDC.3060702@siemens.com>
	<DD4F44FB-6EC2-44FD-8F29-5C83107D7C37@suse.de>
	<4E6F10DD.6060606@siemens.com>
	<6BA6355D-D77A-40F4-A8C4-61901A926E71@suse.de>
	<4E6F1BAF.2000105@siemens.com>
	<2A74238E-5C89-444B-9DB9-4B380D182AC3@suse.de>
	<4E6F3FB8.6060705@siemens.com>
	<CAAu8pHty2nzvikbMjgEu07UheuQLD3s1B2kGSvsEX-=wO38ZtA@mail.gmail.com>
	<4E7053A3.8090508@redhat.com>
	<B073C410-AB29-4037-ABAD-91880E88A2C2@suse.de>
	<4E706303.9040502@redhat.com> <4E7063D9.3040803@siemens.com>
	<4E70645D.8050100@redhat.com> <4E7064BA.1050700@siemens.com>
	<58B7465A-925F-4732-A557-AB57BEFCD64B@suse.de>
	<4E706763.8020706@redhat.com>
	<CAAu8pHv-jc7jyM6vnpfscZ-vViwh9ieT-Y8FN72SXBEDisj2bg@mail.gmail.com>
	<14B02BB3-FFB5-4B67-B0AC-6E6A9806AE0E@suse.de>
In-Reply-To: <14B02BB3-FFB5-4B67-B0AC-6E6A9806AE0E@suse.de>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [Qemu-devel] [PATCH v3 5/6] vga: Use linear mapping + dirty
 logging in chain 4 memory access mode
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Alexander Graf <agraf@suse.de>
Cc: Anthony Liguori <aliguori@us.ibm.com>, Jan Kiszka <jan.kiszka@siemens.com>, qemu-devel <qemu-devel@nongnu.org>, Blue Swirl <blauwirbel@gmail.com>, =?ISO-8859-1?Q?Andreas_F=E4rber?= <andreas.faerber@web.de>, Gerd Hoffmann <kraxel@redhat.com>

On 09/14/2011 11:14 PM, Alexander Graf wrote:
> >>  (assuming I understood the problem correctly - not sure)
> >
> >  I think you did.
>
> Well I don't completely, so would anybody who feels reasonably savvy in messing with the new memory api like to step up and implement this? :)
>
>

Can you explain what the memory map looks like from the hardware point 
of view?

-- 
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.