From: "Michael S. Tsirkin" <mst@redhat.com>
To: Ani Sinha <ani@anisinha.ca>
Cc: imammedo@redhat.com, qemu-devel@nongnu.org, liavalb@gmail.com
Subject: Re: [PATCH v7 0/4] hw/acpi: add indication for i8042 in IA-PC boot flags of the FADT table
Date: Sun, 6 Mar 2022 16:36:34 -0500 [thread overview]
Message-ID: <20220306163605-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20220304154032.2071585-1-ani@anisinha.ca>
On Fri, Mar 04, 2022 at 09:10:28PM +0530, Ani Sinha wrote:
> 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.
I wonder how will such a guest work on an existing qemu release then.
> Changelog:
> v7:
> fixed a compilation issue. the fix was not committed when running "make check"
> v6:
> addressed comments from v5. added microvm changes too as a part of this series.
> v5:
> Addressed review comments from v4. Also got rid of microvm changes. Will send
> them in a separate patch.
>
>
>
> Ani Sinha (1):
> hw/acpi/microvm: turn on 8042 bit in FADT boot architecture flags if
> present
>
> 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 | 8 +++++++-
> hw/i386/acpi-build.c | 8 ++++++++
> hw/i386/acpi-microvm.c | 6 ++++++
> include/hw/acpi/acpi-defs.h | 1 +
> include/hw/input/i8042.h | 15 +++++++++++++++
> 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
> 9 files changed, 37 insertions(+), 1 deletion(-)
>
> --
> 2.25.1
next prev parent reply other threads:[~2022-03-06 21:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-04 15:40 [PATCH v7 0/4] hw/acpi: add indication for i8042 in IA-PC boot flags of the FADT table Ani Sinha
2022-03-04 15:40 ` [PATCH v7 1/4] tests/acpi: i386: allow FACP acpi table changes Ani Sinha
2022-03-04 15:40 ` [PATCH v7 2/4] hw/acpi: add indication for i8042 in IA-PC boot flags of the FADT table Ani Sinha
2022-03-06 10:36 ` Michael S. Tsirkin
2022-03-06 14:26 ` Ani Sinha
2022-03-07 11:12 ` Igor Mammedov
2022-03-04 15:40 ` [PATCH v7 3/4] tests/acpi: i386: update FACP table differences Ani Sinha
2022-03-04 15:40 ` [PATCH v7 4/4] hw/acpi/microvm: turn on 8042 bit in FADT boot architecture flags if present Ani Sinha
2022-03-06 21:36 ` Michael S. Tsirkin [this message]
2022-03-07 3:43 ` [PATCH v7 0/4] hw/acpi: add indication for i8042 in IA-PC boot flags of the FADT table 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=20220306163605-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=ani@anisinha.ca \
--cc=imammedo@redhat.com \
--cc=liavalb@gmail.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).