From: Igor Mammedov <imammedo@redhat.com>
To: Roman Kagan <rkagan@virtuozzo.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
Eduardo Habkost <ehabkost@redhat.com>,
qemu-block@nongnu.org, "Michael S. Tsirkin" <mst@redhat.com>,
qemu-stable@nongnu.org, qemu-devel@nongnu.org,
Paolo Bonzini <pbonzini@redhat.com>, John Snow <jsnow@redhat.com>,
Richard Henderson <rth@twiddle.net>
Subject: Re: [Qemu-devel] [PATCH v4 0/4] i386: expose floppy-related objects in SSDT
Date: Tue, 29 Dec 2015 15:09:36 +0100 [thread overview]
Message-ID: <20151229150936.53a6e4bf@nial.brq.redhat.com> (raw)
In-Reply-To: <1451055852-30910-1-git-send-email-rkagan@virtuozzo.com>
On Fri, 25 Dec 2015 18:04:08 +0300
Roman Kagan <rkagan@virtuozzo.com> wrote:
> Windows on UEFI systems is only capable of detecting the presence and
> the type of floppy drives via corresponding ACPI objects.
>
> Those objects are added in the last patch of the series; the three
> preceding ones pave the way to it, by making the necessary data
> public and by moving the whole floppy drive controller description into
> runtime-generated SSDT.
>
> Note that the series conflicts with Igor's patchset for dynamic DSDT, in
> particular, with "[PATCH 50/74] pc: acpi: move FDC0 device from DSDT
> to SSDT"; I haven't managed to avoid that while trying to meet
> maintainer's comments.
To remove conflicts and to make it more suitable for stable, I'd drop
"2/4 i386/acpi: make floppy controller object dynamic"
and split test blob out of
"4/4 i386: populate floppy drive information in SSDT"
into a separate patch so one can see effects of applying 4/4
and then update blobs if resulting ASL diff is as expected.
>
> Roman Kagan (4):
> i386/pc: expose identifying the floppy controller
> i386/acpi: make floppy controller object dynamic
> expose floppy drive geometry and CMOS type
> i386: populate floppy drive information in SSDT
>
> Signed-off-by: Roman Kagan <rkagan@virtuozzo.com>
> Cc: "Michael S. Tsirkin" <mst@redhat.com>
> Cc: Eduardo Habkost <ehabkost@redhat.com>
> Cc: Igor Mammedov <imammedo@redhat.com>
> Cc: John Snow <jsnow@redhat.com>
> Cc: Kevin Wolf <kwolf@redhat.com>
> Cc: Paolo Bonzini <pbonzini@redhat.com>
> Cc: Richard Henderson <rth@twiddle.net>
> Cc: qemu-block@nongnu.org
> Cc: qemu-stable@nongnu.org
> ---
> changes since v3:
> - make FDC object fully dynamic in a separate patch
> - split out support patches
> - include test data updates with the respective patches to maintain
> bisectability
>
> changes since v2:
> - explicit endianness for buffer data
> - reorder code to reduce conflicts with dynamic DSDT patchset
> - update test data
>
>
> hw/block/fdc.c | 11 +++++
> hw/i386/acpi-build.c | 92 ++++++++++++++++++++++++++++++++++++
> hw/i386/acpi-dsdt-isa.dsl | 18 -------
> hw/i386/acpi-dsdt.dsl | 1 -
> hw/i386/pc.c | 46 ++++++++++--------
> hw/i386/q35-acpi-dsdt.dsl | 7 +--
> include/hw/block/fdc.h | 2 +
> include/hw/i386/pc.h | 3 ++
> tests/acpi-test-data/pc/DSDT | Bin 3028 -> 2946 bytes
> tests/acpi-test-data/pc/SSDT | Bin 2486 -> 2635 bytes
> tests/acpi-test-data/pc/SSDT.bridge | Bin 4345 -> 4494 bytes
> tests/acpi-test-data/q35/DSDT | Bin 7666 -> 7578 bytes
> 12 files changed, 137 insertions(+), 43 deletions(-)
>
next prev parent reply other threads:[~2015-12-29 14:09 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-25 15:04 [Qemu-devel] [PATCH v4 0/4] i386: expose floppy-related objects in SSDT Roman Kagan
2015-12-25 15:04 ` [Qemu-devel] [PATCH v4 1/4] i386/pc: expose identifying the floppy controller Roman Kagan
2015-12-25 15:04 ` [Qemu-devel] [PATCH v4 2/4] i386/acpi: make floppy controller object dynamic Roman Kagan
2015-12-25 15:04 ` [Qemu-devel] [PATCH v4 3/4] expose floppy drive geometry and CMOS type Roman Kagan
2015-12-25 15:04 ` [Qemu-devel] [PATCH v4 4/4] i386: populate floppy drive information in SSDT Roman Kagan
2015-12-29 14:09 ` Igor Mammedov [this message]
2015-12-29 16:17 ` [Qemu-devel] [PATCH v4 0/4] i386: expose floppy-related objects " Roman Kagan
2015-12-29 16:27 ` Igor Mammedov
2015-12-29 16:42 ` Michael S. Tsirkin
-- strict thread matches above, loose matches on Subject: below --
2015-12-16 7:45 [Qemu-devel] [PATCH v2 1/1] " Denis V. Lunev
2015-12-16 16:46 ` John Snow
2015-12-16 16:46 ` Igor Mammedov
2015-12-16 17:34 ` Roman Kagan
2015-12-16 22:15 ` Igor Mammedov
2015-12-17 13:26 ` Roman Kagan
2015-12-17 17:08 ` Igor Mammedov
2015-12-18 19:32 ` [Qemu-devel] [PATCH v3 0/2] " Roman Kagan
2015-12-18 19:32 ` [Qemu-devel] [PATCH v3 1/2] " Roman Kagan
2015-12-22 15:07 ` Michael S. Tsirkin
2015-12-22 15:13 ` Roman Kagan
2015-12-22 15:56 ` Igor Mammedov
2015-12-18 19:32 ` [Qemu-devel] [PATCH v3 2/2] tests: update expected SSDT for floppy changes Roman Kagan
2015-12-22 16:41 ` Michael S. Tsirkin
2015-12-23 13:08 ` Roman Kagan
2015-12-23 13:45 ` Michael S. Tsirkin
2015-12-23 15:06 ` Roman Kagan
2015-12-23 17:20 ` Roman Kagan
2015-12-23 17:47 ` Igor Mammedov
2015-12-23 17:51 ` Roman Kagan
2015-12-24 6:17 ` Michael S. Tsirkin
2015-12-25 15:25 ` Roman Kagan
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=20151229150936.53a6e4bf@nial.brq.redhat.com \
--to=imammedo@redhat.com \
--cc=ehabkost@redhat.com \
--cc=jsnow@redhat.com \
--cc=kwolf@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@nongnu.org \
--cc=rkagan@virtuozzo.com \
--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 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).