From: Markus Armbruster <armbru@redhat.com>
To: qemu-devel@nongnu.org
Cc: Anthony Perard <anthony.perard@citrix.com>,
xen-devel@lists.xenproject.org,
Stefano Stabellini <sstabellini@kernel.org>
Subject: Re: configure --help lacks explanation of xen-pci-passthrough
Date: Thu, 03 May 2018 18:41:41 +0200 [thread overview]
Message-ID: <87r2mshet6.fsf@dusky.pond.sub.org> (raw)
In-Reply-To: <87lgdjvem0.fsf@dusky.pond.sub.org> (Markus Armbruster's message of "Thu, 19 Apr 2018 09:29:11 +0200")
Ping?
Markus Armbruster <armbru@redhat.com> writes:
> $ ./configure --help | grep -C 3 xen-pci-passthrough
> virtfs VirtFS
> mpath Multipath persistent reservation passthrough
> xen xen backend driver support
> xen-pci-passthrough
> brlapi BrlAPI (Braile)
> curl curl connectivity
> membarrier membarrier system call (for Linux 4.14+ or Windows)
>
> This is the only --enable thing without an explanation. Okay, many of
> the explanations suck, but that's no excuse. Xen guys, please provide
> one.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
WARNING: multiple messages have this Message-ID (diff)
From: Markus Armbruster <armbru@redhat.com>
To: qemu-devel@nongnu.org
Cc: Stefano Stabellini <sstabellini@kernel.org>,
Anthony Perard <anthony.perard@citrix.com>,
xen-devel@lists.xenproject.org
Subject: Re: [Qemu-devel] configure --help lacks explanation of xen-pci-passthrough
Date: Thu, 03 May 2018 18:41:41 +0200 [thread overview]
Message-ID: <87r2mshet6.fsf@dusky.pond.sub.org> (raw)
In-Reply-To: <87lgdjvem0.fsf@dusky.pond.sub.org> (Markus Armbruster's message of "Thu, 19 Apr 2018 09:29:11 +0200")
Ping?
Markus Armbruster <armbru@redhat.com> writes:
> $ ./configure --help | grep -C 3 xen-pci-passthrough
> virtfs VirtFS
> mpath Multipath persistent reservation passthrough
> xen xen backend driver support
> xen-pci-passthrough
> brlapi BrlAPI (Braile)
> curl curl connectivity
> membarrier membarrier system call (for Linux 4.14+ or Windows)
>
> This is the only --enable thing without an explanation. Okay, many of
> the explanations suck, but that's no excuse. Xen guys, please provide
> one.
next prev parent reply other threads:[~2018-05-03 16:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-19 7:29 configure --help lacks explanation of xen-pci-passthrough Markus Armbruster
2018-04-19 7:29 ` [Qemu-devel] " Markus Armbruster
2018-05-03 16:41 ` Markus Armbruster [this message]
2018-05-03 16:41 ` Markus Armbruster
2018-05-04 9:17 ` [Qemu-devel] [PATCH] configure: Add explanation for --enable-xen-pci-passthrough Anthony PERARD
2018-05-04 11:26 ` Markus Armbruster
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=87r2mshet6.fsf@dusky.pond.sub.org \
--to=armbru@redhat.com \
--cc=anthony.perard@citrix.com \
--cc=qemu-devel@nongnu.org \
--cc=sstabellini@kernel.org \
--cc=xen-devel@lists.xenproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.