From patchwork Wed Feb 2 17:21:36 2022 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Frank Heimes X-Patchwork-Id: 1587730 Return-Path: X-Original-To: incoming@patchwork.ozlabs.org Delivered-To: patchwork-incoming@bilbo.ozlabs.org Authentication-Results: bilbo.ozlabs.org; dkim=fail reason="signature verification failed" (2048-bit key; unprotected) header.d=canonical.com header.i=@canonical.com header.a=rsa-sha256 header.s=20210705 header.b=Z8kTRb1S; dkim-atps=neutral Authentication-Results: ozlabs.org; spf=none (no SPF record) smtp.mailfrom=lists.ubuntu.com (client-ip=91.189.94.19; helo=huckleberry.canonical.com; envelope-from=kernel-team-bounces@lists.ubuntu.com; receiver=) Received: from huckleberry.canonical.com (huckleberry.canonical.com [91.189.94.19]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by bilbo.ozlabs.org (Postfix) with ESMTPS id 4JppWh2X78z9s8s for ; Thu, 3 Feb 2022 04:22:07 +1100 (AEDT) Received: from localhost ([127.0.0.1] helo=huckleberry.canonical.com) by huckleberry.canonical.com with esmtp (Exim 4.86_2) (envelope-from ) id 1nFJKR-0004TT-Qe; Wed, 02 Feb 2022 17:21:59 +0000 Received: from smtp-relay-canonical-0.internal ([10.131.114.83] helo=smtp-relay-canonical-0.canonical.com) by huckleberry.canonical.com with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.86_2) (envelope-from ) id 1nFJKQ-0004TM-Ot for kernel-team@lists.ubuntu.com; Wed, 02 Feb 2022 17:21:58 +0000 Received: from T570.fritz.box (p5dce27a2.dip0.t-ipconnect.de [93.206.39.162]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by smtp-relay-canonical-0.canonical.com (Postfix) with ESMTPSA id D4AD240E01 for ; Wed, 2 Feb 2022 17:21:57 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=canonical.com; s=20210705; t=1643822517; bh=AiGVXMDt9EV4BrU0eFdhyEQvxAcUDUATinJ/JH5vxmM=; h=From:To:Subject:Date:Message-Id:MIME-Version; b=Z8kTRb1S60cO8bIEWfPPpwqYfyvsf88/ZvGvrUOl8Q+eOxg87ToNmX9GkfROpIpVL 3mjY04va6nKZYs1UwCnsXAzaObslLxSMwMmKwgdUnJN8A67LE16cjSBgkJ6D2naY+a m5d8WI5oqUYIzJhN7zLpElSYIMXZEjmqU8ZaOR3MZlHkJmvFqgSB6pifLwYh9kW/VW WmabRMyofV6bdJvRKN3H3AS8qQF/bDOxMJk2KZuAZQVmx1SrR54oxOfdKNya5hYTLV p9L/U8DheRqZ7K0i+/LSYeLgpwU3HSQPKtvAxzEoZzmIAZxi/wat4rW1qolbgMqCAX V0DgtHGnWLikg== From: frank.heimes@canonical.com To: kernel-team@lists.ubuntu.com Subject: [J][PATCH 0/2] KVM: Improve SIGP architectural compliance (LP: 1959735) Date: Wed, 2 Feb 2022 18:21:36 +0100 Message-Id: <20220202172138.411440-1-frank.heimes@canonical.com> X-Mailer: git-send-email 2.25.1 MIME-Version: 1.0 X-BeenThere: kernel-team@lists.ubuntu.com X-Mailman-Version: 2.1.20 Precedence: list List-Id: Kernel team discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: kernel-team-bounces@lists.ubuntu.com Sender: "kernel-team" BugLink: https://bugs.launchpad.net/bugs/1959735 Linux as a guest operating system often doesn't have as stringent requirements to architectural compliance as traditional operating systems that rely on it. Specifically, KVM implements the SIGP RESTART in a non-compliant way, as it reports a CPU state to be stopped after SIGP RESTART was issued, while it should report a busy condition until the CPU is really started. This feature covers the necessary fixes/improvements to KVM SIGP processing. Eric Farman (2): KVM: s390: Add a routine for setting userspace CPU state KVM: s390: Simplify SIGP Set Arch handling arch/s390/kvm/kvm-s390.c | 6 +++--- arch/s390/kvm/kvm-s390.h | 9 +++++++++ arch/s390/kvm/sigp.c | 14 +------------- 3 files changed, 13 insertions(+), 16 deletions(-)