From: "Michael S. Tsirkin" <mst@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: QEMU Developers <qemu-devel@nongnu.org>,
Anthony Liguori <anthony@codemonkey.ws>,
Marcel Apfelbaum <marcel.a@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] hw/pci: completed master-abort emulation
Date: Wed, 25 Sep 2013 02:43:40 +0300 [thread overview]
Message-ID: <20130924234340.GA3892@redhat.com> (raw)
In-Reply-To: <CAFEAcA9b14AcX3pJd_Lu-kM0eWGCkHwbinWy-RLfOwurnkBd4w@mail.gmail.com>
On Wed, Sep 25, 2013 at 08:36:09AM +0900, Peter Maydell wrote:
> On 25 September 2013 00:41, Michael S. Tsirkin <mst@redhat.com> wrote:
> > On Tue, Sep 24, 2013 at 08:21:50PM +0900, Peter Maydell wrote:
> > Right. You might be able to use MR hierarchy to find the last bridge to
> > claim transaction. That should to be enough for PCI, for express you
> > then need to find all devices on the path between bus master and the
> > last bridge. For this task, memory subsystem can't be used I think.
>
> Mmm, if you need to do something for every device on the
> path then that's more awkward with MRs.
>
> > Whether the result will be cleaner than open-coding it all, I don't
> > really know.
>
> Yes. I was just suggesting it was worth considering at least to
> the point of being able to make a decision about which design
> is likely to be cleaner. If PCI express needs the dynamic walk
> of the path then it's probably better to handle plain PCI that
> way too for consistency.
>
> -- PMM
It would seem so. The express spec is kind of murky about this
but experiments with real hardware seem to confirm this.
--
MST
prev parent reply other threads:[~2013-09-24 23:41 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-23 11:01 [Qemu-devel] [PATCH] hw/pci: completed master-abort emulation Marcel Apfelbaum
2013-09-23 11:27 ` Michael S. Tsirkin
2013-09-23 12:37 ` Marcel Apfelbaum
2013-09-23 13:45 ` Michael S. Tsirkin
2013-09-23 14:43 ` Marcel Apfelbaum
2013-09-23 15:10 ` Michael S. Tsirkin
2013-09-23 17:49 ` Marcel Apfelbaum
2013-09-23 18:45 ` Michael S. Tsirkin
2013-09-24 8:07 ` Marcel Apfelbaum
2013-09-24 8:29 ` Michael S. Tsirkin
2013-09-24 8:44 ` Marcel Apfelbaum
2013-09-24 8:58 ` Michael S. Tsirkin
2013-09-24 10:44 ` Marcel Apfelbaum
2013-09-24 10:55 ` Peter Maydell
2013-09-24 11:17 ` Marcel Apfelbaum
2013-09-24 11:21 ` Peter Maydell
2013-09-24 11:41 ` Marcel Apfelbaum
2013-09-24 15:41 ` Michael S. Tsirkin
2013-09-24 16:24 ` Michael S. Tsirkin
2013-09-24 23:36 ` Peter Maydell
2013-09-24 23:43 ` Michael S. Tsirkin [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=20130924234340.GA3892@redhat.com \
--to=mst@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=marcel.a@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
/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.