From: Shu-Chun Weng via <qemu-devel@nongnu.org>
To: qemu-devel@nongnu.org
Cc: Riku Voipio <riku.voipio@iki.fi>, Shu-Chun Weng <scw@google.com>,
Laurent Vivier <laurent@vivier.eu>
Subject: [PATCH 0/2] thunk, linux-user: Add support for SIOCETHTOOL ioctl
Date: Fri, 18 Dec 2020 13:41:40 -0800 [thread overview]
Message-ID: <20201218214142.3673709-1-scw@google.com> (raw)
Hi Riku and Laurent,
These two patches together implements the SIOCETHTOOL ioctl operations. Many of
the kernel structures in this operations make use of flexible arrays (array with
no size / zero size at the end of the structure), so I extended thunk to handle
these fields natively.
This patch set was previously sent out under "[PATCH 0/6] fcntl, sockopt, and
ioctl options" and the following revisions, but did not get any feedback.
Shu-Chun Weng (2):
thunk: supports flexible arrays
linux-user: Add support for SIOCETHTOOL ioctl
include/exec/user/thunk.h | 24 +
linux-user/ethtool.c | 848 ++++++++++++++++++++++++++++++++++
linux-user/ethtool.h | 20 +
linux-user/ethtool_entries.h | 107 +++++
linux-user/ioctls.h | 2 +
linux-user/meson.build | 1 +
linux-user/qemu.h | 1 +
linux-user/syscall.c | 36 +-
linux-user/syscall_defs.h | 12 +
linux-user/syscall_types.h | 280 +++++++++++
tests/tcg/multiarch/ethtool.c | 423 +++++++++++++++++
thunk.c | 152 +++++-
12 files changed, 1893 insertions(+), 13 deletions(-)
create mode 100644 linux-user/ethtool.c
create mode 100644 linux-user/ethtool.h
create mode 100644 linux-user/ethtool_entries.h
create mode 100644 tests/tcg/multiarch/ethtool.c
--
2.29.2.684.gfbc64c5ab5-goog
next reply other threads:[~2020-12-18 21:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-18 21:41 Shu-Chun Weng via [this message]
2020-12-18 21:41 ` [PATCH 1/2] thunk: supports flexible arrays Shu-Chun Weng via
2020-12-18 21:41 ` [PATCH 2/2] linux-user: Add support for SIOCETHTOOL ioctl Shu-Chun Weng via
2020-12-18 21:51 ` [PATCH 0/2] thunk, " no-reply
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=20201218214142.3673709-1-scw@google.com \
--to=qemu-devel@nongnu.org \
--cc=laurent@vivier.eu \
--cc=riku.voipio@iki.fi \
--cc=scw@google.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).