Hi
On Wed, Oct 31, 2018 at 8:05 PM Daniel P. Berrangé wrote:
>
> On Wed, Oct 31, 2018 at 07:44:36PM +0400, Marc-André Lureau wrote:
> > Hi
> >
> > On Tue, Oct 16, 2018 at 4:14 PM Daniel P. Berrangé
> > wrote:
> > > > > It just reinvents the chardev unix socket syntax, but in a
> > > > > differe
On Wed, Oct 31, 2018 at 07:44:36PM +0400, Marc-André Lureau wrote:
> Hi
>
> On Tue, Oct 16, 2018 at 4:14 PM Daniel P. Berrangé
> wrote:
> > > > It just reinvents the chardev unix socket syntax, but in a
> > > > different adhoc manner, which is repeating the mistake we have
> > > > made time & ag
Hi
On Tue, Oct 16, 2018 at 4:14 PM Daniel P. Berrangé wrote:
> > > It just reinvents the chardev unix socket syntax, but in a
> > > different adhoc manner, which is repeating the mistake we have
> > > made time & again in QEMU. Using QAPI we can directly accept
> > > the ChardevSocket syntax we a
On Tue, Oct 16, 2018 at 02:47:12PM +0400, Marc-André Lureau wrote:
> Hi
>
> On Fri, Oct 12, 2018 at 1:56 PM Daniel P. Berrangé
> wrote:
> >
> > On Fri, Oct 12, 2018 at 01:43:39PM +0400, Marc-André Lureau wrote:
> > > Hi
> > >
> > > On Thu, Oct 11, 2018 at 7:49 PM Daniel P. Berrangé
> > > wrote
Hi
On Fri, Oct 12, 2018 at 1:56 PM Daniel P. Berrangé wrote:
>
> On Fri, Oct 12, 2018 at 01:43:39PM +0400, Marc-André Lureau wrote:
> > Hi
> >
> > On Thu, Oct 11, 2018 at 7:49 PM Daniel P. Berrangé
> > wrote:
> > >
> > > Adding Markus since we're talking about new CLI argument and capability
>
On Fri, Oct 12, 2018 at 12:23:11PM +0200, Gerd Hoffmann wrote:
> Hi,
>
> > Note, I can't remember what Markus had proposed for CLI arguments in
> > QAPI, so I invented something arbitary but plausible.
>
> Using qapi visitors to parse the command line. Used by -blockdev and
> -display (and may
Hi,
> Note, I can't remember what Markus had proposed for CLI arguments in
> QAPI, so I invented something arbitary but plausible.
Using qapi visitors to parse the command line. Used by -blockdev and
-display (and maybe others meanwhile). See parse_display_qapi().
I think Daniels suggestion
On Fri, Oct 12, 2018 at 01:43:39PM +0400, Marc-André Lureau wrote:
> Hi
>
> On Thu, Oct 11, 2018 at 7:49 PM Daniel P. Berrangé
> wrote:
> >
> > Adding Markus since we're talking about new CLI argument and capability
> > reporting standards.
> >
> > On Fri, Sep 14, 2018 at 05:52:30PM +0400, Marc-
Hi
On Thu, Oct 11, 2018 at 7:49 PM Daniel P. Berrangé wrote:
>
> Adding Markus since we're talking about new CLI argument and capability
> reporting standards.
>
> On Fri, Sep 14, 2018 at 05:52:30PM +0400, Marc-André Lureau wrote:
> > As discussed during "[PATCH v4 00/29] vhost-user for input & G
On Thu, Oct 11, 2018 at 04:48:34PM +0100, Daniel P. Berrangé wrote:
> Adding Markus since we're talking about new CLI argument and capability
> reporting standards.
>
> On Fri, Sep 14, 2018 at 05:52:30PM +0400, Marc-André Lureau wrote:
> > As discussed during "[PATCH v4 00/29] vhost-user for input
Adding Markus since we're talking about new CLI argument and capability
reporting standards.
On Fri, Sep 14, 2018 at 05:52:30PM +0400, Marc-André Lureau wrote:
> As discussed during "[PATCH v4 00/29] vhost-user for input & GPU"
> review, let's define a common set of backend conventions to help wit
On Sat, Oct 06, 2018 at 02:32:45AM +0400, Marc-André Lureau wrote:
> Hi
>
> On Fri, Oct 5, 2018 at 7:59 PM Hoffmann, Gerd wrote:
> >
> > Hi,
> >
> > > For example, "virgl" support may not be implemented. This
> > > --print-capabilities is a simple way to check what the backend
> > > implements.
Hi
On Fri, Oct 5, 2018 at 7:59 PM Hoffmann, Gerd wrote:
>
> Hi,
>
> > For example, "virgl" support may not be implemented. This
> > --print-capabilities is a simple way to check what the backend
> > implements.
>
> What is the expected behavior in case virgl is implemented by the
> backend, but
Hi,
> For example, "virgl" support may not be implemented. This
> --print-capabilities is a simple way to check what the backend
> implements.
What is the expected behavior in case virgl is implemented by the
backend, but not available (due to lack of 3d hardware in the host for
example) ?
che
Hi
On Fri, Oct 5, 2018 at 5:51 PM Ján Tomko wrote:
>
> On Fri, Sep 14, 2018 at 05:52:30PM +0400, Marc-André Lureau wrote:
> >As discussed during "[PATCH v4 00/29] vhost-user for input & GPU"
> >review, let's define a common set of backend conventions to help with
> >management layer implementatio
On Fri, Sep 14, 2018 at 05:52:30PM +0400, Marc-André Lureau wrote:
As discussed during "[PATCH v4 00/29] vhost-user for input & GPU"
review, let's define a common set of backend conventions to help with
management layer implementation, and interoperability.
v2:
- drop --pidfile
- add some notes
As discussed during "[PATCH v4 00/29] vhost-user for input & GPU"
review, let's define a common set of backend conventions to help with
management layer implementation, and interoperability.
v2:
- drop --pidfile
- add some notes about daemonizing & stdin/out/err
Cc: libvir-l...@redhat.com
Cc: G
17 matches
Mail list logo
