On 03.12.18 11:29, Cornelia Huck wrote:
On Mon, 3 Dec 2018 11:09:37 +0100
Michael Mueller <mimu@xxxxxxxxxxxxx> wrote:
On 03.12.18 10:50, Cornelia Huck wrote:
On Fri, 30 Nov 2018 15:32:15 +0100
Michael Mueller <mimu@xxxxxxxxxxxxx> wrote:
By initializing the GIB, it will be used by the kvm host.
Signed-off-by: Michael Mueller <mimu@xxxxxxxxxxxxx>
---
Documentation/kmsg/s390/kvm | 12 ++++++++++++
arch/s390/kvm/kvm-s390.c | 10 +++++++++-
2 files changed, 21 insertions(+), 1 deletion(-)
diff --git a/Documentation/kmsg/s390/kvm b/Documentation/kmsg/s390/kvm
index 76ffe2012254..6908476a54f1 100644
--- a/Documentation/kmsg/s390/kvm
+++ b/Documentation/kmsg/s390/kvm
@@ -10,3 +10,15 @@
* If this problem persists after a reload of the kvm kernel module, gather
* Linux debug data and contact your support organization.
*/
+
+/*?
+ * Text: "Failed to initialize GIB rc=%d\n"
+ * Severity: Error
+ * Parameter:
+ * @1: return code of the GIB initialization call
+ * Description:
+ * The initialization if the GIB (Guest Information Block) was not successful.
+ * User action:
+ * If this problem persists after a reload of the kvm kernel module, gather
+ * Linux debug data and contact your support organization.
+ */
This does not exist upstream. Wrong branch?
No, not the wrong branch, wrong file. These are the very first kmsgs for
kvm and
it turns out that we defined
#define KMSG_COMPONENT "kvm-s390"
as the location.
The upstream s390 features branch does not contain a
Documentation/kmsg/ directory. IIRC this was never accepted upstream?
I wasn't aware of that but see it now! So the patch has to be broken
up...
