From: Pawel Moll <pawel.moll@arm.com>
To: Christopher Covington <cov@codeaurora.org>
Cc: Peter Maydell <peter.maydell@linaro.org>,
"virtualization@lists.linux-foundation.org"
<virtualization@lists.linux-foundation.org>
Subject: Re: VirtIO-MMIO on MMU-less System
Date: Tue, 28 Oct 2014 16:48:13 +0000 [thread overview]
Message-ID: <1414514893.15353.1.camel@arm.com> (raw)
In-Reply-To: <544FC762.5060507@codeaurora.org>
On Tue, 2014-10-28 at 16:42 +0000, Christopher Covington wrote:
> Just out of curiosity, could VirtIO-MMIO peripherals work on an MMU-less
> system, such as a hypothetical M-flavor QEMU TCG virt machine?
The interface is using physical addresses (or physical page numbers), so
MMU or not - it doesn't care.
Now, whether the existing implementation of the drivers (or host-side
implementation of the virtoo device) would work, that's another
question. I see nothing in virtio-mmio driver that clearly wouldn't
work, but you never know...
Pawel
next prev parent reply other threads:[~2014-10-28 16:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-28 16:42 VirtIO-MMIO on MMU-less System Christopher Covington
2014-10-28 16:48 ` Pawel Moll [this message]
2014-10-28 16:51 ` 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=1414514893.15353.1.camel@arm.com \
--to=pawel.moll@arm.com \
--cc=cov@codeaurora.org \
--cc=peter.maydell@linaro.org \
--cc=virtualization@lists.linux-foundation.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