From: Olaf Hering <olaf@aepfle.de>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: kwolf@redhat.com, qemu-devel@nongnu.org, stefanha@redhat.com
Subject: Re: [Qemu-devel] [PATCH v2] xen_disk: add discard support
Date: Thu, 20 Feb 2014 19:20:58 +0100 [thread overview]
Message-ID: <20140220182057.GB19843@aepfle.de> (raw)
In-Reply-To: <alpine.DEB.2.02.1402201803290.15812@kaball.uk.xensource.com>
On Thu, Feb 20, Stefano Stabellini wrote:
> On Thu, 6 Feb 2014, Olaf Hering wrote:
> > @@ -253,6 +254,8 @@ static int ioreq_parse(struct ioreq *ioreq)
> > case BLKIF_OP_WRITE:
> > ioreq->prot = PROT_READ; /* from memory */
> > break;
> > + case BLKIF_OP_DISCARD:
> > + return 0;
> > default:
> > xen_be_printf(&blkdev->xendev, 0, "error: unknown operation (%d)\n",
> > ioreq->req.operation);
>
> Unfortunately I didn't realize before that older Xen releases don't
> define BLKIF_OP_DISCARD, therefore this patch would cause QEMU build
> failures against Xen 4.1 for example.
Would that work for you?
Olaf
diff --git a/include/hw/xen/xen_common.h b/include/hw/xen/xen_common.h
index 2d5a25b..4ca03ff 100644
--- a/include/hw/xen/xen_common.h
+++ b/include/hw/xen/xen_common.h
@@ -144,6 +144,9 @@ static inline int xen_xc_hvm_inject_msi(XenXC xen_xc, domid_t dom,
{
return -ENOSYS;
}
+#ifndef BLKIF_OP_DISCARD
+#define BLKIF_OP_DISCARD 5
+#endif
#else
static inline int xen_xc_hvm_inject_msi(XenXC xen_xc, domid_t dom,
uint64_t addr, uint32_t data)
next prev parent reply other threads:[~2014-02-20 18:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-06 15:59 [Qemu-devel] [PATCH v2] xen_disk: add discard support Olaf Hering
2014-02-20 18:06 ` Stefano Stabellini
2014-02-20 18:14 ` Olaf Hering
2014-02-20 18:17 ` Stefano Stabellini
2014-02-20 18:20 ` Olaf Hering [this message]
2014-02-23 15:30 ` Stefano Stabellini
2014-02-24 16:28 ` Olaf Hering
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=20140220182057.GB19843@aepfle.de \
--to=olaf@aepfle.de \
--cc=kwolf@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--cc=stefano.stabellini@eu.citrix.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.