From: Will Deacon <will.deacon@arm.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Pranavkumar Sawargaonkar <pranavkumar@linaro.org>,
"linaro-kernel@lists.linaro.org" <linaro-kernel@lists.linaro.org>,
Patch Tracking <patches@linaro.org>,
Marc Zyngier <Marc.Zyngier@arm.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"kvmarm@lists.cs.columbia.edu" <kvmarm@lists.cs.columbia.edu>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [RFC] arm64: Early printk support for virtio-mmio console devices.
Date: Fri, 19 Apr 2013 10:36:24 +0100 [thread overview]
Message-ID: <20130419093624.GC13283@mudshark.cambridge.arm.com> (raw)
In-Reply-To: <CAFEAcA8j124G=vaHObJ_w5wOhUiS3KYKbjMnigbnr6mgwFxZUg@mail.gmail.com>
On Fri, Apr 19, 2013 at 10:30:40AM +0100, Peter Maydell wrote:
> On 19 April 2013 10:27, Will Deacon <will.deacon@arm.com> wrote:
> > On Fri, Apr 19, 2013 at 10:25:35AM +0100, Pranavkumar Sawargaonkar wrote:
> >> I am not against using 8250 emulation (as far as it solves printk
> >> issues for kernel booting logs), but my point is why not to add early
> >> read-write support for virtio console, which also can be useful in
> >> emulation less mach-virt environment also ?
> >
> > We can have both, but only one of those requires a change to the virtio
> > specification.
>
> I don't think avoiding writing a spec is necessarily a good reason
> for insisting on emulation of a lump of hardware 95% of whose
> capabilities you aren't going to use...
Don't get me wrong; I'm in favour of having earlyprintk over virtio console
too, I'm just pointing out that we can also plug in the 8250 emulation that
we already have with very little effort. I'm not insisting on anything.
Will
next prev parent reply other threads:[~2013-04-19 9:36 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-18 5:52 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 [this message]
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
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=20130419093624.GC13283@mudshark.cambridge.arm.com \
--to=will.deacon@arm.com \
--cc=Marc.Zyngier@arm.com \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@linaro.org \
--cc=peter.maydell@linaro.org \
--cc=pranavkumar@linaro.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
Powered by JetHome