All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Liran Alon <liran.alon@oracle.com>
Cc: ehabkost@redhat.com, qemu-devel@nongnu.org, pbonzini@redhat.com,
	elad.gabay@oracle.com, imammedo@redhat.com, rth@twiddle.net
Subject: Re: [PATCH] acpi: Add Windows ACPI Emulated Device Table (WAET)
Date: Thu, 12 Mar 2020 02:27:30 -0400	[thread overview]
Message-ID: <20200312021332-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <f746828c-0a15-2613-a6bf-300750be1be5@oracle.com>

On Thu, Mar 12, 2020 at 03:31:49AM +0200, Liran Alon wrote:
> 
> On 11/03/2020 22:24, Michael S. Tsirkin wrote:
> > Notice the process as documented in ./tests/qtest/bios-tables-test.c
> > 
> Thanks for explicitly pointing me to that process.
> 
> I have followed the process described there (Both steps 1-3 and steps 4-7).
> On step (6), I have noted that many existing ACPI tables don't have expected
> binaries for all the execution-matrix.
> E.g. tests/data/acpi/pc/APIC.{bridge, ipmikcs, memhp, numamem} are all
> missing.
> Similar missing files exists for FACP, FACS, HPET and MCFG.
> 
> I should add for WAET the expected binaries for all the execution-matrix
> right?
> Is it just an existing issue that for the existing tables some of the
> expected binaries are missing? But the tests seems to pass.
> Can you clarify this for me?
> 
> Thanks,
> -Liran

It's because of this (which we should probably rewrite as a loop):

try_again:
        aml_file = g_strdup_printf("%s/%s/%.4s%s", data_dir, data->machine,
                                   sdt->aml, ext);
        if (getenv("V")) {
            fprintf(stderr, "Looking for expected file '%s'\n", aml_file);
        }
        if (g_file_test(aml_file, G_FILE_TEST_EXISTS)) {
            exp_sdt.aml_file = aml_file;
        } else if (*ext != '\0') {
            /* try fallback to generic (extension less) expected file */
            ext = "";
            g_free(aml_file);
            goto try_again;
        }

if WAET is always added, then a single WAET will be enough for you.

-- 
MST



  reply	other threads:[~2020-03-12  6:28 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-11 17:08 [PATCH] acpi: Add Windows ACPI Emulated Device Table (WAET) Liran Alon
2020-03-11 18:59 ` no-reply
2020-03-11 19:08   ` Liran Alon
2020-03-11 20:24     ` Michael S. Tsirkin
2020-03-12  1:31       ` Liran Alon
2020-03-12  6:27         ` Michael S. Tsirkin [this message]
2020-03-11 19:00 ` no-reply
2020-03-11 20:36 ` Michael S. Tsirkin
2020-03-11 23:20   ` Liran Alon
2020-03-12  6:12     ` Michael S. Tsirkin
2020-03-12 11:30       ` Liran Alon
2020-03-12 12:19         ` Michael S. Tsirkin
2020-03-12 12:55           ` Liran Alon
2020-03-12 16:35             ` Igor Mammedov
2020-03-12 18:48               ` Liran Alon
2020-03-13  9:35                 ` Igor Mammedov
2020-03-12 16:27 ` Igor Mammedov
2020-03-12 17:09   ` Michael S. Tsirkin
2020-03-13  9:36     ` Igor Mammedov
2020-03-13 15:26       ` Michael S. Tsirkin
2020-03-16 13:26         ` Igor Mammedov
2020-03-12 17:28   ` Liran Alon
2020-03-12 19:47     ` Michael S. Tsirkin
2020-03-12 21:17       ` Liran Alon
2020-03-13 10:05     ` Igor Mammedov
2020-03-13 14:23       ` Liran Alon

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=20200312021332-mutt-send-email-mst@kernel.org \
    --to=mst@redhat.com \
    --cc=ehabkost@redhat.com \
    --cc=elad.gabay@oracle.com \
    --cc=imammedo@redhat.com \
    --cc=liran.alon@oracle.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=rth@twiddle.net \
    /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.