qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Peter Maydell <peter.maydell@linaro.org>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Anthony Liguori <aliguori@us.ibm.com>,
	David Gibson <david@gibson.dropbear.id.au>,
	qemu-devel@nongnu.org, patches@linaro.org
Subject: Re: [Qemu-devel] [PATCH 0/2] Drop support for qdev taddr properties
Date: Tue, 2 Apr 2013 21:33:48 +0100	[thread overview]
Message-ID: <CAFEAcA9aoDp03r8yx-3y_obi0xCpFpxYm1URNxMO95uSi_pkCw@mail.gmail.com> (raw)
In-Reply-To: <515B2CE6.3040703@redhat.com>

On 2 April 2013 20:09, Paolo Bonzini <pbonzini@redhat.com> wrote:
> Il 02/04/2013 19:07, Peter Maydell ha scritto:
>> It's not a problem with sysbus, it's a problem with people
>> being lazy about implementing things that do DMA. For instance
>> PCI doesn't take a MemoryRegion* for DMA, it just assumes it
>> can DMA into the system address space.
>
> PCI does provide its own DMAContext*, which includes an AddressSpace.
> This address space ("view of the world") is different for each device.

Yes, but (unless you're using the legacy stuff spapr uses)
it generates it via get_system_memory(), which is always
wrong (though often close enough that Linux will work right).

>> (it does let you pass
>> a DMAContext, but maybe that goes away with the patches you
>> mention above; it's only used for spapr.)
>
> It is extended so that it is also used for spapr with those patches.

I'm confused. Do you mean that it's changed so that spapr passes
a MemoryRegion* rather than a DMAContext*, or so that everything
uses a DMAContext* ? (The comments in pci.c suggest that the former
is the intended approach.)

-- PMM

  reply	other threads:[~2013-04-02 20:34 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-02 16:10 [Qemu-devel] [PATCH 0/2] Drop support for qdev taddr properties Peter Maydell
2013-04-02 16:10 ` [Qemu-devel] [PATCH 1/2] hw/sm501: Use correct setter for sysbus-ohci dma-address property Peter Maydell
2013-04-02 16:10 ` [Qemu-devel] [PATCH 2/2] qdev: Drop taddr properties Peter Maydell
2013-04-02 16:42 ` [Qemu-devel] [PATCH 0/2] Drop support for qdev " Paolo Bonzini
2013-04-02 17:07   ` Peter Maydell
2013-04-02 19:09     ` Paolo Bonzini
2013-04-02 20:33       ` Peter Maydell [this message]
2013-04-02 20:39         ` Paolo Bonzini
2013-04-02 20:43           ` Peter Maydell

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=CAFEAcA9aoDp03r8yx-3y_obi0xCpFpxYm1URNxMO95uSi_pkCw@mail.gmail.com \
    --to=peter.maydell@linaro.org \
    --cc=aliguori@us.ibm.com \
    --cc=david@gibson.dropbear.id.au \
    --cc=patches@linaro.org \
    --cc=pbonzini@redhat.com \
    --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 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).