From: cov@codeaurora.org (Christopher Covington)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] Early printk support for virtio console devices.
Date: Tue, 07 May 2013 11:52:45 -0400 [thread overview]
Message-ID: <5189234D.3040208@codeaurora.org> (raw)
In-Reply-To: <CAFEAcA9jBSpN2p9ZaU+_gX41Ke3nvpSKVrWV8Rioy_ioadKCgg@mail.gmail.com>
On 05/07/2013 08:19 AM, Peter Maydell wrote:
> On 7 May 2013 05:46, Rusty Russell <rusty@rustcorp.com.au> wrote:
>> Peter Maydell <peter.maydell@linaro.org> writes:
>>> That all looks like sensible QEMU implementation possibilities
>>> but it seems to be a bit of a non-sequitur from "how do we
>>> tell the kernel to actually use this?"
>>
>> You enable the feature in the virtio console device, and a kernel
>> compiled with EARLY_PRINTK will use it?
>
> Well, at the moment EARLY_PRINTK is hardcoded to
> "use some specific UART or equivalent selected at
> compile time". So the equivalent presumably would
> be to hard-compile "use virtio-console", but then
> how does that code know where the virtio-console
> is in the address space?
arm64 uses a kernel argument.
Christopher
--
Employee of Qualcomm Innovation Center, Inc.
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
hosted by the Linux Foundation.
WARNING: multiple messages have this Message-ID (diff)
From: Christopher Covington <cov@codeaurora.org>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Rusty Russell <rusty@rustcorp.com.au>,
"linaro-kernel@lists.linaro.org" <linaro-kernel@lists.linaro.org>,
"patches@linaro.org" <patches@linaro.org>,
"linux-kernel@vger.kernel.org List"
<linux-kernel@vger.kernel.org>, Alexander Graf <agraf@suse.de>,
Amit Shah <amit.shah@redhat.com>,
"kvmarm@lists.cs.columbia.edu" <kvmarm@lists.cs.columbia.edu>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Pranavkumar Sawargaonkar <pranavkumar@linaro.org>
Subject: Re: [PATCH 0/2] Early printk support for virtio console devices.
Date: Tue, 07 May 2013 11:52:45 -0400 [thread overview]
Message-ID: <5189234D.3040208@codeaurora.org> (raw)
In-Reply-To: <CAFEAcA9jBSpN2p9ZaU+_gX41Ke3nvpSKVrWV8Rioy_ioadKCgg@mail.gmail.com>
On 05/07/2013 08:19 AM, Peter Maydell wrote:
> On 7 May 2013 05:46, Rusty Russell <rusty@rustcorp.com.au> wrote:
>> Peter Maydell <peter.maydell@linaro.org> writes:
>>> That all looks like sensible QEMU implementation possibilities
>>> but it seems to be a bit of a non-sequitur from "how do we
>>> tell the kernel to actually use this?"
>>
>> You enable the feature in the virtio console device, and a kernel
>> compiled with EARLY_PRINTK will use it?
>
> Well, at the moment EARLY_PRINTK is hardcoded to
> "use some specific UART or equivalent selected at
> compile time". So the equivalent presumably would
> be to hard-compile "use virtio-console", but then
> how does that code know where the virtio-console
> is in the address space?
arm64 uses a kernel argument.
Christopher
--
Employee of Qualcomm Innovation Center, Inc.
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
hosted by the Linux Foundation.
next prev parent reply other threads:[~2013-05-07 15:52 UTC|newest]
Thread overview: 68+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-26 11:04 [PATCH 0/2] Early printk support for virtio console devices Pranavkumar Sawargaonkar
2013-04-26 11:04 ` Pranavkumar Sawargaonkar
2013-04-26 11:04 ` [PATCH 1/2] virtio: console: Add early writeonly register to config space Pranavkumar Sawargaonkar
2013-04-26 11:04 ` Pranavkumar Sawargaonkar
2013-04-29 3:10 ` Rusty Russell
2013-04-29 3:10 ` Rusty Russell
2013-04-26 11:04 ` [PATCH 2/2] arm64: earlyprintk support for virtio-mmio console Pranavkumar Sawargaonkar
2013-04-26 11:04 ` Pranavkumar Sawargaonkar
2013-04-26 11:19 ` [PATCH 0/2] Early printk support for virtio console devices Alexander Graf
2013-04-26 11:19 ` Alexander Graf
2013-04-26 11:33 ` Peter Maydell
2013-04-26 11:33 ` Peter Maydell
2013-04-26 12:06 ` Anup Patel
2013-04-26 12:06 ` Anup Patel
2013-04-26 12:33 ` Arnd Bergmann
2013-04-26 12:33 ` Arnd Bergmann
2013-04-26 12:59 ` Anup Patel
2013-04-26 12:59 ` Anup Patel
2013-04-26 15:03 ` Arnd Bergmann
2013-04-26 15:03 ` Arnd Bergmann
2013-04-26 15:54 ` Marc Zyngier
2013-04-26 15:54 ` Marc Zyngier
2013-04-26 15:19 ` Peter Maydell
2013-04-26 15:19 ` Peter Maydell
2013-04-29 3:09 ` Rusty Russell
2013-04-29 3:09 ` Rusty Russell
2013-04-29 12:22 ` Alexander Graf
2013-04-29 12:22 ` Alexander Graf
2013-04-29 12:48 ` Pranavkumar Sawargaonkar
2013-04-29 12:48 ` Pranavkumar Sawargaonkar
2013-04-29 12:53 ` Alexander Graf
2013-04-29 12:53 ` Alexander Graf
2013-05-01 2:07 ` Rusty Russell
2013-05-01 2:07 ` Rusty Russell
2013-05-01 6:53 ` Anup Patel
2013-05-01 6:53 ` Anup Patel
2013-05-01 14:46 ` Will Deacon
2013-05-01 14:46 ` Will Deacon
2013-05-02 10:06 ` Peter Maydell
2013-05-02 10:06 ` Peter Maydell
2013-05-06 5:11 ` Rusty Russell
2013-05-06 5:11 ` Rusty Russell
2013-05-06 9:14 ` Peter Maydell
2013-05-06 9:14 ` Peter Maydell
2013-05-07 4:46 ` Rusty Russell
2013-05-07 4:46 ` Rusty Russell
2013-05-07 12:19 ` Peter Maydell
2013-05-07 12:19 ` Peter Maydell
2013-05-07 15:52 ` Christopher Covington [this message]
2013-05-07 15:52 ` Christopher Covington
2013-05-07 15:58 ` Peter Maydell
2013-05-07 15:58 ` Peter Maydell
2013-05-08 14:17 ` Catalin Marinas
2013-05-08 14:17 ` Catalin Marinas
2013-05-09 10:39 ` Grant Likely
2013-05-09 10:39 ` Grant Likely
2013-05-06 9:40 ` Pranavkumar Sawargaonkar
2013-05-06 9:40 ` Pranavkumar Sawargaonkar
2013-04-29 12:50 ` Peter Maydell
2013-04-29 12:50 ` Peter Maydell
2013-04-29 12:53 ` Alexander Graf
2013-04-29 12:53 ` Alexander Graf
2013-04-30 0:32 ` Rusty Russell
2013-04-30 0:32 ` Rusty Russell
2013-05-01 0:26 ` Alexander Graf
2013-05-01 0:26 ` Alexander Graf
2013-05-01 5:01 ` Anup Patel
2013-05-01 5:01 ` Anup Patel
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=5189234D.3040208@codeaurora.org \
--to=cov@codeaurora.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.