From: Avi Kivity <avi@redhat.com>
To: "Nicholas A. Bellinger" <nab@linux-iscsi.org>
Cc: Jens Axboe <axboe@kernel.dk>,
Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>,
kvm-devel <kvm@vger.kernel.org>,
"Michael S. Tsirkin" <mst@redhat.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Zhi Yong Wu <wuzhy@linux.vnet.ibm.com>,
qemu-devel <qemu-devel@nongnu.org>,
lf-virt <virtualization@lists.linux-foundation.org>,
Anthony Liguori <aliguori@linux.vnet.ibm.com>,
target-devel <target-devel@vger.kernel.org>,
Hannes Reinecke <hare@suse.de>,
linux-scsi <linux-scsi@vger.kernel.org>,
Paolo Bonzini <pbonzini@redhat.com>,
Zhi Yong Wu <wuzhy@cn.ibm.com>, Christoph Hellwig <hch@lst.de>
Subject: Re: [Qemu-devel] [PATCH] tcm_vhost: Expose ABI version via VHOST_SCSI_GET_ABI_VERSION
Date: Sun, 29 Jul 2012 15:50:59 +0300 [thread overview]
Message-ID: <501531B3.5060301@redhat.com> (raw)
In-Reply-To: <1343333727.22538.3.camel@haakon2.linux-iscsi.org>
On 07/26/2012 11:15 PM, Nicholas A. Bellinger wrote:
>>
>
> Example..? If there is a better way to handle ioctl compat I'd
> certainly like to hear about it.
>
r = ioctl(fd, KVM_CHECK_EXTENSION, KVM_CAP_ASSIGN_DEV_IRQ);
if (r == -1)
...
if (r)
// ioctl(fd, KVM_ASSIGN_DEV_IRQ, ...) is available
else
not available
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2012-07-29 12:51 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-24 1:26 [Qemu-devel] [PATCH] tcm_vhost: Expose ABI version via VHOST_SCSI_GET_ABI_VERSION Nicholas A. Bellinger
2012-07-24 1:56 ` Greg Kroah-Hartman
2012-07-24 20:45 ` Nicholas A. Bellinger
2012-07-25 11:55 ` Stefan Hajnoczi
2012-07-25 21:14 ` Nicholas A. Bellinger
2012-07-25 22:35 ` Stefan Hajnoczi
2012-07-26 2:34 ` Nicholas A. Bellinger
2012-07-26 8:58 ` Avi Kivity
2012-07-26 20:15 ` Nicholas A. Bellinger
2012-07-29 12:35 ` Michael S. Tsirkin
2012-07-29 12:50 ` Avi Kivity [this message]
2012-07-25 13:10 ` Avi Kivity
2012-07-25 21:10 ` Nicholas A. Bellinger
2012-07-29 12:27 ` Michael S. Tsirkin
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=501531B3.5060301@redhat.com \
--to=avi@redhat.com \
--cc=aliguori@linux.vnet.ibm.com \
--cc=axboe@kernel.dk \
--cc=gregkh@linuxfoundation.org \
--cc=hare@suse.de \
--cc=hch@lst.de \
--cc=kvm@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=mst@redhat.com \
--cc=nab@linux-iscsi.org \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@linux.vnet.ibm.com \
--cc=target-devel@vger.kernel.org \
--cc=virtualization@lists.linux-foundation.org \
--cc=wuzhy@cn.ibm.com \
--cc=wuzhy@linux.vnet.ibm.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 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).