qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Liav Albani <liavalb@gmail.com>
To: Ani Sinha <ani@anisinha.ca>, Igor Mammedov <imammedo@redhat.com>
Cc: shentey@gmail.com, qemu-devel@nongnu.org, mst@redhat.com
Subject: Re: [PATCH v4 2/3] hw/acpi: add indication for i8042 in IA-PC boot flags of the FADT table
Date: Tue, 1 Mar 2022 21:20:57 +0200	[thread overview]
Message-ID: <3face56c-7488-6736-6394-af1d9979d00f@gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.22.394.2203011514030.1522204@anisinha-lenovo>


On 3/1/22 11:52, Ani Sinha wrote:
>
> On Tue, 1 Mar 2022, Igor Mammedov wrote:
>
>> On Mon, 28 Feb 2022 22:17:32 +0200
>> Liav Albani <liavalb@gmail.com> 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.
>>>
>>> This change only applies to the x86/q35 machine type, as it uses FACP
>>> ACPI table with revision higher than 1, which should implement at least
>>> ACPI 2.0 features within the table, hence it can also set the IA-PC boot
>>> flags register according to the ACPI 2.0 specification.
>>>
>>> Signed-off-by: Liav Albani <liavalb@gmail.com>
>>> ---
>>>   hw/acpi/aml-build.c         | 11 ++++++++++-
>>>   hw/i386/acpi-build.c        |  9 +++++++++
>>>   hw/i386/acpi-microvm.c      |  9 +++++++++
>> commit message says it's q35 specific, so wy it touched microvm anc piix4?
> Igor is correct. Although I see that currently there are no 8042 devices
> for microvms, maybe we should be conservative and add the code to detect
> the device anyway. In that case, the change could affect microvms too when
> such devices get added in the future.
>
>
> echo -e "info qtree\r\nquit\r\n" | ./qemu-system-x86_64 -machine microvm
> -monitor stdio 2>/dev/null | grep 8042
>
> <empty>

What about this?

echo -e "info qtree\r\nquit\r\n" | qemu-system-x86_64 -machine microvm 
-device i8042 -monitor stdio 2>/dev/null | grep 8042

Or this?

echo -e "info mtree\r\nquit\r\n" | qemu-system-x86_64 -machine microvm 
-device i8042 -monitor stdio 2>/dev/null | grep 8042

>


  parent reply	other threads:[~2022-03-01 19:51 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-28 20:17 [PATCH v4 0/3] hw/acpi: add indication for i8042 in IA-PC boot flags of the FADT table Liav Albani
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 [this message]
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=3face56c-7488-6736-6394-af1d9979d00f@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).