qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Wen Congyang <wency@cn.fujitsu.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
	Isaku Yamahata <yamahata@valinux.co.jp>,
	qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] pci: implement bridge filtering
Date: Wed, 14 Sep 2011 09:48:06 +0800	[thread overview]
Message-ID: <4E7007D6.8030102@cn.fujitsu.com> (raw)
In-Reply-To: <20110904181313.GA14020@redhat.com>

At 09/05/2011 02:13 AM, Michael S. Tsirkin Write:
> Support bridge filtering on top of the memory
> API as suggested by Avi Kivity:
> 
> Create a memory region for the bridge's address space.  This region is
> not directly added to system_memory or its descendants.  Devices under
> the bridge see this region as its pci_address_space().  The region is
> as large as the entire address space - it does not take into account
> any windows.
> 
> For each of the three windows (pref, non-pref, vga), create an alias
> with the appropriate start and size.  Map the alias into the bridge's
> parent's pci_address_space(), as subregions.
> 
> Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
> ---
> 
> The below seems to work fine for me so I applied this.
> Still need to test bridge filtering, any help with this
> appreciated.
> 


I test bridge filtering, and the BAR still can be visible on guest even if
I change the memory region.

Thanks
Wen Congyang

  reply	other threads:[~2011-09-14  1:49 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-04 18:13 [Qemu-devel] [PATCH] pci: implement bridge filtering Michael S. Tsirkin
2011-09-14  1:48 ` Wen Congyang [this message]
2011-09-20  8:09   ` Wen Congyang
2011-09-20 11:44     ` Avi Kivity
2011-09-20 12:22       ` Michael S. Tsirkin
2011-09-20 12:26         ` Avi Kivity
2011-09-20 11:55     ` Michael S. Tsirkin
2011-09-20 12:12       ` Avi Kivity

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4E7007D6.8030102@cn.fujitsu.com \
    --to=wency@cn.fujitsu.com \
    --cc=kwolf@redhat.com \
    --cc=mst@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=yamahata@valinux.co.jp \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).