From: "Enrico Weigelt, metux IT consult" <lkml@metux.net>
To: Hao Chen <chenhaosjtuacm@google.com>,
Stefan Hajnoczi <stefanha@redhat.com>
Cc: virtio-dev@lists.oasis-open.org
Subject: Re: [virtio-dev] [PATCH] Add virtio parameter server device specification
Date: Fri, 4 Jun 2021 12:50:56 +0200 [thread overview]
Message-ID: <ea3a5d06-d18b-ba44-f6e9-224eaebfdf95@metux.net> (raw)
In-Reply-To: <CABATKF-t-xfj0cTa6zsnKJwLbXUCLaSZOqUWXDEOfKpR3KCPgw@mail.gmail.com>
On 02.06.21 22:09, Hao Chen wrote:
> We can use any protocol to implement this, and publish it somewhere, but it
> does not carry the same weight as putting it in the virtio spec. It is
> easier to say
> "we use virtio, and for this device we use virtio-xxx device", but it
> would be weird to
> say "we use virtio, but for this device, we use vsock+some other non-standard
> protocol, please support this or you will break the compatibility".
Why not directly putting 9P links into virtio devices ?
In both cases we still have the problem knowing the actual meaning of
the individual parameters. Not so different from some raw IO space
(just a bit easier to parse).
I believe we need some layer above for describing the actual meanings.
--mtx
--
---
Hinweis: unverschlüsselte E-Mails können leicht abgehört und manipuliert
werden ! Für eine vertrauliche Kommunikation senden Sie bitte ihren
GPG/PGP-Schlüssel zu.
---
Enrico Weigelt, metux IT consult
Free software and Linux embedded engineering
info@metux.net -- +49-151-27565287
---------------------------------------------------------------------
To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org
next prev parent reply other threads:[~2021-06-04 10:51 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-21 0:33 [virtio-dev] [PATCH] Add virtio parameter server device specification Hao Chen
2021-04-30 10:55 ` Cornelia Huck
2021-05-07 23:06 ` Hao Chen
2021-05-11 9:24 ` Cornelia Huck
2021-05-13 14:46 ` Stefan Hajnoczi
2021-05-17 19:28 ` Hao Chen
[not found] ` <20210517193030.1568902-1-chenhaosjtuacm@google.com>
2021-05-17 19:32 ` [virtio-dev] [PATCH v2] " Hao Chen
[not found] ` <20210517193617.1576401-1-chenhaosjtuacm@google.com>
2021-05-17 19:37 ` [virtio-dev] Fwd: [PATCH v3] " Hao Chen
2021-05-19 17:01 ` [virtio-dev] " Cornelia Huck
2021-05-18 6:02 ` [virtio-dev] [PATCH] " Enrico Weigelt, metux IT consult
2021-05-18 21:56 ` Hao Chen
2021-06-02 13:48 ` Enrico Weigelt, metux IT consult
2021-06-02 20:09 ` Hao Chen
2021-06-04 10:50 ` Enrico Weigelt, metux IT consult [this message]
2021-06-09 20:30 ` Hao Chen
2021-06-10 16:06 ` Enrico Weigelt, metux IT consult
2021-06-10 23:15 ` Hao Chen
[not found] ` <20210610231954.2937837-1-chenhaosjtuacm@google.com>
2021-06-10 23:20 ` [virtio-dev] Re: [PATCH v4] " Hao Chen
2021-06-11 18:44 ` Hao Chen
2021-09-08 20:42 ` Hao Chen
[not found] ` <CABATKF9kqVOeR44vcTH_aw5Sx9geT0-gVpyqngcAwnkcxVN35Q@mail.gmail.com>
2021-10-04 18:30 ` Hao Chen
2021-05-24 14:37 ` [virtio-dev] [PATCH] " Stefan Hajnoczi
2021-05-24 18:45 ` Hao Chen
2021-05-25 16:56 ` Stefan Hajnoczi
2021-06-09 9:12 ` Stefan Hajnoczi
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=ea3a5d06-d18b-ba44-f6e9-224eaebfdf95@metux.net \
--to=lkml@metux.net \
--cc=chenhaosjtuacm@google.com \
--cc=stefanha@redhat.com \
--cc=virtio-dev@lists.oasis-open.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.