From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([140.186.70.92]:34891)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <avi@redhat.com>) id 1R5zBm-0005yv-Ln
	for qemu-devel@nongnu.org; Tue, 20 Sep 2011 08:12:39 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <avi@redhat.com>) id 1R5zBg-0004QH-Vk
	for qemu-devel@nongnu.org; Tue, 20 Sep 2011 08:12:38 -0400
Received: from mx1.redhat.com ([209.132.183.28]:24785)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <avi@redhat.com>) id 1R5zBg-0004Q9-MA
	for qemu-devel@nongnu.org; Tue, 20 Sep 2011 08:12:32 -0400
Message-ID: <4E788329.4060300@redhat.com>
Date: Tue, 20 Sep 2011 15:12:25 +0300
From: Avi Kivity <avi@redhat.com>
MIME-Version: 1.0
References: <20110904181313.GA14020@redhat.com>
	<4E7007D6.8030102@cn.fujitsu.com> <4E784A33.7040302@cn.fujitsu.com>
	<20110920115504.GA18393@redhat.com>
In-Reply-To: <20110920115504.GA18393@redhat.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [Qemu-devel] [PATCH] pci: implement bridge filtering
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: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Kevin Wolf <kwolf@redhat.com>, Isaku Yamahata <yamahata@valinux.co.jp>, qemu-devel@nongnu.org

On 09/20/2011 02:55 PM, Michael S. Tsirkin wrote:
> >
> >  Hi Michael S. Tsirkin:
> >  I test pci bridge filtering on real hardware, and I find that I can mmap
> >  the resource after I change the memory base and memory limit(The BAR should
> >  be not visible on OS after changing the memory region).
> >
> >  So I try to write and read to the BAR. Here is my test result:
> >  1. Before changing the pci bridge's memory region, I can read and write to the memory, and
> >     I can get the same value that I write.
> >
> >  2. After changing the pci bridge's memory region, I can still read and write to the memory,
> >     but it is very slow, and I can not get the same value that I write(The value is always 0).
> >
> >  Does this result means that pci bridge filtering works fine?
> >
> >  Thanks
> >  Wen Congyang
>
> Sounds more or less right except I expect to get ffffffff
> and not 0. Avi, any idea?
>

No, what does the default handler do?

-- 
error compiling committee.c: too many arguments to function