From: "Michael S. Tsirkin" <mst@redhat.com>
To: "Denis V. Lunev" <den@openvz.org>
Cc: Eduardo Habkost <ehabkost@redhat.com>,
qemu-devel@nongnu.org, Roman Kagan <rkagan@virtuozzo.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Igor Mammedov <imammedo@redhat.com>,
Richard Henderson <rth@twiddle.net>
Subject: Re: [Qemu-devel] [PATCH for 2.5? 1/1] DSDT: add floppy-related objects
Date: Mon, 14 Dec 2015 16:21:27 +0200 [thread overview]
Message-ID: <20151214161950-mutt-send-email-mst@redhat.com> (raw)
In-Reply-To: <566E8B39.5070202@openvz.org>
On Mon, Dec 14, 2015 at 12:26:17PM +0300, Denis V. Lunev wrote:
> On 12/14/2015 12:21 PM, Michael S. Tsirkin wrote:
> >On Mon, Dec 14, 2015 at 11:22:39AM +0300, Denis V. Lunev wrote:
> >>From: Roman Kagan <rkagan@virtuozzo.com>
> >>
> >>On x86-based systems Linux determines the presence and the type of
> >>floppy drives via a query of a CMOS field. So does SeaBIOS when
> >>populating the return data for int 0x13 function 0x08.
> >>
> >>Windows doesn't; instead, it requests this information from BIOS via int
> >>0x13/0x08 or through ACPI objects _FDE (Floppy Drive Enumerate) and _FDI
> >>(Floppy Drive Information). On UEFI systems only ACPI-based detection
> >>is supported.
> >>
> >>QEMU used not to provide those objects in its DSDT; as a result floppy
> >>drives were invisible to Windows on UEFI/OVMF.
> >>
> >>This patch implements those objects in ASL, making the ACPI interpreter
> >>query the CMOS field and populate the objects. The data values used for
> >>_FDI (which, per ACPI spec, is supposed to be equivalent to BIOS int
> >>0x13/0x08) are taken from SeaBIOS.
> >>
> >>Signed-off-by: Roman Kagan <rkagan@virtuozzo.com>
> >>Signed-off-by: Denis V. Lunev <den@openvz.org>
> >>CC: Michael S. Tsirkin <mst@redhat.com>
> >>CC: Igor Mammedov <imammedo@redhat.com>
> >>CC: Paolo Bonzini <pbonzini@redhat.com>
> >>CC: Richard Henderson <rth@twiddle.net>
> >>CC: Eduardo Habkost <ehabkost@redhat.com>
> >This is not a regression, so I'm inclined not to merge this for 2.5.
> >Pls correct me if I'm wrong.
> >
>
> this was a question actually.
>
> Yes, this is not a regression but user observable bug. The floppy
> is not available in Windows UEFI guests and it is not that easy
> to get VirtIO drivers in this case installed especially for root
> disk.
>
> Den
So it's an important patch but I don't think it's a showstopper for 2.5,
and this is too risky to merge without doing another rc.
This can go into 2.5.1 perhaps.
--
MST
next prev parent reply other threads:[~2015-12-14 14:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-14 8:22 [Qemu-devel] [PATCH for 2.5? 1/1] DSDT: add floppy-related objects Denis V. Lunev
2015-12-14 9:21 ` Michael S. Tsirkin
2015-12-14 9:26 ` Denis V. Lunev
2015-12-14 9:28 ` Paolo Bonzini
2015-12-14 9:41 ` Denis V. Lunev
2015-12-14 9:44 ` Paolo Bonzini
2015-12-14 9:49 ` Denis V. Lunev
2015-12-14 9:52 ` Paolo Bonzini
2015-12-14 14:21 ` Michael S. Tsirkin [this message]
2015-12-14 15:05 ` Igor Mammedov
2015-12-14 15:11 ` Denis V. Lunev
2015-12-14 15:27 ` Igor Mammedov
2015-12-14 15:38 ` Roman Kagan
2015-12-14 15:59 ` Igor Mammedov
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=20151214161950-mutt-send-email-mst@redhat.com \
--to=mst@redhat.com \
--cc=den@openvz.org \
--cc=ehabkost@redhat.com \
--cc=imammedo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@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).