From: marc.zyngier@arm.com (Marc Zyngier)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC] arm64: Early printk support for virtio-mmio console devices.
Date: Thu, 18 Apr 2013 17:59:43 +0200 [thread overview]
Message-ID: <217a4f2dd017af16204391012751e9f9@localhost> (raw)
In-Reply-To: <51701084.5050706@codeaurora.org>
On Thu, 18 Apr 2013 11:25:56 -0400, Christopher Covington
<cov@codeaurora.org> wrote:
> Hi Pranavkumar,
>
> On 04/18/2013 01:52 AM, PranavkumarSawargaonkar wrote:
>> From: Pranavkumar Sawargaonkar <pranavkumar@linaro.org>
>>
>> This patch implements early printk support for virtio-mmio console
>> devices
>> without using any hypercalls.
>
> Is it possible that using DCC might be an easier solution?
You would end up with the exact same problem as with a hypercall based
solution: once you're in the hypervisor, what do you do with the data? You
end up having to invent another channel to forward it down to your platform
emulation in order to have it printed where the user expects it.
Using a MMIO based solution is probably the best solution, as it uses the
existing infrastructure.
M.
--
Fast, cheap, reliable. Pick two.
next prev parent reply other threads:[~2013-04-18 15:59 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-18 5:52 [RFC] arm64: Early printk support for virtio-mmio console devices PranavkumarSawargaonkar
2013-04-18 6:49 ` Marc Zyngier
2013-04-18 7:24 ` Pranavkumar Sawargaonkar
[not found] ` <CAAHg+HhajHFC=1nh6YQNgpf=Na2FqcsYJ=t+ag9QiTg6TxUz9w@mail.gmail.com>
2013-04-18 7:36 ` Marc Zyngier
2013-04-18 8:48 ` Pranavkumar Sawargaonkar
2013-04-18 8:53 ` Alexander Graf
2013-04-19 9:05 ` Will Deacon
2013-04-19 9:25 ` Pranavkumar Sawargaonkar
2013-04-19 9:27 ` Will Deacon
2013-04-19 9:30 ` Peter Maydell
2013-04-19 9:34 ` Pranavkumar Sawargaonkar
2013-04-19 9:39 ` Will Deacon
2013-04-19 10:05 ` Peter Maydell
2013-04-19 16:12 ` Catalin Marinas
2013-04-19 16:14 ` Peter Maydell
2013-04-19 16:22 ` Catalin Marinas
2013-04-19 16:33 ` Peter Maydell
2013-04-19 17:14 ` Catalin Marinas
2013-04-19 17:40 ` Peter Maydell
2013-04-19 9:36 ` Will Deacon
2013-04-18 19:06 ` Pranavkumar Sawargaonkar
2013-04-18 8:30 ` Peter Maydell
2013-04-18 8:51 ` Alexander Graf
2013-04-18 8:51 ` Marc Zyngier
2013-04-18 6:51 ` Rusty Russell
2013-04-18 7:32 ` Pranavkumar Sawargaonkar
2013-04-18 8:44 ` Alexander Graf
2013-04-18 8:55 ` Pranavkumar Sawargaonkar
2013-04-18 10:01 ` Jean-Christophe PLAGNIOL-VILLARD
2013-04-22 1:21 ` Rusty Russell
2013-04-22 3:10 ` Anup Patel
2013-04-22 5:15 ` Rusty Russell
2013-04-23 5:53 ` Pranavkumar Sawargaonkar
2013-04-22 14:50 ` Alexander Graf
2013-04-18 15:25 ` Christopher Covington
2013-04-18 15:59 ` Marc Zyngier [this message]
2013-04-18 18:59 ` Pranavkumar Sawargaonkar
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=217a4f2dd017af16204391012751e9f9@localhost \
--to=marc.zyngier@arm.com \
--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).