Linux s390 Architecture development
 help / color / mirror / Atom feed
From: Julian Ruess <julianr@linux.ibm.com>
To: schnelle@linux.ibm.com, wintera@linux.ibm.com, ts@linux.ibm.com,
	oberpar@linux.ibm.com, gbayer@linux.ibm.com
Cc: mjrosato@linux.ibm.com, alifm@linux.ibm.com, raspl@linux.ibm.com,
	hca@linux.ibm.com, agordeev@linux.ibm.com, gor@linux.ibm.com,
	julianr@linux.ibm.com,
	linux390-list@tuxmaker.boeblingen.de.ibm.com,
	linux-s390@vger.kernel.org
Subject: [PATCH 0/4] Introduce dibs peer bus driver, dibs console and dibs block device driver
Date: Thu, 08 Oct 2026 10:08:02 +0200	[thread overview]
Message-ID: <20261008-console_server-v1-0-636b11ebf191@linux.ibm.com> (raw)

Hi all,

this series is based on net-next.

It introduces the concept of dibs peer devices as devices on a virtual
bus, called the dibs peer bus, implemented on top of the dibs
communication layer. These devices are based on the concept that one
peer on a dibs abstracted fabric can present virtual devices for
consumption by other peers on the same fabric. In this series two such
device drivers, a console/tty driver and a block device driver are
included. While the console/tty allows two peers to establish a virtual
TTY between them the block device driver allows read-only access to
block data, such as the contents of an image file.

This is a prerequisite for an in-development, open-source user space
driver stack (console server) that uses the s390 ISM (Internal Shared
Memory) device to implement and announce dibs peer devices to multiple
remote target systems. These peer devices are currently of type console
and block device. In addition to the console device which enables
console access, the block device support enables a target system to
access resources such as ISO images provided by the console server. Both
the console and block device functionality operate without requiring any
network connectivity. The console server is planned to be part of
s390-tools.

Thank you,
Julian and Tobias

Signed-off-by: Julian Ruess <julianr@linux.ibm.com>
---
Julian Ruess (3):
      dibs: introduce dibs peer device bus driver
      dibs: introduce dibs console peer device driver
      dibs: introduce dibs block device peer device driver

Tobias Schumacher (1):
      dibs: introduce ring-buffer send/receive API

 arch/s390/configs/debug_defconfig |    3 +
 arch/s390/configs/defconfig       |    3 +
 drivers/dibs/Kconfig              |   32 +
 drivers/dibs/Makefile             |    5 +-
 drivers/dibs/dibs_blk.c           |  798 ++++++++++++++++++++++++
 drivers/dibs/dibs_console.c       |  388 ++++++++++++
 drivers/dibs/dibs_main.c          |  500 ++++++++++++++-
 drivers/dibs/dibs_peer_bus_drv.c  | 1220 +++++++++++++++++++++++++++++++++++++
 include/linux/dibs.h              |  177 +++++-
 9 files changed, 3122 insertions(+), 4 deletions(-)
---
base-commit: 8df0638138d3e0344fd1fb36cf2d1ca1cf5028f0
change-id: 20260330-console_server-fc7a9ced6481

Best regards,
-- 
Julian Ruess <julianr@linux.ibm.com>


             reply	other threads:[~2026-10-08  8:08 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-08  8:08 Julian Ruess [this message]
2026-10-08  8:08 ` [PATCH 1/4] dibs: introduce ring-buffer send/receive API Julian Ruess
2026-10-08  8:21   ` sashiko-bot
2026-10-09 20:47   ` Niklas Schnelle
2026-10-08  8:08 ` [PATCH 2/4] dibs: introduce dibs peer device bus driver Julian Ruess
2026-10-08  8:27   ` sashiko-bot
2026-10-08  8:08 ` [PATCH 3/4] dibs: introduce dibs console peer device driver Julian Ruess
2026-10-08  8:26   ` sashiko-bot
2026-10-08  8:08 ` [PATCH 4/4] dibs: introduce dibs block device " Julian Ruess
2026-10-08  8:30   ` sashiko-bot

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=20261008-console_server-v1-0-636b11ebf191@linux.ibm.com \
    --to=julianr@linux.ibm.com \
    --cc=agordeev@linux.ibm.com \
    --cc=alifm@linux.ibm.com \
    --cc=gbayer@linux.ibm.com \
    --cc=gor@linux.ibm.com \
    --cc=hca@linux.ibm.com \
    --cc=linux-s390@vger.kernel.org \
    --cc=linux390-list@tuxmaker.boeblingen.de.ibm.com \
    --cc=mjrosato@linux.ibm.com \
    --cc=oberpar@linux.ibm.com \
    --cc=raspl@linux.ibm.com \
    --cc=schnelle@linux.ibm.com \
    --cc=ts@linux.ibm.com \
    --cc=wintera@linux.ibm.com \
    /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