From: Alexander Ivanov <alexander.ivanov@virtuozzo.com>
To: qemu-devel@nongnu.org
Cc: den@virtuozzo.com, michael.roth@amd.com, kkostiuk@redhat.com
Subject: [PATCH v2 0/7] qga: Add FreeBSD support
Date: Thu, 29 Sep 2022 09:52:32 +0200 [thread overview]
Message-ID: <20220929075239.1675374-1-alexander.ivanov@virtuozzo.com> (raw)
Add freeze/thaw, shutdown/halt/reboot and password setting support for
FreeBSD.
v2:
1: Reject the idea to move all the Linux-specific code to a separate file.
First commit now adds initial support of FreeBSD. Fixed device paths
and fixed virtio device initialization (disable echo). Add comment why
we should disable the code under HAVE_GETIFADDRS in FreeBSD.
2: Replace the second commit (which now is the first) by moving
Linux-specific freeze/thaw code to a separate file commands-linux.c.
3: Add error raising if stat() returns error. Replaced strcmp() calls by
g_str_equal(). Add a comment explaining why UFSRESUME isn't necessary.
4: Replace #elifdef by #elif defined().
5: Now the code doesn't move from one file to aanother but still is
moving inside file so the patch doesn't become easier to review. =(
Fixed typos.
6,7: New patches. Add guest-network-get-interfaces command support.
Alexander Ivanov (7):
qga: Add initial FreeBSD support
qga: Move Linux-specific FS freeze/thaw code to a separate file
qga: Add UFS freeze/thaw support for FreeBSD
qga: Add shutdown/halt/reboot support for FreeBSD
qga: Add support for user password setting in FreeBSD
qga: Move HW address getting to a separate function
qga: Add HW address getting for FreeBSD
meson.build | 2 +-
qga/channel-posix.c | 14 +
qga/commands-bsd.c | 193 ++++++++++
qga/commands-common.h | 52 +++
qga/commands-linux.c | 286 ++++++++++++++
qga/commands-posix.c | 843 ++++++++++++++++--------------------------
qga/main.c | 13 +-
qga/meson.build | 6 +
8 files changed, 867 insertions(+), 542 deletions(-)
create mode 100644 qga/commands-bsd.c
create mode 100644 qga/commands-linux.c
--
2.34.1
next reply other threads:[~2022-09-29 8:24 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-29 7:52 Alexander Ivanov [this message]
2022-09-29 7:52 ` [PATCH 1/7] qga: Add initial FreeBSD support Alexander Ivanov
2022-09-29 11:29 ` Marc-André Lureau
2022-09-29 14:11 ` Alexander Ivanov
2022-09-29 7:52 ` [PATCH 2/7] qga: Move Linux-specific FS freeze/thaw code to a separate file Alexander Ivanov
2022-09-29 11:29 ` Marc-André Lureau
2022-09-29 7:52 ` [PATCH 3/7] qga: Add UFS freeze/thaw support for FreeBSD Alexander Ivanov
2022-09-29 11:28 ` Marc-André Lureau
2022-09-29 7:52 ` [PATCH 4/7] qga: Add shutdown/halt/reboot " Alexander Ivanov
2022-09-29 11:28 ` Marc-André Lureau
2022-09-29 7:52 ` [PATCH 5/7] qga: Add support for user password setting in FreeBSD Alexander Ivanov
2022-09-29 11:22 ` Marc-André Lureau
2022-09-29 14:29 ` Alexander Ivanov
2022-09-30 8:19 ` Marc-André Lureau
2022-09-30 13:11 ` Alexander Ivanov
2022-09-29 7:52 ` [PATCH 6/7] qga: Move HW address getting to a separate function Alexander Ivanov
2022-09-29 11:28 ` Marc-André Lureau
2022-09-29 14:33 ` Alexander Ivanov
2022-09-29 7:52 ` [PATCH 7/7] qga: Add HW address getting for FreeBSD Alexander Ivanov
2022-09-29 11:28 ` Marc-André Lureau
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=20220929075239.1675374-1-alexander.ivanov@virtuozzo.com \
--to=alexander.ivanov@virtuozzo.com \
--cc=den@virtuozzo.com \
--cc=kkostiuk@redhat.com \
--cc=michael.roth@amd.com \
--cc=qemu-devel@nongnu.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).