All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Nico Boehr" <nrb@linux.ibm.com>
To: "Christoph Schlameuss" <schlameuss@linux.ibm.com>,
	<linux-s390@vger.kernel.org>
Cc: "Janosch Frank" <frankja@linux.ibm.com>,
	"Claudio Imbrenda" <imbrenda@linux.ibm.com>,
	"Nico Böhr" <nrb@linux.ibm.com>,
	"David Hildenbrand" <david@kernel.org>,
	"Thomas Huth" <thuth@redhat.com>,
	kvm@vger.kernel.org
Subject: Re: [kvm-unit-tests PATCH v2 2/5] s390x: sclp: Remove unnecessary padding from struct sclp_facilities
Date: Wed, 15 Apr 2026 13:10:12 +0200	[thread overview]
Message-ID: <DHTOKQ1LRG2N.367JA1MZ9W2DI@linux.ibm.com> (raw)
In-Reply-To: <20260324-vsie-stfle-fac-v2-2-5e52be2e4081@linux.ibm.com>

On Tue Mar 24, 2026 at 4:28 PM CET, Christoph Schlameuss wrote:
> Struct sclp_facilities is only used within the guest to keep the facility
> information. Nothing bad should happen when the struct size changes in the
> future.
>
> Suggested-by: Janosch Frank <frankja@linux.ibm.com>
> Signed-off-by: Christoph Schlameuss <schlameuss@linux.ibm.com>
> ---
>  lib/s390x/sclp.h | 1 -
>  1 file changed, 1 deletion(-)
>
> diff --git a/lib/s390x/sclp.h b/lib/s390x/sclp.h
> index 22f120d1b7ea7d1c3fe822385d0c689e5b3459fe..42a2f2e9f25a45d3ebd71729df0d9d6d93a4fb50 100644
> --- a/lib/s390x/sclp.h
> +++ b/lib/s390x/sclp.h
> @@ -132,7 +132,6 @@ struct sclp_facilities {
>  	uint64_t has_kss : 1;
>  	uint64_t has_pfmfi : 1;
>  	uint64_t has_ibs : 1;
> -	uint64_t : 64 - 15;
>  };

If I'm not mistaken this is already wrong if I did proper counting since
there are 17 bits and we only subtract 15.

Since bit fields are guaranteed to be allocated left to right (see [1], p 14),
this change makes sense.

Reviewed-by: Nico Boehr <nrb@linux.ibm.com>

[1] ELF Application Binary Interface s390x Supplement, Version 1.6

  parent reply	other threads:[~2026-04-15 11:10 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-24 15:28 [kvm-unit-tests PATCH v2 0/5] s390x: Add test for STFLE interpretive execution (format-2) Christoph Schlameuss
2026-03-24 15:28 ` [kvm-unit-tests PATCH v2 1/5] s390x: snippets: Add reset_guest() to lib Christoph Schlameuss
2026-04-15 11:00   ` Nico Boehr
2026-03-24 15:28 ` [kvm-unit-tests PATCH v2 2/5] s390x: sclp: Remove unnecessary padding from struct sclp_facilities Christoph Schlameuss
2026-03-25  9:20   ` Janosch Frank
2026-04-15 11:10   ` Nico Boehr [this message]
2026-03-24 15:28 ` [kvm-unit-tests PATCH v2 3/5] s390x: sclp: Rework sclp_facilities_setup() for simpler control flow Christoph Schlameuss
2026-04-15 11:27   ` Nico Boehr
2026-04-17 15:28     ` Christoph Schlameuss
2026-03-24 15:28 ` [kvm-unit-tests PATCH v2 4/5] s390x: sclp: Add detection of alternate STFLE facilities Christoph Schlameuss
2026-04-15 11:34   ` Nico Boehr
2026-04-17 15:28     ` Christoph Schlameuss
2026-04-21 12:52       ` Nico Boehr
2026-04-21 13:02         ` Christoph Schlameuss
2026-03-24 15:28 ` [kvm-unit-tests PATCH v2 5/5] s390x: Add test for STFLE interpretive execution (format-2) Christoph Schlameuss
2026-03-25 10:18   ` Janosch Frank
2026-04-21 11:45     ` Christoph Schlameuss

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=DHTOKQ1LRG2N.367JA1MZ9W2DI@linux.ibm.com \
    --to=nrb@linux.ibm.com \
    --cc=david@kernel.org \
    --cc=frankja@linux.ibm.com \
    --cc=imbrenda@linux.ibm.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=schlameuss@linux.ibm.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.