All of lore.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.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: Tue, 20 Sep 2011 15:12:25 +0300	[thread overview]
Message-ID: <4E788329.4060300@redhat.com> (raw)
In-Reply-To: <20110920115504.GA18393@redhat.com>

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

      reply	other threads:[~2011-09-20 12:12 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
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 [this message]

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=4E788329.4060300@redhat.com \
    --to=avi@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.