qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Nina Schoetterl-Glausch <nsg@linux.ibm.com>
To: Thomas Huth <thuth@redhat.com>,
	Shalini Chellathurai Saroja <shalini@linux.ibm.com>,
	qemu-s390x mailing list <qemu-s390x@nongnu.org>
Cc: qemu-devel mailing list <qemu-devel@nongnu.org>,
	Hendrik Brueckner <brueckner@linux.ibm.com>
Subject: Re: [PATCH qemu v2 2/3] hw/s390x: add SCLP event type CPI
Date: Wed, 05 Mar 2025 20:00:28 +0100	[thread overview]
Message-ID: <dd6a3b1487abdb16202d435aa1f8d8c34454b0bc.camel@linux.ibm.com> (raw)
In-Reply-To: <01508dbb-7ee5-4c5b-87c9-667bc296fdbf@redhat.com>

On Wed, 2025-03-05 at 19:04 +0100, Thomas Huth wrote:

[...]

> > +
> > +static int write_event_data(SCLPEvent *event, EventBufferHeader *evt_buf_hdr)
> > +{
> > +    ControlProgramIdMsg *cpi = container_of(evt_buf_hdr, ControlProgramIdMsg,
> > +                                            ebh);
> > +    S390CcwMachineState *ms = S390_CCW_MACHINE(qdev_get_machine());
> > +
> > +    ascii_put(ms->cpi.system_type, (char *)cpi->data.system_type, 8);
> > +    ascii_put(ms->cpi.system_name, (char *)cpi->data.system_name, 8);
> > +    ascii_put(ms->cpi.sysplex_name, (char *)cpi->data.sysplex_name, 8);
> > +    ms->cpi.system_level = be64_to_cpu(cpi->data.system_level);
> 
> Can we be confident that system_level is always properly aligned?

It has offset 40 from the start of a heap allocation, so yes, but it is far
from obvious so I wouldn't mind ldq_be_p.

> Otherwise it's maybe better to use ldq_be_p() instead?
> 
>   Thomas
> 
> 

-- 
IBM Deutschland Research & Development GmbH
Vorsitzender des Aufsichtsrats: Wolfgang Wendt
Geschäftsführung: David Faller
Sitz der Gesellschaft: Böblingen / Registergericht: Amtsgericht Stuttgart, HRB 243294


  reply	other threads:[~2025-03-05 19:02 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-24 12:04 [PATCH qemu v2 1/3] hw/s390x: add CPI identifiers to QOM Shalini Chellathurai Saroja
2025-02-24 12:04 ` [PATCH qemu v2 2/3] hw/s390x: add SCLP event type CPI Shalini Chellathurai Saroja
2025-03-05 18:04   ` Thomas Huth
2025-03-05 19:00     ` Nina Schoetterl-Glausch [this message]
2025-03-06  8:07       ` shalini
2025-03-06  8:04     ` shalini
2025-02-24 12:04 ` [PATCH qemu v2 3/3] hw/s390x: support migration of CPI values Shalini Chellathurai Saroja
2025-03-05 18:33   ` Thomas Huth
2025-03-06 14:10     ` shalini
2025-03-06 15:08       ` Thomas Huth
2025-03-07  8:04         ` Shalini Chellathurai Saroja
2025-03-07 15:29     ` Shalini Chellathurai Saroja
2025-03-05 15:56 ` [PATCH qemu v2 1/3] hw/s390x: add CPI identifiers to QOM Thomas Huth
2025-03-06 12:23   ` shalini
2025-03-06 14:55     ` Thomas Huth
2025-03-06 15:44       ` Nina Schoetterl-Glausch
2025-03-06 16:05         ` Daniel P. Berrangé
2025-03-10 15:16           ` Shalini Chellathurai Saroja
2025-03-05 16:06 ` Daniel P. Berrangé
2025-03-06 13:55   ` shalini
2025-03-06 15:06     ` Daniel P. Berrangé
2025-03-06 15:36       ` Nina Schoetterl-Glausch
2025-03-07 15:22       ` Shalini Chellathurai Saroja
2025-03-05 18:05 ` Thomas Huth
2025-03-06 13:57   ` shalini

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=dd6a3b1487abdb16202d435aa1f8d8c34454b0bc.camel@linux.ibm.com \
    --to=nsg@linux.ibm.com \
    --cc=brueckner@linux.ibm.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-s390x@nongnu.org \
    --cc=shalini@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 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).