qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@redhat.com>
To: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>
Cc: kwolf@redhat.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 0/5] cmd646 tidy-up and interrupt status fixes
Date: Tue, 12 Aug 2014 09:53:43 +0100	[thread overview]
Message-ID: <20140812085343.GA20490@stefanha-thinkpad.redhat.com> (raw)
In-Reply-To: <1407515016-26273-1-git-send-email-mark.cave-ayland@ilande.co.uk>

[-- Attachment #1: Type: text/plain, Size: 1493 bytes --]

On Fri, Aug 08, 2014 at 05:23:31PM +0100, Mark Cave-Ayland wrote:
> This patchset came out of my work trying to boot NetBSD on SPARC64.
> 
> According to the datasheet, the 646U2 UDMA interrupt status bits are exact 
> mirrors of the normal DMA interrupt status bits, and an interrupt can be
> cleared by writing a 1 to the relevant bit in PCI configuration space.
> 
> The existing implementation caused NetBSD to fail since it would always check
> and clear the normal DMA interrupt status bit, even if UDMA was being used.
> Hence this patchset ensures that the current interrupt status is always 
> consistent between both normal DMA and UDMA registers, including when either 
> one of the interrupt status bits is cleared by writing to PCI configuration 
> space.
> 
> Signed-off-by: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>
> 
> Mark Cave-Ayland (5):
>   cmd646: add constants for CNTRL register access
>   cmd646: synchronise DMA interrupt status with UDMA interrupt status
>   cmd646: switch cmd646_update_irq() to accept PCIDevice instead of
>     PCIIDEState
>   cmd646: allow MRDMODE interrupt status bits clearing from PCI config
>     space
>   cmd646: synchronise UDMA interrupt status with DMA interrupt status
> 
>  hw/ide/cmd646.c |   94 +++++++++++++++++++++++++++++++++++++++++++++++++------
>  1 file changed, 85 insertions(+), 9 deletions(-)

Thanks, applied to my block tree:
https://github.com/stefanha/qemu/commits/block

Stefan

[-- Attachment #2: Type: application/pgp-signature, Size: 473 bytes --]

      parent reply	other threads:[~2014-08-12  8:54 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-08 16:23 [Qemu-devel] [PATCH 0/5] cmd646 tidy-up and interrupt status fixes Mark Cave-Ayland
2014-08-08 16:23 ` [Qemu-devel] [PATCH 1/5] cmd646: add constants for CNTRL register access Mark Cave-Ayland
2014-08-08 16:23 ` [Qemu-devel] [PATCH 2/5] cmd646: synchronise DMA interrupt status with UDMA interrupt status Mark Cave-Ayland
2014-08-08 16:23 ` [Qemu-devel] [PATCH 3/5] cmd646: switch cmd646_update_irq() to accept PCIDevice instead of PCIIDEState Mark Cave-Ayland
2014-08-08 16:23 ` [Qemu-devel] [PATCH 4/5] cmd646: allow MRDMODE interrupt status bits clearing from PCI config space Mark Cave-Ayland
2014-08-08 16:23 ` [Qemu-devel] [PATCH 5/5] cmd646: synchronise UDMA interrupt status with DMA interrupt status Mark Cave-Ayland
2014-08-11 15:12   ` Stefan Hajnoczi
2014-08-11 15:33     ` Mark Cave-Ayland
2014-08-12  8:47       ` Stefan Hajnoczi
2014-08-11 15:13 ` [Qemu-devel] [PATCH 0/5] cmd646 tidy-up and interrupt status fixes Stefan Hajnoczi
2014-08-12  8:53 ` Stefan Hajnoczi [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=20140812085343.GA20490@stefanha-thinkpad.redhat.com \
    --to=stefanha@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=mark.cave-ayland@ilande.co.uk \
    --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).