linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: pranavkumar@linaro.org (Pranavkumar Sawargaonkar)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] Early printk support for virtio console devices.
Date: Fri, 26 Apr 2013 16:34:54 +0530	[thread overview]
Message-ID: <1366974299-17877-1-git-send-email-pranavkumar@linaro.org> (raw)

This patch-set implements early printk support for virtio console devices without using any hypercalls.

The current virtio early printk code in kernel expects that hypervisor will provide some mechanism generally a hypercall to support early printk. This patch-set does not break existing hypercall based early print support.

This implementation adds:
1. Early writeonly register named early_wr in virtio console's config space.
2. Host feature flags namely VIRTIO_CONSOLE_F_EARLY_WRITE for telling guest about early-write capability in console device.

Early write mechanism:
1. When a guest wants to out some character, it has to simply write the character to early_wr register in config space of virtio console device.

Pranavkumar Sawargaonkar (2):
  virtio: console: Add early writeonly register to config space
  arm64: earlyprintk support for virtio-mmio console

 Documentation/virtual/virtio-spec.txt |   13 ++++++++++--
 arch/arm64/kernel/early_printk.c      |   35 +++++++++++++++++++++++++++++++++
 include/uapi/linux/virtio_console.h   |    3 +++
 3 files changed, 49 insertions(+), 2 deletions(-)

-- 
1.7.9.5

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

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-26 11:04 Pranavkumar Sawargaonkar [this message]
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
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=1366974299-17877-1-git-send-email-pranavkumar@linaro.org \
    --to=pranavkumar@linaro.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 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).