From: Liav Albani <liavalb@gmail.com>
To: qemu-devel@nongnu.org
Cc: ani@anisinha.ca, imammedo@redhat.com, shentey@gmail.com,
Liav Albani <liavalb@gmail.com>,
mst@redhat.com
Subject: [PATCH v4 0/3] hw/acpi: add indication for i8042 in IA-PC boot flags of the FADT table
Date: Mon, 28 Feb 2022 22:17:30 +0200 [thread overview]
Message-ID: <20220228201733.714580-1-liavalb@gmail.com> (raw)
This can allow the guest OS to determine more easily if i8042 controller
is present in the system or not, so it doesn't need to do probing of the
controller, but just initialize it immediately, before enumerating the
ACPI AML namespace.
To allow "flexible" indication, I don't hardcode the bit at location 1
as on in the IA-PC boot flags, but try to search for i8042 on the ISA
bus to verify it exists in the system.
Why this is useful you might ask - this patch allows the guest OS to
probe and use the i8042 controller without decoding the ACPI AML blob
at all. For example, as a developer of the SerenityOS kernel, I might
want to allow people to not try to decode the ACPI AML namespace (for
now, we still don't support ACPI AML as it's a work in progress), but
still to not probe for the i8042 but just use it after looking in the
IA-PC boot flags in the ACPI FADT table.
Liav Albani (3):
tests/acpi: i386: allow FACP acpi table changes
hw/acpi: add indication for i8042 in IA-PC boot flags of the FADT
table
tests/acpi: i386: update FACP table differences
hw/acpi/aml-build.c | 11 ++++++++++-
hw/i386/acpi-build.c | 9 +++++++++
hw/i386/acpi-microvm.c | 9 +++++++++
include/hw/acpi/acpi-defs.h | 1 +
tests/data/acpi/q35/FACP | Bin 244 -> 244 bytes
tests/data/acpi/q35/FACP.nosmm | Bin 244 -> 244 bytes
tests/data/acpi/q35/FACP.slic | Bin 244 -> 244 bytes
tests/data/acpi/q35/FACP.xapic | Bin 244 -> 244 bytes
8 files changed, 29 insertions(+), 1 deletion(-)
--
2.35.1
next reply other threads:[~2022-02-28 20:19 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-28 20:17 Liav Albani [this message]
2022-02-28 20:17 ` [PATCH v4 1/3] tests/acpi: i386: allow FACP acpi table changes Liav Albani
2022-03-01 2:55 ` Ani Sinha
2022-02-28 20:17 ` [PATCH v4 2/3] hw/acpi: add indication for i8042 in IA-PC boot flags of the FADT table Liav Albani
2022-03-01 2:59 ` Ani Sinha
2022-03-01 8:48 ` Igor Mammedov
2022-03-01 8:43 ` Igor Mammedov
2022-03-01 9:52 ` Ani Sinha
2022-03-01 11:51 ` Igor Mammedov
2022-03-01 19:20 ` Liav Albani
2022-03-02 5:14 ` Ani Sinha
2022-03-02 12:42 ` Michael S. Tsirkin
2022-03-02 15:43 ` Liav Albani
2022-03-02 15:51 ` Ani Sinha
2022-03-02 15:58 ` Ani Sinha
2022-03-01 11:19 ` Michael S. Tsirkin
2022-03-01 11:47 ` Igor Mammedov
2022-03-01 12:18 ` Michael S. Tsirkin
2022-03-02 15:45 ` Liav Albani
2022-03-04 10:58 ` Igor Mammedov
2022-03-01 19:11 ` Liav Albani
2022-03-02 5:12 ` Ani Sinha
2022-03-02 8:47 ` Michael S. Tsirkin
2022-02-28 20:17 ` [PATCH v4 3/3] tests/acpi: i386: update FACP table differences Liav Albani
2022-03-01 2:59 ` Ani Sinha
2022-03-01 11:21 ` Michael S. Tsirkin
2022-03-01 19:13 ` Liav Albani
2022-03-02 5:05 ` Ani Sinha
2022-03-02 8:48 ` Michael S. Tsirkin
2022-03-04 10:26 ` [PATCH v4 0/3] hw/acpi: add indication for i8042 in IA-PC boot flags of the FADT table Michael S. Tsirkin
2022-03-04 10:34 ` Ani Sinha
2022-03-04 10:39 ` Michael S. Tsirkin
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=20220228201733.714580-1-liavalb@gmail.com \
--to=liavalb@gmail.com \
--cc=ani@anisinha.ca \
--cc=imammedo@redhat.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=shentey@gmail.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;
as well as URLs for NNTP newsgroup(s).