public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Marc Zyngier <marc.zyngier@arm.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Anup Patel <anup.patel@linaro.org>,
	Peter Maydell <peter.maydell@linaro.org>,
	"linaro-kernel@lists.linaro.org" <linaro-kernel@lists.linaro.org>,
	"patches@linaro.org" <patches@linaro.org>,
	Alexander Graf <agraf@suse.de>,
	"linux-kernel@vger.kernel.org List"
	<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: [PATCH 0/2] Early printk support for virtio console devices.
Date: Fri, 26 Apr 2013 16:54:01 +0100	[thread overview]
Message-ID: <517AA319.5070709@arm.com> (raw)
In-Reply-To: <201304261703.17798.arnd@arndb.de>

On 26/04/13 16:03, Arnd Bergmann wrote:
> On Friday 26 April 2013, Anup Patel wrote:
>> I am curious about how smh-based or hypercall-based early prints would
>> be handled in following scenario:
>>
>> "A board is running KVM ARM enabled kernel and linux console on serial
>> port. Now a user remotely connects to the board via telnet/ssh and
>> launches a VM with smh-based or hypercall-based earlyprintk."
>>
>> In the above scenario, will smh-based or hypercall-based earlyprints
>> appear to user on remote shell or not ?
> 
> The implementation of the console device would still be done by KVM,
> as for any other virtual device, so it shows up whereever kvm is
> configured to output the console data.

Actually, at least in the case of smh-based earlyprintk, the output only
appears in the model console, and never reach the rest of the kernel.

And any other non-MMIO approach (like a hypercall) will be very hard to
feed back to the console, as KVM itself has no idea of what a "console"
is. You'd need another side channel to userspace, hoping that it will be
able to merge the multiple streams.

	M.
-- 
Jazz is not dead. It just smells funny...


  reply	other threads:[~2013-04-26 15:54 UTC|newest]

Thread overview: 34+ 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 ` [PATCH 1/2] virtio: console: Add early writeonly register to config space Pranavkumar Sawargaonkar
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:19 ` [PATCH 0/2] Early printk support for virtio console devices Alexander Graf
2013-04-26 11:33   ` Peter Maydell
2013-04-26 12:06     ` Anup Patel
2013-04-26 12:33       ` Arnd Bergmann
2013-04-26 12:59         ` Anup Patel
2013-04-26 15:03           ` Arnd Bergmann
2013-04-26 15:54             ` Marc Zyngier [this message]
2013-04-26 15:19         ` Peter Maydell
2013-04-29  3:09   ` Rusty Russell
2013-04-29 12:22     ` Alexander Graf
2013-04-29 12:48       ` Pranavkumar Sawargaonkar
2013-04-29 12:53         ` Alexander Graf
2013-05-01  2:07           ` Rusty Russell
2013-05-01  6:53             ` Anup Patel
2013-05-01 14:46               ` Will Deacon
2013-05-02 10:06             ` Peter Maydell
2013-05-06  5:11               ` Rusty Russell
2013-05-06  9:14                 ` Peter Maydell
2013-05-07  4:46                   ` Rusty Russell
2013-05-07 12:19                     ` Peter Maydell
2013-05-07 15:52                       ` Christopher Covington
2013-05-07 15:58                         ` Peter Maydell
2013-05-08 14:17                           ` Catalin Marinas
2013-05-09 10:39                             ` Grant Likely
2013-05-06  9:40                 ` Pranavkumar Sawargaonkar
2013-04-29 12:50       ` Peter Maydell
2013-04-29 12:53         ` Alexander Graf
2013-04-30  0:32       ` Rusty Russell
2013-05-01  0:26         ` Alexander Graf
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=517AA319.5070709@arm.com \
    --to=marc.zyngier@arm.com \
    --cc=agraf@suse.de \
    --cc=anup.patel@linaro.org \
    --cc=arnd@arndb.de \
    --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 \
    /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