linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Steffen Eiden <seiden@linux.ibm.com>
To: Heiko Carstens <hca@linux.ibm.com>,
	Alexander Gordeev <agordeev@linux.ibm.com>,
	Christian Borntraeger <borntraeger@linux.ibm.com>,
	Janosch Frank <frankja@linux.ibm.com>,
	Claudio Imbrenda <imbrenda@linux.ibm.com>,
	Vasily Gorbik <gor@linux.ibm.com>,
	linux-s390@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-mm@kvack.org
Cc: nrb@linux.ibm.com
Subject: [PATCH 0/2] s390: Autoload uvdevice module based on CPU feature
Date: Fri,  1 Jul 2022 12:02:08 +0200	[thread overview]
Message-ID: <20220701100210.5482-1-seiden@linux.ibm.com> (raw)

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=y, Size: 607 bytes --]

Currently, the uvdevice (drivers/s390/char/uvdevice) must be loaded
manually. We can, however, determine if the Ultravisor is available
by observing facility 158. 

This series, first, introduces the HWCAP_UV connected to facility 158.
And, second, it automatically loads the uvdevice if HWCAP_UV is present.

Steffen Eiden (2):
  s390/hwcaps: Add HWCAP_UV
  drivers/s390/char/uvdevice: Autoload module based on CPU feature

 arch/s390/include/asm/elf.h  | 2 ++
 arch/s390/kernel/processor.c | 5 +++++
 drivers/s390/char/uvdevice.c | 5 ++---
 3 files changed, 9 insertions(+), 3 deletions(-)

-- 
2.35.3



             reply	other threads:[~2022-07-01 10:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-01 10:02 Steffen Eiden [this message]
2022-07-01 10:02 ` [PATCH 1/2] s390/hwcaps: Add HWCAP_UV Steffen Eiden
2022-07-01 10:10   ` Christian Borntraeger
2022-07-04 10:00     ` Heiko Carstens
2022-07-04 11:35       ` Steffen Eiden
2022-07-01 10:02 ` [PATCH 2/2] drivers/s390/char/uvdevice: Autoload module based on CPU feature Steffen Eiden

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=20220701100210.5482-1-seiden@linux.ibm.com \
    --to=seiden@linux.ibm.com \
    --cc=agordeev@linux.ibm.com \
    --cc=borntraeger@linux.ibm.com \
    --cc=frankja@linux.ibm.com \
    --cc=gor@linux.ibm.com \
    --cc=hca@linux.ibm.com \
    --cc=imbrenda@linux.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=nrb@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;
as well as URLs for NNTP newsgroup(s).