From: Igor Mammedov <imammedo@redhat.com>
To: qemu-devel@nongnu.org
Cc: mst@redhat.com
Subject: Re: [Qemu-devel] [PATCH v2] tests: acpi: fix FADT not being compared to reference table
Date: Tue, 30 Jan 2018 13:55:14 +0100 [thread overview]
Message-ID: <20180130135514.065e1c6a@redhat.com> (raw)
In-Reply-To: <1516116626-195863-1-git-send-email-imammedo@redhat.com>
On Tue, 16 Jan 2018 16:30:26 +0100
Igor Mammedov <imammedo@redhat.com> wrote:
> It turns out that FADT isn't actually tested for changes
> against reference table, since it happens to be the 1st
> table in RSDT which is currently ignored.
> Fix it by making sure that all tables from RSDT are added
> to test list.
>
> NOTE: FADT contains guest allocated pointers to FACS/DSDT,
> zero them out so that possible FACS/DSDT address change
> won't affect test results.
>
> Signed-off-by: Igor Mammedov <imammedo@redhat.com>
> ---
> v2:
> - fixup FACS/DSDT pointers in FADT to avoid false test
> failure if pointers change ("Michael S. Tsirkin" <mst@redhat.com>)
ping
[...]
prev parent reply other threads:[~2018-01-30 12:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-16 15:30 [Qemu-devel] [PATCH v2] tests: acpi: fix FADT not being compared to reference table Igor Mammedov
2018-01-30 12:55 ` Igor Mammedov [this message]
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=20180130135514.065e1c6a@redhat.com \
--to=imammedo@redhat.com \
--cc=mst@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).