[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Qemu-devel] [Bug 1381846] [NEW] Data sent to parallel port in guest is
From: |
Adam Goode |
Subject: |
[Qemu-devel] [Bug 1381846] [NEW] Data sent to parallel port in guest is lost if host buffer fills up |
Date: |
Thu, 16 Oct 2014 02:49:56 -0000 |
Public bug reported:
It appears that qemu will blindly write characters out to the chardev
and drop them on the floor if a write fails with EAGAIN, without
initiating flow control (via BUSY and ACK) back to the guest. If the
host buffer is too small, or is talking to a hardware device that is too
slow, data will be lost.
I notice this problem when I run a DOS program with this on the qemu command
line:
-parallel /dev/usb/lp0
I can work around this problem by buffering via a pipe, but this looks
like a general problem. Is there a way to wire up the readiness of the
output chardev to the parallel port ACK and BUSY lines, and signal an
ISA interrupt? I don't know the code well enough to tell.
** Affects: qemu
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1381846
Title:
Data sent to parallel port in guest is lost if host buffer fills up
Status in QEMU:
New
Bug description:
It appears that qemu will blindly write characters out to the chardev
and drop them on the floor if a write fails with EAGAIN, without
initiating flow control (via BUSY and ACK) back to the guest. If the
host buffer is too small, or is talking to a hardware device that is
too slow, data will be lost.
I notice this problem when I run a DOS program with this on the qemu command
line:
-parallel /dev/usb/lp0
I can work around this problem by buffering via a pipe, but this looks
like a general problem. Is there a way to wire up the readiness of the
output chardev to the parallel port ACK and BUSY lines, and signal an
ISA interrupt? I don't know the code well enough to tell.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1381846/+subscriptions
- [Qemu-devel] [PATCH v4 00/12] QEmu memory hot unplug support., Tang Chen, 2014/10/16
- [Qemu-devel] [PATCH v4 03/12] acpi, mem-hotplug: Add acpi_memory_hotplug_sci() to rise sci for memory hotplug., Tang Chen, 2014/10/16
- [Qemu-devel] [PATCH v4 01/12] acpi, mem-hotplug: Use PC_DIMM_SLOT_PROP in acpi_memory_plug_cb()., Tang Chen, 2014/10/16
- [Qemu-devel] [PATCH v4 05/12] acpi, piix4: Add memory hot unplug support for piix4., Tang Chen, 2014/10/16
- [Qemu-devel] [PATCH v4 02/12] acpi, mem-hotplug: Add acpi_memory_get_slot_status_descriptor() to get MemStatus., Tang Chen, 2014/10/16
- [Qemu-devel] [PATCH v4 04/12] acpi, mem-hotplug: Add acpi_memory_unplug_cb() to implement memory unplug., Tang Chen, 2014/10/16
- [Qemu-devel] [PATCH v4 07/12] pc: Add memory hot unplug support for pc machine., Tang Chen, 2014/10/16
- [Qemu-devel] [PATCH v4 06/12] acpi, ich9: Add memory hot unplug support for ich9., Tang Chen, 2014/10/16
- [Qemu-devel] [PATCH v4 08/12] qdev: Add memory hot unplug support for bus-less devices., Tang Chen, 2014/10/16
- [Qemu-devel] [PATCH v4 09/12] pc-dimm: Add pc_dimm_unrealize() for memory hot unplug support., Tang Chen, 2014/10/16
- [Qemu-devel] [PATCH v4 10/12] acpi: Add hardware implementation for memory hot unplug., Tang Chen, 2014/10/16