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: Anthony Liguori <aliguori@us.ibm.com>,
	patches@linaro.org, qemu-devel@nongnu.org,
	David Gibson <david@gibson.dropbear.id.au>
Subject: Re: [Qemu-devel] [PATCH 0/2] Drop support for qdev taddr properties
Date: Tue, 02 Apr 2013 18:42:33 +0200	[thread overview]
Message-ID: <515B0A79.50906@redhat.com> (raw)
In-Reply-To: <1364919044-18413-1-git-send-email-peter.maydell@linaro.org>

Il 02/04/2013 18:10, Peter Maydell ha scritto:
> There is currently only one user of the qdev taddr (target addr,
> now hwaddr) property code, and that user is wrong anyway, since the
> property it's trying to set isn't actually a taddr property.
> Fix the erroneous use in sm501 and drop all the taddr property code.
> 
> The justification for dropping the support is that a device should
> generally not be exposing properties whose width (conceptually)
> depends on the target CPU type. (This is the same rationale for
> not supporting hwaddr fields in migration state.) Instead the
> device should expose either a 32 bit or 64 bit property, depending
> on what the actual hardware does.
> 
> Aside: I may try to get rid of the DMAADDR property too at some
> point, because what the sysbus-ohci device should actually be doing
> is taking a MemoryRegion* [or maybe a DMAContext*]

Avi had patches to unify DMAContext and MemoryRegion.  I should revive
them perhaps.

> representing what
> it should be DMAing into, rather than the current "DMA into the
> system address space at addr + some constant offset" hack. One
> thing at a time, though.

That's a general problem with sysbus.  I guess if you need another
address space you should define your own bus, like PCI does.

Paolo

> Peter Maydell (2):
>   hw/sm501: Use correct setter for sysbus-ohci dma-address property
>   qdev: Drop taddr properties
> 
>  hw/Makefile.objs        |  1 -
>  hw/fdc.c                |  1 -
>  hw/milkymist-hw.h       |  1 -
>  hw/milkymist-minimac2.c |  1 -
>  hw/qdev-addr.c          | 78 -------------------------------------------------
>  hw/qdev-addr.h          | 10 -------
>  hw/sm501.c              |  3 +-
>  hw/sparc/sun4m.c        |  1 -
>  hw/tcx.c                |  1 -
>  hw/xilinx_axidma.c      |  1 -
>  10 files changed, 1 insertion(+), 97 deletions(-)
>  delete mode 100644 hw/qdev-addr.c
>  delete mode 100644 hw/qdev-addr.h
> 

  parent reply	other threads:[~2013-04-02 16:42 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 ` Paolo Bonzini [this message]
2013-04-02 17:07   ` [Qemu-devel] [PATCH 0/2] Drop support for qdev " Peter Maydell
2013-04-02 19:09     ` Paolo Bonzini
2013-04-02 20:33       ` Peter Maydell
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=515B0A79.50906@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=aliguori@us.ibm.com \
    --cc=david@gibson.dropbear.id.au \
    --cc=patches@linaro.org \
    --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).