xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Juergen Gross <jgross@suse.com>
To: xen-devel <xen-devel@lists.xenproject.org>
Subject: potential problem with qdisk backend
Date: Fri, 6 May 2016 13:41:14 +0200	[thread overview]
Message-ID: <572C82DA.3040308@suse.com> (raw)

Looking at the qdisk backend implementation I wondered whether
blkif_get_x86_32_req() is really correct, especially for the
BLKIF_OP_DISCARD case. The Linux kernel based blk backend seems to
distinguish 32- and 64-bit layouts of blkif_request_discard while
qemu treats them to be the same.

Am I completely wrong here?


Juergen

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

             reply	other threads:[~2016-05-06 11:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-06 11:41 Juergen Gross [this message]
2016-05-11 13:53 ` potential problem with qdisk backend Juergen Gross
2016-05-16 11:59   ` Stefano Stabellini
2016-05-13 15:42 ` Jan Beulich

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=572C82DA.3040308@suse.com \
    --to=jgross@suse.com \
    --cc=xen-devel@lists.xenproject.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).