From: Eric Farman <farman@linux.ibm.com>
To: Heiko Carstens <hca@linux.ibm.com>,
Thomas Huth <thuth@redhat.com>, Halil Pasic <pasic@linux.ibm.com>,
Christian Borntraeger <borntraeger@linux.ibm.com>
Cc: qemu-s390x@nongnu.org, qemu-devel@nongnu.org
Subject: Re: [PATCH] s390/sclp: fix SCLP facility map
Date: Thu, 02 Nov 2023 14:50:48 -0400 [thread overview]
Message-ID: <0cb53eda95889a41d485b993003a10600a7d4424.camel@linux.ibm.com> (raw)
In-Reply-To: <20231024100703.929679-1-hca@linux.ibm.com>
(+cc qemu-devel)
On Tue, 2023-10-24 at 12:07 +0200, Heiko Carstens wrote:
> Qemu's SCLP implementation incorrectly reports that it supports CPU
> reconfiguration. If a guest issues a CPU reconfiguration request it
> is rejected as invalid command.
>
> Fix the SCLP_HAS_CPU_INFO mask, and remove the unused
> SCLP_CMDW_CONFIGURE_CPU and SCLP_CMDW_DECONFIGURE_CPU defines.
>
> Reviewed-by: Eric Farman <farman@linux.ibm.com>
> Reviewed-by: Halil Pasic <pasic@linux.ibm.com>
> Signed-off-by: Heiko Carstens <hca@linux.ibm.com>
> ---
> include/hw/s390x/sclp.h | 4 +---
> 1 file changed, 1 insertion(+), 3 deletions(-)
Thomas, any concerns? Could this get picked up for 8.2, please?
>
> diff --git a/include/hw/s390x/sclp.h b/include/hw/s390x/sclp.h
> index 9aef6d937012..b4ecd04e2341 100644
> --- a/include/hw/s390x/sclp.h
> +++ b/include/hw/s390x/sclp.h
> @@ -38,10 +38,8 @@
> #define MAX_STORAGE_INCREMENTS 1020
>
> /* CPU hotplug SCLP codes */
> -#define SCLP_HAS_CPU_INFO
> 0x0C00000000000000ULL
> +#define SCLP_HAS_CPU_INFO
> 0x0800000000000000ULL
> #define SCLP_CMDW_READ_CPU_INFO 0x00010001
> -#define SCLP_CMDW_CONFIGURE_CPU 0x00110001
> -#define SCLP_CMDW_DECONFIGURE_CPU 0x00100001
>
> /* SCLP PCI codes */
> #define SCLP_HAS_IOA_RECONFIG
> 0x0000000040000000ULL
next parent reply other threads:[~2023-11-02 18:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20231024100703.929679-1-hca@linux.ibm.com>
2023-11-02 18:50 ` Eric Farman [this message]
2023-11-07 9:45 ` [PATCH] s390/sclp: fix SCLP facility map Thomas Huth
2023-11-07 13:57 ` Eric Farman
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=0cb53eda95889a41d485b993003a10600a7d4424.camel@linux.ibm.com \
--to=farman@linux.ibm.com \
--cc=borntraeger@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=pasic@linux.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
--cc=thuth@redhat.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).