qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: John Snow <jsnow@redhat.com>
To: qemu-devel <qemu-devel@nongnu.org>
Cc: "Andreas Färber" <afaerber@suse.de>, qemu-block@nongnu.org
Subject: [Qemu-devel] 2.3-rc0 ahci-test failure on ppc64
Date: Wed, 18 Mar 2015 21:56:06 -0400	[thread overview]
Message-ID: <550A2CB6.5030300@redhat.com> (raw)

Andreas brought this failure to my attention; it looks like PIO 
read/writes for nsectors > 1 for IDE or AHCI will fail on ppc64.

The failure is in the IDE core layer.

In a nutshell, we've never *actually* supported PIO r/w for nsectors > 
1, I just started testing it as a spec compliance item (and because it 
was easy to just swap out DMA with PIO commands in my test framework.)

It looks like my tests passing on LE are just an unfortunate coincidence.

I'll prepare some patches tomorrow.

Thanks,
--js

                 reply	other threads:[~2015-03-19  1:56 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=550A2CB6.5030300@redhat.com \
    --to=jsnow@redhat.com \
    --cc=afaerber@suse.de \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    /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).