From: Ani Sinha <anisinha@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: "Michael S. Tsirkin" <mst@redhat.com>,
"Alex Bennée" <alex.bennee@linaro.org>,
"Igor Mammedov" <imammedo@redhat.com>,
qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [PATCH] acpi/tests/bios-tables-test: add an environment variable for iasl location
Date: Sat, 20 May 2023 20:43:01 +0530 [thread overview]
Message-ID: <31DC243F-BA0D-48B8-9CC3-43982DDB9535@redhat.com> (raw)
In-Reply-To: <CABgObfZb7L3-7xrayi2X1pUOHVmsyxj5D8fLg2nTh86Fef1YvQ@mail.gmail.com>
> On 20-May-2023, at 3:06 PM, Paolo Bonzini <pbonzini@redhat.com> wrote:
>
>
>
> Il sab 20 mag 2023, 09:25 Ani Sinha <anisinha@redhat.com> ha scritto:
> 40c909f534e3f3cd2 from what I can see. It requires a full QEMU build in order to turn on CONFIG_IASL in bios-tables-test. At some point in the past, we could just install iasl and rerun the test and it would discover iasl in the path if CONFIG_IASL was not defined.
>
> So you want CONFIG_IASL to *not* have the full path if you configure with --iasl=iasl?
Iasl is *not* a mandatory tool to run that test. So we do not want any configure option at all. It is absolutely not needed and makes the entire workflow more burdensome.
>
> Paolo
>
>
> I have proposed a patch with the title "acpi/tests/bios-tables-test: pass iasl path through environment variable”.
> I have tested possible scenarios and it would satisfy my uneasiness. One thing I could not find is how to discover OS environment variable from meson.build. From what I could gather, currently it is not supported. Hence, when both CONFIG_IASL is passed from the command line and meson discovers one of its own, the meson one would be enforced and not the one developer passed.
>
>
next prev parent reply other threads:[~2023-05-20 15:13 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-17 12:07 [PATCH] acpi/tests/bios-tables-test: add an environment variable for iasl location Ani Sinha
2023-05-17 14:17 ` Michael S. Tsirkin
2023-05-17 14:27 ` Ani Sinha
2023-05-17 14:36 ` Michael S. Tsirkin
2023-05-17 14:49 ` Ani Sinha
2023-05-17 15:16 ` Alex Bennée
2023-05-17 15:25 ` Michael S. Tsirkin
2023-05-17 15:58 ` Alex Bennée
2023-05-17 16:07 ` Michael S. Tsirkin
2023-05-17 16:20 ` Alex Bennée
2023-05-18 6:01 ` Ani Sinha
2023-05-18 10:40 ` Michael S. Tsirkin
2023-05-18 11:01 ` Ani Sinha
2023-05-19 17:13 ` Paolo Bonzini
2023-05-20 7:25 ` Ani Sinha
2023-05-20 9:36 ` Paolo Bonzini
2023-05-20 15:13 ` Ani Sinha [this message]
2023-05-22 10:21 ` Paolo Bonzini
2023-05-18 11:19 ` Ani Sinha
2023-05-18 6:11 ` Ani Sinha
2023-05-17 15:48 ` Ani Sinha
2023-05-17 16:07 ` Alex Bennée
2023-05-17 16:43 ` Bernhard Beschow
2023-05-18 5:55 ` Ani Sinha
2023-05-18 10:27 ` Michael S. Tsirkin
2023-05-21 8:54 ` Michael S. Tsirkin
2023-05-21 14:51 ` Ani Sinha
2023-05-22 10:34 ` Ani Sinha
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=31DC243F-BA0D-48B8-9CC3-43982DDB9535@redhat.com \
--to=anisinha@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=imammedo@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
/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).