From: Jag Raman <jag.raman@oracle.com>
To: sparclinux@vger.kernel.org
Subject: [PATCH v3 0/5] LDC changes for porting VCC driver into upstream kernel
Date: Thu, 25 May 2017 14:25:53 +0000 [thread overview]
Message-ID: <cover.1495721691.git.jag.raman@oracle.com> (raw)
This series of patches is part of an effort to add VCC (Virtual Channel
Concentrator) and VDS (Virtual Disk Server) support to Linux.
VCC & VDS enable the virtualization of serial console and storage
respectively, on SPARC processors. VCC provides access to the guest
domain's serial console. VDS provides the ability to allocate storage to
the guest domain.
Both VCC & VDS depend 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 & VDS to be enabled, it requires that these core functionalities
support them.
This version 3 of the series addresses the following changes
suggested by Dave Miller
Patch 1/5: Removes ldc_enable_hv_intr & ldc_disable_hv_intr APIs
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 | 6 ++
arch/sparc/kernel/ldc.c | 145 +++++++++++++++++++++++++++++------------
2 files changed, 108 insertions(+), 43 deletions(-)
next reply other threads:[~2017-05-25 14:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-25 14:25 Jag Raman [this message]
2017-05-26 5:41 ` [PATCH v3 0/5] LDC changes for porting VCC driver into upstream kernel Christoph Hellwig
2017-05-26 15:51 ` Jag Raman
2017-05-26 16:27 ` 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.1495721691.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.