From: Anthony Liguori <anthony@codemonkey.ws>
To: Blue Swirl <blauwirbel@gmail.com>
Cc: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Memory API: handling unassigned physical memory
Date: Tue, 01 May 2012 08:53:38 -0500 [thread overview]
Message-ID: <4F9FEAE2.9040205@codemonkey.ws> (raw)
In-Reply-To: <CAAu8pHs2cAqoWg9z4PSceXEmqbwA340=wa4WRFdkBW1n=VVerA@mail.gmail.com>
On 05/01/2012 01:57 AM, Blue Swirl wrote:
> On Mon, Apr 30, 2012 at 13:52, Mark Cave-Ayland
> <mark.cave-ayland@ilande.co.uk> wrote:
>> On 30/04/12 14:27, Peter Maydell wrote:
>>
>> Hi Peter,
>>
>>
>>>> IMO the best fix is to unsysbus the device and qomify it instead. This
>>>> way we're 100% flexible in how we can attach it.
>>>
>>>
>>> You don't need to wait for QOM to grow enough features to
>>> replace sysbus. If you don't like what sysbus_mmio_map() does, you
>>
>>
>> Oh - so does this mean that QOM is not feature-complete?
>
> At least 'Pin' class to replace GPIOs and IRQs is not in HEAD (but
> Anthony already has a tree somewhere) and I can't remember what was
> the plan for buses.
I'm planning on pushing bus support in before I freeze 1.1.
Regards,
Anthony Liguori
next prev parent reply other threads:[~2012-05-01 13:53 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 [this message]
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
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=4F9FEAE2.9040205@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=blauwirbel@gmail.com \
--cc=mark.cave-ayland@ilande.co.uk \
--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.