From: Juergen Gross <jgross@suse.com>
To: linux-s390@vger.kernel.org, linux-kernel@vger.kernel.org,
Heiko Carstens <hca@linux.ibm.com>,
Alexander Gordeev <agordeev@linux.ibm.com>,
Christian Borntraeger <borntraeger@linux.ibm.com>,
Vasily Gorbik <gor@linux.ibm.com>,
Sven Schnelle <svens@linux.ibm.com>
Subject: Re: [PATCH] s390/kvm: avoid hypfs error message
Date: Mon, 20 Jun 2022 08:03:18 +0200 [thread overview]
Message-ID: <5431f626-9bd3-ed54-9889-aafbba9ca3e0@suse.com> (raw)
In-Reply-To: <20220607123314.10255-1-jgross@suse.com>
[-- Attachment #1.1.1: Type: text/plain, Size: 890 bytes --]
Ping?
On 07.06.22 14:33, Juergen Gross wrote:
> When booting under KVM the following error messages are issued:
>
> hypfs.7f5705: The hardware system does not support hypfs
> hypfs.7a79f0: Initialization of hypfs failed with rc=-61
>
> While being documented, they can easily be avoided by bailing out of
> hypfs_init() early in case of running as a KVM guest.
>
> Signed-off-by: Juergen Gross <jgross@suse.com>
> ---
> arch/s390/hypfs/inode.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/arch/s390/hypfs/inode.c b/arch/s390/hypfs/inode.c
> index 5c97f48cea91..bdf078f3c641 100644
> --- a/arch/s390/hypfs/inode.c
> +++ b/arch/s390/hypfs/inode.c
> @@ -464,6 +464,9 @@ static int __init hypfs_init(void)
> {
> int rc;
>
> + if (MACHINE_IS_KVM)
> + return -ENODATA;
> +
> hypfs_dbfs_init();
>
> if (hypfs_diag_init()) {
[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 3149 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 495 bytes --]
next prev parent reply other threads:[~2022-06-20 6:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-07 12:33 [PATCH] s390/kvm: avoid hypfs error message Juergen Gross
2022-06-20 6:03 ` Juergen Gross [this message]
2022-06-20 7:18 ` Christian Borntraeger
2022-06-20 9:19 ` Heiko Carstens
2022-06-20 9:25 ` Juergen Gross
2022-06-20 9:28 ` Christian Borntraeger
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=5431f626-9bd3-ed54-9889-aafbba9ca3e0@suse.com \
--to=jgross@suse.com \
--cc=agordeev@linux.ibm.com \
--cc=borntraeger@linux.ibm.com \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=svens@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