From: Paolo Bonzini <pbonzini@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: marcandre.lureau@redhat.com,
"Daniel P. Berrangé" <berrange@redhat.com>,
qemu-devel@nongnu.org, "Bruce Rogers" <brogers@suse.com>
Subject: Re: [PATCH] meson: install ivshmem-client and ivshmem-server
Date: Fri, 4 Sep 2020 09:57:29 +0200 [thread overview]
Message-ID: <509826bc-9683-dd1d-fa6a-55fc3fddc57c@redhat.com> (raw)
In-Reply-To: <87a6y6dmy4.fsf@dusky.pond.sub.org>
On 04/09/20 09:24, Markus Armbruster wrote:
>> Ah, via the tools variable in configure. Nice maze. I've queued the patch.
> Please don't.
>
> These programs are examples to help people understand how the ivhsmem
> device works. They might even be useful for debugging. They are *not*
> to be used in production.
Oooookay. :) It needs to be documented in the changelog.
Paolo
> docs/specs/ivshmem-spec.txt:
>
> Example server code is in contrib/ivshmem-server/. Not to be used in
> production. It assumes all clients use the same number of interrupt
> vectors.
>
> A standalone client is in contrib/ivshmem-client/. It can be useful
> for debugging.
>
> Installing example *source* might make sense (but I doubt it).
> Installing the binaries does not.
>
next prev parent reply other threads:[~2020-09-04 7:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-03 15:35 [PATCH] meson: install ivshmem-client and ivshmem-server Bruce Rogers
2020-09-03 15:42 ` Marc-André Lureau
2020-09-03 15:44 ` Paolo Bonzini
2020-09-03 15:49 ` Daniel P. Berrangé
2020-09-03 16:10 ` Bruce Rogers
2020-09-03 17:55 ` Paolo Bonzini
2020-09-04 7:24 ` Markus Armbruster
2020-09-04 7:57 ` Paolo Bonzini [this message]
2020-09-04 9:20 ` Markus Armbruster
2020-09-04 11:49 ` Bruce Rogers
2020-09-04 13:39 ` Markus Armbruster
2020-09-04 9:37 ` Philippe Mathieu-Daudé
2020-09-04 10:27 ` Daniel P. Berrangé
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=509826bc-9683-dd1d-fa6a-55fc3fddc57c@redhat.com \
--to=pbonzini@redhat.com \
--cc=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=brogers@suse.com \
--cc=marcandre.lureau@redhat.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).