public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Jones <andrew.jones@linux.dev>
To: Claudio Imbrenda <imbrenda@linux.ibm.com>
Cc: Nico Boehr <nrb@linux.ibm.com>,
	kvm@vger.kernel.org, frankja@linux.ibm.com, seiden@linux.ibm.com,
	nsg@linux.ibm.com, thuth@redhat.com
Subject: Re: [kvm-unit-tests PATCH v1 1/1] s390x: fix make standalone
Date: Wed, 4 Jan 2023 15:48:44 +0100	[thread overview]
Message-ID: <20230104144844.ldhurl73imixvrx2@orel> (raw)
In-Reply-To: <20230104120720.0d3490bd@p-imbrenda>

On Wed, Jan 04, 2023 at 12:07:20PM +0100, Claudio Imbrenda wrote:
> On Mon, 26 Dec 2022 19:41:12 +0100
> Andrew Jones <andrew.jones@linux.dev> wrote:
> 
> > On Wed, Dec 21, 2022 at 10:14:52AM +0100, Nico Boehr wrote:
> > > Quoting Nico Boehr (2022-12-21 09:16:51)  
> > > > Quoting Claudio Imbrenda (2022-12-20 18:55:08)  
> > > > > A recent patch broke make standalone. The function find_word is not
> > > > > available when running make standalone, replace it with a simple grep.
> > > > > 
> > > > > Reported-by: Nina Schoetterl-Glausch <nsg@linux.ibm.com>
> > > > > Fixes: 743cacf7 ("s390x: don't run migration tests under PV")
> > > > > Signed-off-by: Claudio Imbrenda <imbrenda@linux.ibm.com>  
> > > > 
> > > > I am confused why find_word would not be available in standalone, since run() in runtime.bash uses it quite a few times.
> > > > 
> > > > Not that I mind the grep, but I fear more might be broken in standalone?  
> > 
> > standalone tests don't currently include scripts/$ARCH/func.bash, which
> > may be an issue for s390x. That could be fixed, though.
> > 
> > > > 
> > > > Anyways, to get this fixed ASAP:
> > > > 
> > > > Acked-by: Nico Boehr <nrb@linux.ibm.com>  
> > > 
> > > OK, I get it now, find_word is not available during _build time_.  
> > 
> > That could be changed, but it'd need to be moved to somewhere that
> > mkstandalone.sh wants to source, which could be common.bash, but
> > then we'd need to include common.bash in the standalone tests. So,
> > a new file for find_word() would be cleaner, but that sounds like
> > overkill.
> 
> the hack I posted here was meant to be "clean enough" and
> arch-only (since we are the only ones with this issue). To be
> honest, I don't really care __how__ we fix the problem, only that we do
> fix it :)
> 
> what do you think would be the cleanest solution?

A new file, but, like I said, that may be overkill at this time.

Thanks,
drew

  parent reply	other threads:[~2023-01-04 14:49 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-20 17:55 [kvm-unit-tests PATCH v1 1/1] s390x: fix make standalone Claudio Imbrenda
2022-12-21  8:16 ` Nico Boehr
2022-12-21  9:14   ` Nico Boehr
2022-12-26 18:41     ` Andrew Jones
2023-01-03 14:04       ` Nina Schoetterl-Glausch
2023-01-03 14:29         ` Andrew Jones
2023-01-04 11:07       ` Claudio Imbrenda
2023-01-04 12:56         ` Thomas Huth
2023-01-04 14:48         ` Andrew Jones [this message]
2022-12-26 18:36 ` Andrew Jones
2023-01-04 12:52   ` Thomas Huth
2023-01-04 14:49     ` Andrew Jones
2023-01-03 14:05 ` Nina Schoetterl-Glausch

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=20230104144844.ldhurl73imixvrx2@orel \
    --to=andrew.jones@linux.dev \
    --cc=frankja@linux.ibm.com \
    --cc=imbrenda@linux.ibm.com \
    --cc=kvm@vger.kernel.org \
    --cc=nrb@linux.ibm.com \
    --cc=nsg@linux.ibm.com \
    --cc=seiden@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