qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Peter Crosthwaite <peter.crosthwaite@xilinx.com>,
	patches@linaro.org, qemu-devel@nongnu.org,
	Gerd Hoffmann <kraxel@redhat.com>,
	David Gibson <david@gibson.dropbear.id.au>,
	Avi Kivity <avi@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] dma: Define dma_context_memory and use in sysbus-ohci
Date: Tue, 13 Nov 2012 16:04:17 +0100	[thread overview]
Message-ID: <50A26171.9090808@redhat.com> (raw)
In-Reply-To: <CAFEAcA_JL+FCwWYCMFjwYzetcoFb0y-28DcXZxNffB0Z19j8RA@mail.gmail.com>

Il 13/11/2012 12:44, Peter Maydell ha scritto:
>>> >> As soon as Avi's iommu patches go in, in fact, dma->as will just be as.
>>> >> Even if as == NULL were to be outlawed and you'd be forced to write
>>> >> get_address_space_memory(), taking the pain to create dummy DMAContexts
>>> >> now is just not worth it.
>> >
>> > Personally I think it's better not to permit NULL DMAContexts or
>> > AddressSpaces here, because they're kind of a hack (in the same way
>> > that the "system address space" is kind of a hack). In real hardware
>> > you probably aren't really doing dma to that address space but to
>> > some more local bus. dma_context_memory/address_space_memory are
>> > nice and easy to search for, whereas NULL isn't. [And in general
>> > I think NULL is too easy to use; if you have to go looking for the
>> > system dma context you've been prompted to think about whether
>> > that's the right one...]
> Ping! Can we have a ruling on what the right fix for this is so
> we can fix these segfaults before 1.3 release, please?

I think this patch is already in Gerd's queue.

Paolo

  reply	other threads:[~2012-11-13 15:04 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-23 17:26 [Qemu-devel] [PATCH] dma: Define dma_context_memory and use in sysbus-ohci Peter Maydell
2012-10-25 10:33 ` Peter Crosthwaite
2012-10-26  0:48   ` David Gibson
2012-10-26  2:53     ` Peter Crosthwaite
2012-10-26  3:58       ` David Gibson
2012-10-26 13:09         ` Paolo Bonzini
2012-10-26 16:00           ` Peter Maydell
2012-11-13 11:44             ` Peter Maydell
2012-11-13 15:04               ` Paolo Bonzini [this message]
2012-11-13 15:21                 ` Gerd Hoffmann
2012-11-13 15:26                   ` Paolo Bonzini
2012-11-18 16:53               ` 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=50A26171.9090808@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=avi@redhat.com \
    --cc=david@gibson.dropbear.id.au \
    --cc=kraxel@redhat.com \
    --cc=patches@linaro.org \
    --cc=peter.crosthwaite@xilinx.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 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).