patches and low-level development discussion
 help / color / mirror / code / Atom feed
From: Demi Marie Obenour <demiobenour@gmail.com>
To: Alyssa Ross <hi@alyssa.is>
Cc: Spectrum OS Development <devel@spectrum-os.org>
Subject: Re: [PATCH 1/4] scripts/run-qemu.sh: better error checks & formatting
Date: Thu, 13 Nov 2025 10:36:12 -0500	[thread overview]
Message-ID: <57488ef1-722f-4e91-808c-c875fbc59a63@gmail.com> (raw)
In-Reply-To: <87v7jeglzi.fsf@alyssa.is>


[-- Attachment #1.1.1: Type: text/plain, Size: 2345 bytes --]

On 11/13/25 07:23, Alyssa Ross wrote:
> Demi Marie Obenour <demiobenour@gmail.com> writes:
> 
>> No other functional change intended.
>>
>> Signed-off-by: Demi Marie Obenour <demiobenour@gmail.com>
>> ---
>>  scripts/run-qemu.sh | 24 ++++++++++++++----------
>>  1 file changed, 14 insertions(+), 10 deletions(-)
> 
> This is a lot of changes all in one, without individual explanation.
> I'd appreciate it if they could be broken up and explained, because I'm
> going to have to ask what the purpose of each change is.
> 
>> diff --git a/scripts/run-qemu.sh b/scripts/run-qemu.sh
>> index 64fd29259ab108bc547cb7c74623ae9dc288b3b7..9c6c8193bbeba5916038c82d8f76992051719c19 100755
>> --- a/scripts/run-qemu.sh
>> +++ b/scripts/run-qemu.sh
>> @@ -1,11 +1,15 @@
>> -#!/bin/sh -ue
>> +#!/bin/sh --
> 
> The idea here is to be robust against the script being invoked with
> argv[0] set to "-c" or something?

Correct.

>>  # SPDX-FileCopyrightText: 2023-2025 Alyssa Ross <hi@alyssa.is>
>>  # SPDX-License-Identifier: EUPL-1.2+
>>  
>>  # This script wraps around QEMU to paper over platform differences,
>>  # which can't be handled portably in Make language.
>> +set -uef
> 
> Adding -f makes sense.
> 
>> +if [ -n ${ARCH+test} ]; then
>> +	ARCH=$(uname -m)
>> +fi
>>  
>> -case "${ARCH:="$(uname -m)"}" in
>> +case $ARCH in
>>  	aarch64)
>>  		machine=virt,accel=kvm:tcg,gic-version=3,iommu=smmuv3
>>  		;;
> 
> Why is this better?

If uname exits with a non-zero status, the script will exit rather
than continuing.

>> @@ -17,13 +21,13 @@ case "${ARCH:="$(uname -m)"}" in
>>  esac
>>  
>>  i=0
>> -while [ $i -lt $# ]; do
>> -	arg="$1"
>> +while [ "$i" -lt "$#" ]; do
>> +	arg=$1
>>  	shift
>>  
>> -	case "$arg" in
>> +	case $arg in
>>  		-append)
> 
> Makes sense as long as we're consistent about it.  I wonder if we could
> get the formatter to do this.

+1

>> -			set -- "$@" -append "${append:+$append }$1"
>> +			set -- "$@" -append ${append:+"$append "}"$1"
>>  			i=$((i + 2))
>>  			shift
>>  			continue
> 
> Don't understand this one.  We've gone from one set of quotes to two
> sequential ones.

I remember reading that the first version might not conform to POSIX.
I'm not sure if it matters though.
-- 
Sincerely,
Demi Marie Obenour (she/her/hers)

[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 7253 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2025-11-13 15:36 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-08  3:41 [PATCH 0/4] Minor improvements to scripts/run-qemu.sh Demi Marie Obenour
2025-11-08  3:41 ` [PATCH 1/4] scripts/run-qemu.sh: better error checks & formatting Demi Marie Obenour
2025-11-09 11:28   ` Alyssa Ross
2025-11-13 12:23   ` Alyssa Ross
2025-11-13 15:36     ` Demi Marie Obenour [this message]
2025-11-13 16:56       ` Alyssa Ross
2025-11-13 19:29         ` Demi Marie Obenour
2025-11-08  3:41 ` [PATCH 2/4] scripts/run-qemu.sh: decrease indentation Demi Marie Obenour
2025-11-08  3:41 ` [PATCH 3/4] scripts/run-qemu.sh: Preserve ,, in QEMU arguments Demi Marie Obenour
2025-11-13 12:28   ` Alyssa Ross
2025-11-13 15:36     ` Demi Marie Obenour
2025-11-13 19:30     ` Demi Marie Obenour
2025-11-08  3:41 ` [PATCH 4/4] scripts/run-qemu.sh: Unset variables from the environment Demi Marie Obenour
2025-11-13 12:27   ` Alyssa Ross
2025-11-13 19:30     ` Demi Marie Obenour
2025-11-14 11:22   ` Alyssa Ross

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=57488ef1-722f-4e91-808c-c875fbc59a63@gmail.com \
    --to=demiobenour@gmail.com \
    --cc=devel@spectrum-os.org \
    --cc=hi@alyssa.is \
    /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.
Code repositories for project(s) associated with this public inbox

	https://spectrum-os.org/git/crosvm
	https://spectrum-os.org/git/doc
	https://spectrum-os.org/git/mktuntap
	https://spectrum-os.org/git/nixpkgs
	https://spectrum-os.org/git/spectrum
	https://spectrum-os.org/git/ucspi-vsock
	https://spectrum-os.org/git/www

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).