From: peter.maydell@linaro.org (Peter Maydell)
To: linux-arm-kernel@lists.infradead.org
Subject: [kvmarm] [Qemu-devel] [RFC] Virtio-desktop: Virtio-based virtual desktop
Date: Thu, 24 Jan 2013 14:42:36 +0000 [thread overview]
Message-ID: <CAFEAcA-EM-aj-tMZbfhbLg20OB0iBk7qnTRuYav0PBaRNTsXXw@mail.gmail.com> (raw)
In-Reply-To: <EC4021BD-DDB7-4D28-BD79-4B7A809200AE@suse.de>
On 24 January 2013 14:38, Alexander Graf <agraf@suse.de> wrote:
> But check out the QEMU e500 machine. We have a fully device tree
> based machine type in the kernel. QEMU drives it by generating a
> device tree for devices it actually exposes on the fly.
The ARM equivalent for that would be mach-virt, I think
(I forget what the status is but no doubt somebody will
remind me :-))
> The big advantage we have here is that
>
> 1) We don't have to emulate all hardware real hardware emulates
> 2) We're not restricted to emulate what real hardware emulates. PCI on ARM anyone?
...do we have an ARM PCI controller of any working kind in
the kernel? versatilepb's PCI controller doesn't count as
it is utterly broken :-)
-- PMM
next prev parent reply other threads:[~2013-01-24 14:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CALrVBktEQM5D-L+60RTzdRgo7jLZ671KxWMUFGnQwQ1bzgjO2A@mail.gmail.com>
2013-01-24 9:25 ` [Qemu-devel] [RFC] Virtio-desktop: Virtio-based virtual desktop Stefan Hajnoczi
2013-01-24 14:38 ` [kvmarm] " Alexander Graf
2013-01-24 14:42 ` Peter Maydell [this message]
2013-01-24 14:52 ` Alexander Graf
[not found] ` <CALrVBksLFyq5Vb+oLtASrdgU6x=GxXCEFy_ZWmvSosDOU6CsiQ@mail.gmail.com>
2013-01-25 7:46 ` Stefan Hajnoczi
2013-01-25 19:04 ` Blue Swirl
2013-01-25 19:31 ` [kvmarm] " Alexander Graf
2013-01-27 8:20 ` [Qemu-devel] [kvmarm] " Gleb Natapov
2013-01-27 10:12 ` Blue Swirl
2013-01-27 13:53 ` Gleb Natapov
2013-01-27 14:07 ` [Qemu-devel] " Anthony Liguori
2013-01-27 16:23 ` [kvmarm] " Alexander Graf
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=CAFEAcA-EM-aj-tMZbfhbLg20OB0iBk7qnTRuYav0PBaRNTsXXw@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=linux-arm-kernel@lists.infradead.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).