All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
	Alex Williamson <alex.williamson@redhat.com>,
	qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH RFC] vga: flag vga ram for notifiers
Date: Thu, 31 Mar 2011 19:44:35 -0500	[thread overview]
Message-ID: <4D951FF3.1010306@codemonkey.ws> (raw)
In-Reply-To: <20110331234240.GA28793@redhat.com>

On 03/31/2011 06:42 PM, Michael S. Tsirkin wrote:
> On Thu, Mar 31, 2011 at 04:49:46PM -0500, Anthony Liguori wrote:
>> On 03/31/2011 04:38 PM, Michael S. Tsirkin wrote:
>>>> That seems like a clearer API, yes. I think it makes it much more
>>>> obvious what it's trying to achieve.
>>>>
>>>> -- PMM
>>> Maybe register_dma_area - its' not 100% virtio specific.
>> It's never been clear to me whether that's true or not.  I've heard
>> mixed things about whether devices DMA to other devices.  I've never
>> been able to find something in a specification stating
>> authoritatively one way or another.
>>
>> Regards,
>>
>> Anthony Liguori
>>
> AFAIK the capability of cross-talk between PCI devices
> exists in PCI and is optional in PCI Express.
>
> PCI spec says:
> 	Full multi-master capability allowing any PCI master peer-to-peer
> 	access to any PCI master/target.
>
> The Express spec says:
> 	"The capability to route peer-to-peer transactions between hierarchy
> 	domains through a Root Complex is optional and implementation dependent.
> 	For example, an implementation may incorporate a real or virtual Switch
> 	internally within the Root Complex to enable full peer-to- peer support
> 	in a software transparent way."

What's not clear to me though, is whether peer-to-peer transactions are 
done via a special PCI mechanism or whether it's done by doing a I/O 
access to the address that the device happens to be mapped to.

Regards,

Anthony Liguori

> However I don't think guests use this with devices we emulate in any way.
>
> Haven't looked at ISA.
>

  reply	other threads:[~2011-04-01  0:44 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-31 17:43 [Qemu-devel] [PATCH RFC] vga: flag vga ram for notifiers Michael S. Tsirkin
2011-03-31 18:33 ` Anthony Liguori
2011-03-31 18:49   ` Michael S. Tsirkin
2011-03-31 19:01     ` Anthony Liguori
2011-03-31 19:07       ` Michael S. Tsirkin
2011-03-31 19:26         ` Anthony Liguori
2011-03-31 20:03           ` Michael S. Tsirkin
2011-03-31 20:21             ` Anthony Liguori
2011-03-31 19:17       ` Alex Williamson
2011-03-31 19:18       ` Peter Maydell
2011-03-31 19:29         ` Anthony Liguori
2011-03-31 20:12           ` Peter Maydell
2011-03-31 20:23             ` Anthony Liguori
2011-03-31 21:32               ` Peter Maydell
2011-03-31 21:38                 ` Michael S. Tsirkin
2011-03-31 21:49                   ` Anthony Liguori
2011-03-31 23:42                     ` Michael S. Tsirkin
2011-04-01  0:44                       ` Anthony Liguori [this message]
2011-04-01  1:07                         ` Michael S. Tsirkin
2011-04-01  7:12                   ` Peter Maydell
2011-04-01 11:21                     ` Michael S. Tsirkin
2011-03-31 21:26           ` Michael S. Tsirkin
2011-03-31 21:32             ` Anthony Liguori
2011-03-31 21:37               ` Michael S. Tsirkin
2011-03-31 21:48                 ` Anthony Liguori

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=4D951FF3.1010306@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --cc=alex.williamson@redhat.com \
    --cc=mst@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.