xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Jan Beulich <JBeulich@novell.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: floppy not working in Linux
Date: Thu, 4 Mar 2010 13:28:49 -0500	[thread overview]
Message-ID: <20100304182849.GC20263@phenom.dumpdata.com> (raw)
In-Reply-To: <4B8FD5370200007800032C05@vpn.id2.novell.com>

On Thu, Mar 04, 2010 at 02:43:51PM +0000, Jan Beulich wrote:
> We had a report that the floppy driver isn't working with current Xen.
> While certainly not a major concern to most of us, it still seems odd that
> this simple a piece of hard-/software wouldn't work under Xen, especially
> as it is known that it had been working a couple of years back.

The USB one works, thought there the DMA Debug interface throws a nice
message about doing DMA from a stack - hadn't looked in details for
in this.
> 
> Trying to debug the issue has surfaced quite a perhaps strange mix of
> observations:
> 
> - On an old (32-bit) box of mine I found that the driver would work
> on Xen 3.1, while the same kernel running on top of 3.2.x would not
> work (nor would a reasonably current kernel on a reasonably current
> Xen).
> - On both this old and not too old a 64-bit box I found that removing
> the REALLY_SLOW_IO definition at the top of floppy.c would reduce
> the amount of errors encountered quite significantly. Specifically, I
> have never seen a mount fail with that change in place (but there
> are occasional errors logged by the driver).
> - Generally, the problems start with unexpected interrupts or, less
> frequently, "-- FDC reply error" messages.
> 
> While the driver certainly didn't change much over the last couple
> of years, the effect of the adjustment above suggests that the
> driver itself may have problems which are just unnoticeable when
> run on bare hardware.
> 
> Given the timing requirements to service the FDC (a maximum of
> about 120us when using the FIFO optimally) I wonder whether it
> is reasonable to expect this to work reliably at all, especially
> when guest domains are consuming non-neglectable amounts of
> CPU time.
> 
> Jan
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel

      reply	other threads:[~2010-03-04 18:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-04 14:43 floppy not working in Linux Jan Beulich
2010-03-04 18:28 ` Konrad Rzeszutek Wilk [this message]

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=20100304182849.GC20263@phenom.dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=JBeulich@novell.com \
    --cc=xen-devel@lists.xensource.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).