From: Konstantin Kostiuk <kkostiuk@redhat.com>
To: Alexander Ivanov <alexander.ivanov@virtuozzo.com>
Cc: qemu-devel@nongnu.org, den@virtuozzo.com, michael.roth@amd.com,
marcandre.lureau@gmail.com
Subject: Re: [PATCH v3 7/7] qga: Add HW address getting for FreeBSD
Date: Mon, 3 Oct 2022 16:49:15 +0300 [thread overview]
Message-ID: <CAPMcbCpLOGm4Q4H=ygSnN=puqFtnL3LBBxSOG2kMzcnKxU7B7g@mail.gmail.com> (raw)
In-Reply-To: <20221003093911.1844031-8-alexander.ivanov@virtuozzo.com>
[-- Attachment #1: Type: text/plain, Size: 1585 bytes --]
Reviewed-by: Konstantin Kostiuk <kkostiuk@redhat.com>
On Mon, Oct 3, 2022 at 12:39 PM Alexander Ivanov <
alexander.ivanov@virtuozzo.com> wrote:
> Replace a dumb function in commands-bsd.c by the code of HW address
> getting.
>
> Reviewed-by: Marc-André Lureau <marcandre.lureau@redhat.com>
> Signed-off-by: Alexander Ivanov <alexander.ivanov@virtuozzo.com>
> ---
> qga/commands-bsd.c | 14 ++++++++++++++
> 1 file changed, 14 insertions(+)
>
> diff --git a/qga/commands-bsd.c b/qga/commands-bsd.c
> index 40f7ec7600..5f423a4710 100644
> --- a/qga/commands-bsd.c
> +++ b/qga/commands-bsd.c
> @@ -20,6 +20,8 @@
> #include <sys/param.h>
> #include <sys/ucred.h>
> #include <sys/mount.h>
> +#include <net/if_dl.h>
> +#include <net/ethernet.h>
> #include <paths.h>
>
> #if defined(CONFIG_FSFREEZE) || defined(CONFIG_FSTRIM)
> @@ -179,7 +181,19 @@ GuestCpuStatsList *qmp_guest_get_cpustats(Error
> **errp)
> int guest_get_hw_addr(struct ifaddrs *ifa, unsigned char *buf,
> bool *obtained, Error **errp)
> {
> + struct sockaddr_dl *sdp;
> +
> *obtained = false;
> + if (ifa->ifa_addr->sa_family != AF_LINK) {
> + /* We can get HW address only for AF_LINK family. */
> + g_debug("failed to get MAC address of %s", ifa->ifa_name);
> + return 0;
> + }
> +
> + sdp = (struct sockaddr_dl *)ifa->ifa_addr;
> + memcpy(buf, sdp->sdl_data + sdp->sdl_nlen, ETHER_ADDR_LEN);
> + *obtained = true;
> +
> return 0;
> }
> #endif /* HAVE_GETIFADDRS */
> --
> 2.34.1
>
>
[-- Attachment #2: Type: text/html, Size: 2283 bytes --]
prev parent reply other threads:[~2022-10-03 13:55 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-03 9:39 [PATCH v3 0/7] qga: Add FreeBSD support Alexander Ivanov
2022-10-03 9:39 ` [PATCH v3 1/7] qga: Add initial " Alexander Ivanov
2022-10-03 9:58 ` Marc-André Lureau
2022-10-03 13:42 ` Konstantin Kostiuk
2022-10-03 9:39 ` [PATCH v3 2/7] qga: Move Linux-specific FS freeze/thaw code to a separate file Alexander Ivanov
2022-10-03 13:42 ` Konstantin Kostiuk
2022-10-03 9:39 ` [PATCH v3 3/7] qga: Add UFS freeze/thaw support for FreeBSD Alexander Ivanov
2022-10-03 13:42 ` Konstantin Kostiuk
2022-10-03 9:39 ` [PATCH v3 4/7] qga: Add shutdown/halt/reboot " Alexander Ivanov
2022-10-03 13:43 ` Konstantin Kostiuk
2022-10-03 9:39 ` [PATCH v3 5/7] qga: Add support for user password setting in FreeBSD Alexander Ivanov
2022-10-03 9:54 ` Marc-André Lureau
2022-10-03 13:43 ` Konstantin Kostiuk
2022-10-03 9:39 ` [PATCH v3 6/7] qga: Move HW address getting to a separate function Alexander Ivanov
2022-10-03 9:58 ` Marc-André Lureau
2022-10-03 13:48 ` Konstantin Kostiuk
2022-10-03 9:39 ` [PATCH v3 7/7] qga: Add HW address getting for FreeBSD Alexander Ivanov
2022-10-03 13:49 ` Konstantin Kostiuk [this message]
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='CAPMcbCpLOGm4Q4H=ygSnN=puqFtnL3LBBxSOG2kMzcnKxU7B7g@mail.gmail.com' \
--to=kkostiuk@redhat.com \
--cc=alexander.ivanov@virtuozzo.com \
--cc=den@virtuozzo.com \
--cc=marcandre.lureau@gmail.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).