From: Christoffer Dall <cdall@cs.columbia.edu>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: tech@virtualopensystems.com, qemu-devel@nongnu.org,
android-virt@lists.cs.columbia.edu,
linaro-toolchain@lists.linaro.org
Subject: Re: [Qemu-devel] [Android-virt] plans for QEMU support for KVM on ARM
Date: Thu, 24 Nov 2011 15:11:02 -0500 [thread overview]
Message-ID: <CAEDV+gJZ2=_sVkeh8fbS822pKjd94dwHR4tLiFo2rcHxK1wW1A@mail.gmail.com> (raw)
In-Reply-To: <CAFEAcA-dvUKdpNgR66roUTnJx1JjfOA3zxGV_YLsjn8A8Lm3ew@mail.gmail.com>
>
> This isn't strictly a requirement for KVM, but we're going to want
> KVM to be able to hand off cp15 accesses to QEMU, and I don't think
> that's going to be maintainable or reliable without this refactoring.
Why do we need KVM to hand off cp15 accesses to QEMU? As of now almost
all of this is supported in-kernel. Do the CP15 behavior vary that
much according to the board config? I would think that other
co-processor accesses would actually be more important if they're used
as interfaces for DSPs etc. But in that case, yes, we need a way to
handle them at least.
>
> [snip]
>
> Also on the radar is a fourth piece of work:
>
> * QEMU virtio-mmio support
>
> This is adding support for the 'mmio' virtio transport, which will
> allow virtio support in a versatile-express model. We're going to
> need this at some point but the current thought is that we want
> to do the above listed more important bits of work first...
> (The exception would probably be if it turned out that this was
> sufficiently useful for making early KVM development easier)
I don't really see why it would be. Is this not merely a question of
performance?
>
> So, questions:
> (1) did we forget something important?
> (2) is anybody else already planning to do any of this (or would
> like to start)? if so we should coordinate...
> (3) is there anything that the kernel folk need/want earlier
> rather than later?
>
Thanks for sending this out.
I would like some clarity (if possible) of which branch the KVM
support for ARM should be based on. Is it the Linaro version of QEMU
and basically just keep rebasing the changes off there until someone
accepts them or?
What would be helpful from the point of view of KVM is to have basic
ARM host support and the A15 system model upstream.
Currently there are a number of changes to the configure script to
make things work and we link against a prebuilt zlib library that we
keep distributing to people who wish to build QEMU for KVM/ARM. I am
not an expert on QEMU and would definitely like some help on doing
this the right way. What's the recommended procedure? Should I send
out the hack-ish patch we have now, and if so, what should be the base
of such a patch.
Best,
Christoffer
next prev parent reply other threads:[~2011-11-24 20:11 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-22 14:44 [Qemu-devel] plans for QEMU support for KVM on ARM Peter Maydell
2011-11-22 15:05 ` [Qemu-devel] [Android-virt] " Alexander Graf
2011-11-22 15:19 ` Peter Maydell
2011-11-23 8:45 ` Paolo Bonzini
2011-11-23 8:55 ` Peter Maydell
2011-11-23 7:50 ` [Qemu-devel] " Jubi Taneja
2011-11-23 8:59 ` Peter Maydell
2011-11-24 20:11 ` Christoffer Dall [this message]
2011-11-24 21:27 ` [Qemu-devel] [Android-virt] " Peter Maydell
2011-11-24 22:02 ` Christoffer Dall
2011-11-24 23:06 ` Peter Maydell
2011-11-24 23:10 ` Alexander Graf
2011-11-24 23:11 ` Peter Maydell
2011-11-24 23:12 ` Alexander Graf
2011-11-24 23:21 ` Christoffer Dall
2011-11-29 18:16 ` Peter Maydell
2011-11-29 18:22 ` Christoffer Dall
2011-11-24 23:08 ` Alexander Graf
2011-11-28 20:51 ` Scott Wood
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='CAEDV+gJZ2=_sVkeh8fbS822pKjd94dwHR4tLiFo2rcHxK1wW1A@mail.gmail.com' \
--to=cdall@cs.columbia.edu \
--cc=android-virt@lists.cs.columbia.edu \
--cc=linaro-toolchain@lists.linaro.org \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=tech@virtualopensystems.com \
/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).