[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <217a4f2dd017af16204391012751e9f9@localhost>
Date: Thu, 18 Apr 2013 17:59:43 +0200
From: Marc Zyngier <marc.zyngier@....com>
To: Christopher Covington <cov@...eaurora.org>
Cc: PranavkumarSawargaonkar <pranavkumar@...aro.org>,
<linaro-kernel@...ts.linaro.org>,
Anup Patel <anup.patel@...aro.org>, <patches@...aro.org>,
<rusty@...tcorp.com.au>, <linux-kernel@...r.kernel.org>,
<kvmarm@...ts.cs.columbia.edu>,
<linux-arm-kernel@...ts.infradead.org>
Subject: Re: [RFC] arm64: Early printk support for virtio-mmio console devices.
On Thu, 18 Apr 2013 11:25:56 -0400, Christopher Covington
<cov@...eaurora.org> wrote:
> Hi Pranavkumar,
>
> On 04/18/2013 01:52 AM, PranavkumarSawargaonkar wrote:
>> From: Pranavkumar Sawargaonkar <pranavkumar@...aro.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.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists