From: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>
To: Blue Swirl <blauwirbel@gmail.com>
Cc: Peter Maydell <peter.maydell@linaro.org>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Memory API: handling unassigned physical memory
Date: Tue, 01 May 2012 19:50:43 +0100 [thread overview]
Message-ID: <4FA03083.4030104@ilande.co.uk> (raw)
In-Reply-To: <CAAu8pHuuKenbBAGvcF=N94v2cz9tJ3iPNmgoT7Wy-CV0mYffjg@mail.gmail.com>
On 01/05/12 08:10, Blue Swirl wrote:
>> In your view, would a suitable fix be to change dma_memory_read,
>> dma_memory_write, dma_opaque, it_shift and dma_enabled to be qdev properties
>> and modify esp_init() to return the qdev reference so they can be set by the
>> caller?
>
> There's an ongoing work to introduce IOMMUs by changing how DMA work
> and this could simplify the DMA part. There's no clean way to use
> function pointers in qdev.
In my current working tree, I have actually managed to get this working
with a customised qdev type macro and the standard qdev pointer type -
so it may not be particularly great, but it works.
> For it_shift, a qdev or QOM property should be OK.
>
> The signal dma_enabled should be eventually replaced by a Pin.
And this is a sysbus concept, yes?
ATB,
Mark.
next prev parent reply other threads:[~2012-05-01 18:50 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4F9D797E.500@ilande.co.uk>
[not found] ` <4F9D97F3.8080608@codemonkey.ws>
[not found] ` <4F9E5028.7010306@redhat.com>
[not found] ` <4F9E82C7.10706@ilande.co.uk>
[not found] ` <4F9E9268.70408@redhat.com>
[not found] ` <CAFEAcA_sKtzmHpFcdhkANLCY0=FuW0Hbof0ifp3uHM66NkWoOQ@mail.gmail.com>
[not found] ` <4F9E9906.8060401@ilande.co.uk>
2012-05-01 6:57 ` [Qemu-devel] Memory API: handling unassigned physical memory Blue Swirl
2012-05-01 13:53 ` Anthony Liguori
2012-05-01 18:48 ` Mark Cave-Ayland
2012-05-02 15:15 ` Bob Breuer
2012-05-06 8:45 ` Blue Swirl
2012-05-06 8:41 ` Blue Swirl
[not found] ` <CAFEAcA9VeJWPQ-LU=DvX6vp+=g44-uWda7zokK2NKfLiSkgGAg@mail.gmail.com>
[not found] ` <4F9EA2AD.9050208@ilande.co.uk>
2012-05-01 7:10 ` Blue Swirl
2012-05-01 18:50 ` Mark Cave-Ayland [this message]
2012-05-01 21:21 ` Andreas Färber
[not found] ` <4F9E9569.5000700@redhat.com>
[not found] ` <CAFEAcA_wFfsq=PwHAc_r-2bgdwUpSHaTOaL2VPVCJSs9x_JT6A@mail.gmail.com>
2012-05-01 12:39 ` Avi Kivity
2012-05-01 12:41 ` Peter Maydell
2012-05-01 12:42 ` Avi Kivity
2012-05-01 12:43 ` Peter Maydell
2012-05-01 12:48 ` Avi Kivity
2012-05-01 12:49 ` Peter Maydell
2012-05-01 13:01 ` Avi Kivity
2012-05-01 13:50 ` Anthony Liguori
2012-05-01 14:00 ` Peter Maydell
2012-05-01 14:06 ` Anthony Liguori
2012-05-01 14:20 ` Peter Maydell
2012-05-01 15:09 ` Anthony Liguori
2012-05-01 15:20 ` Peter Maydell
2012-05-01 15:26 ` Anthony Liguori
2012-05-01 15:37 ` Peter Maydell
2012-05-01 17:21 ` Anthony Liguori
2012-05-01 18:57 ` Mark Cave-Ayland
2012-05-01 19:03 ` Peter Maydell
2012-05-01 14:09 ` Avi Kivity
2012-05-01 14:15 ` Anthony Liguori
2012-05-01 14:26 ` Avi Kivity
2012-05-01 15:13 ` Anthony Liguori
[not found] ` <4F9E96EC.5080005@codemonkey.ws>
2012-05-01 12:41 ` Avi Kivity
[not found] ` <4F9E964A.1010408@ilande.co.uk>
2012-05-01 12:46 ` 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=4FA03083.4030104@ilande.co.uk \
--to=mark.cave-ayland@ilande.co.uk \
--cc=blauwirbel@gmail.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.