qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: John Snow <jsnow@redhat.com>
To: Aurelien Jarno <aurelien@aurel32.net>, qemu-devel@nongnu.org
Cc: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>
Subject: Re: [Qemu-devel] [PATCH for-2.4] macio: re-add TRIM support
Date: Fri, 31 Jul 2015 16:37:17 -0400	[thread overview]
Message-ID: <55BBDC7D.9050100@redhat.com> (raw)
In-Reply-To: <1438198068-32428-1-git-send-email-aurelien@aurel32.net>



On 07/29/2015 03:27 PM, Aurelien Jarno wrote:
> Commit bd4214fc dropped TRIM support by mistake. Given it is still
> advertised to the host when using a drive with discard=on, this cause
> the IDE bus to hang when the host issues a TRIM command.
> 
> This patch fixes that by re-adding the TRIM code, ported to the new
> new DMA implementation.
> 
> Cc: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>
> Cc: John Snow <jsnow@redhat.com>
> Signed-off-by: Aurelien Jarno <aurelien@aurel32.net>
> ---
>  hw/ide/macio.c | 28 ++++++++++++++++++++++++++++
>  1 file changed, 28 insertions(+)
> 
> diff --git a/hw/ide/macio.c b/hw/ide/macio.c
> index a55a479..66ac2ba 100644
> --- a/hw/ide/macio.c
> +++ b/hw/ide/macio.c
> @@ -208,6 +208,33 @@ static void pmac_dma_write(BlockBackend *blk,
>                                cb, io);
>  }
>  
> +static void pmac_dma_trim(BlockBackend *blk,
> +                        int64_t offset, int bytes,
> +                        void (*cb)(void *opaque, int ret), void *opaque)
> +{
> +    DBDMA_io *io = opaque;
> +    MACIOIDEState *m = io->opaque;
> +    IDEState *s = idebus_active_if(&m->bus);
> +    dma_addr_t dma_addr, dma_len;
> +    void *mem;
> +
> +    qemu_iovec_destroy(&io->iov);
> +    qemu_iovec_init(&io->iov, io->len / MACIO_PAGE_SIZE + 1);
> +
> +    dma_addr = io->addr;
> +    dma_len = io->len;
> +    mem = dma_memory_map(&address_space_memory, dma_addr, &dma_len,
> +                         DMA_DIRECTION_TO_DEVICE);
> +
> +    qemu_iovec_add(&io->iov, mem, io->len);
> +    s->io_buffer_size -= io->len;
> +    s->io_buffer_index += io->len;
> +    io->len = 0;
> +
> +    m->aiocb = ide_issue_trim(blk, (offset >> 9), &io->iov, (bytes >> 9),
> +                              cb, io);
> +}
> +
>  static void pmac_ide_atapi_transfer_cb(void *opaque, int ret)
>  {
>      DBDMA_io *io = opaque;
> @@ -313,6 +340,7 @@ static void pmac_ide_transfer_cb(void *opaque, int ret)
>          pmac_dma_write(s->blk, offset, io->len, pmac_ide_transfer_cb, io);
>          break;
>      case IDE_DMA_TRIM:
> +        pmac_dma_trim(s->blk, offset, io->len, pmac_ide_transfer_cb, io);
>          break;
>      }
>  
> 

Looks sane, and tested myself.

Not that this is a problem you introduced, but we don't *unmap* this
memory anywhere, something else I overlooked for the initial patch.

Reviewed-by: John Snow <jsnow@redhat.com>

  reply	other threads:[~2015-07-31 20:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-29 19:27 [Qemu-devel] [PATCH for-2.4] macio: re-add TRIM support Aurelien Jarno
2015-07-31 20:37 ` John Snow [this message]
2015-08-01 11:10 ` Mark Cave-Ayland
2015-08-01 12:37   ` Aurelien Jarno

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=55BBDC7D.9050100@redhat.com \
    --to=jsnow@redhat.com \
    --cc=aurelien@aurel32.net \
    --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).