All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jag Raman <jag.raman@oracle.com>
To: sparclinux@vger.kernel.org
Subject: [PATCH v4 0/5] LDC changes for porting VCC driver into upstream kernel
Date: Fri, 09 Jun 2017 16:29:27 +0000	[thread overview]
Message-ID: <cover.1497022394.git.jag.raman@oracle.com> (raw)

This series of patches is part of an effort to add VCC (Virtual Console
Concentrator) support to Linux.

VCC enables the virtualization of serial console on SPARC processors. VCC 
provides access to the guest domain's serial console.

VCC depends on some core functionalities in the linux kernel for SPARC. The 
functionalities include LDC (Logical Domain Channels), MDESC (Machine
Descriptor) and VIO (Virtual IO protocol). In order for VCC to be enabled,
it requires that these core functionalities support them.

This series of patches adds LDC support to enable VCC on Linux. It
is the first batch of changes to enable VCC.

This version 4 of the series addresses the following changes
suggested by Dave Miller
Patch 1/5: Modifies ldc_print/__ldc_print to print caller name. Fixes
           indentation of wrapped lines.

Jag Raman (5):
  sparc64: expand LDC interface
  sparc64: enhance ldc_abort to print message
  sparc64: ensure LDC channel is ready before communication
  sparc64: ldc abort during vds iso boot
  sparc64: print debug messages when reading from LDC channel

 arch/sparc/include/asm/ldc.h |    8 +++
 arch/sparc/kernel/ldc.c      |  141 +++++++++++++++++++++++++++++-------------
 2 files changed, 106 insertions(+), 43 deletions(-)


             reply	other threads:[~2017-06-09 16:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-09 16:29 Jag Raman [this message]
2017-06-10 21:12 ` [PATCH v4 0/5] LDC changes for porting VCC driver into upstream kernel David Miller

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=cover.1497022394.git.jag.raman@oracle.com \
    --to=jag.raman@oracle.com \
    --cc=sparclinux@vger.kernel.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.