From: David Miller <davem@davemloft.net>
To: sonnyrao@chromium.org
Cc: netdev@vger.kernel.org
Subject: Re: [v2] vhost: add vsock compat ioctl
Date: Sat, 17 Mar 2018 09:24:06 -0400 (EDT) [thread overview]
Message-ID: <20180317.092406.1395846063616448715.davem@davemloft.net> (raw)
In-Reply-To: <CAPz6YkX8SZVOFyOAdhrotvQ7MtGYnuzb_=+tSfX6jB+rvQm2_w@mail.gmail.com>
From: Sonny Rao <sonnyrao@chromium.org>
Date: Fri, 16 Mar 2018 17:54:12 -0700
> On Fri, Mar 16, 2018 at 12:30 PM, David Miller <davem@davemloft.net> wrote:
>>
>> Although the top level ioctls are probably size and layout compatible,
>> I do not think that the deeper ioctls can be called by compat binaries
>> without some translations in order for them to work.
>
> Ok, thanks -- I have only tested VHOST_VSOCK_SET_GUEST_CID and
> VHOST_VSOCK_SET_RUNNING but by deeper ioctls I think you might mean
> the ioctls under vhost_dev_ioctl() and vhost_vring_ioctl()?
Yes.
next prev parent reply other threads:[~2018-03-17 13:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-16 19:30 [v2] vhost: add vsock compat ioctl David Miller
2018-03-17 0:54 ` Sonny Rao
2018-03-17 13:24 ` David Miller [this message]
2018-03-22 9:25 ` Stefan Hajnoczi
2018-03-22 20:38 ` Sonny Rao
2018-03-25 20:50 ` David Miller
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=20180317.092406.1395846063616448715.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=sonnyrao@chromium.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).