, Jun 15, 2021 at 5:04 AM Enrico Weigelt, metux IT consult
wrote:
>
> On 15.06.21 01:28, Hao Chen wrote:
>
> Hi,
>
> > -- Forwarded message -
> > From: Hao Chen
> > Date: Mon, Jun 14, 2021 at 4:26 PM
> > Subject: [PATCH v1] Add virtio a
-- Forwarded message -
From: Hao Chen
Date: Mon, Jun 14, 2021 at 4:26 PM
Subject: [PATCH v1] Add virtio audio policy device specification
To:
This patch includes a new device for coordinating audio among mutliple
VMs.
Signed-off-by: Hao Chen
---
conformance.tex | 18
On Thu, Jun 10, 2021 at 4:19 PM Hao Chen wrote:
>
> This patch introduces a new type of device: parameter server. The device
> acts as a key-value store and the driver can read from, write to or
> subscribe to the properties in the server.
>
> Signed-off-by: Hao Chen
> -
I am not familar with 9P, but in our case we don't need to
launch
1000+ threads to read on files or open 1000+ fds to poll on them (we
literally
have that many properties!). We just process the data from the eventq. Also,
by using a single eventq, we are free from maintaining a data structure li
On Thu, Jun 10, 2021 at 4:19 PM Hao Chen wrote:
> This patch introduces a new type of device: parameter server. The device
> acts as a key-value store and the driver can read from, write to or
> subscribe to the properties in the server.
>
> Signed-off-by: Hao Chen
> ---
our case, so we abandoned this
idea.
On Fri, Jun 4, 2021 at 3:50 AM Enrico Weigelt, metux IT consult <
l...@metux.net> wrote:
> 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 ca
a pipe to the car bus (e.g., power management).
Hao
On Mon, May 17, 2021 at 11:02 PM Enrico Weigelt, metux IT consult
wrote:
>
> On 17.05.21 21:28, Hao Chen wrote:
> > The reason for defining a virtio-parameter-server device is we are
> > interacting
> > with some devic
e-readable// ?
If I understand correctly, the driver need to fill the virtqueues no
matter who is the
reader, so "device-readable" is necessary here. What do you think?
Thanks,
Hao
On Fri, Apr 30, 2021 at 3:55 AM Cornelia Huck wrote:
>
> On Tue, 20 Apr 2021 17:33:17 -0700
This patch introduces a new type of device: parameter server. The device
acts as a key-value store and the driver can read from, write to or
subscribe to the properties in the server.
Signed-off-by: Hao Chen
---
conformance.tex | 26 ++-
content.tex | 1 +
virtio-ps.tex | 197
ntation.
Thanks,
Hao
On Thu, May 13, 2021 at 7:46 AM Stefan Hajnoczi wrote:
>
> On Tue, Apr 20, 2021 at 05:33:17PM -0700, Hao Chen wrote:
> > This patch introduces a new type of device: parameter server. The device
> > acts as a key-value store and the driver can read fr
This patch introduces a new type of device: parameter server. The device
acts as a key-value store and the driver can read from, write to or
subscribe to the properties in the server.
Signed-off-by: Hao Chen
---
conformance.tex | 26 +--
content.tex | 1 +
virtio-ps.tex | 188
than writing it somewhere in
the spec.
On Mon, May 24, 2021 at 7:38 AM Stefan Hajnoczi wrote:
>
> On Mon, May 17, 2021 at 12:28:14PM -0700, Hao Chen wrote:
> > > Can you share a bit about the reason for defining a new VIRTIO device
> > > instead of running an existing key
> If your goal is just to have a standard protocol then I think you can make
> it much easier for others to implement by publishing your own protocol
> spec that runs over a vsock socket.
> If its just reading / setting some kind of "variables" via some path
> name, why not using 9P for that ?
Use device ID 37
Signed-off-by: Hao Chen
---
content.tex | 2 ++
1 file changed, 2 insertions(+)
diff --git a/content.tex b/content.tex
index b72bad0..b88e606 100644
--- a/content.tex
+++ b/content.tex
@@ -2870,6 +2870,8 @@ \chapter{Device Types}\label{sec:Device Types}
\hline
36
Use device ID 39
Signed-off-by: Hao Chen
---
content.tex | 2 ++
1 file changed, 2 insertions(+)
diff --git a/content.tex b/content.tex
index b72bad0..72cb32d 100644
--- a/content.tex
+++ b/content.tex
@@ -2870,6 +2870,8 @@ \chapter{Device Types}\label{sec:Device Types}
\hline
36
GitHub issue updated
On Tue, Apr 6, 2021 at 3:09 AM Cornelia Huck wrote:
>
> On Tue, 30 Mar 2021 12:34:19 -0700
> Hao Chen wrote:
>
> > Use device ID 38
> >
> > Signed-off-by: Hao Chen
> > ---
> > content.tex | 2 ++
> > 1 file changed, 2
Use device ID 38
Signed-off-by: Hao Chen
---
content.tex | 2 ++
1 file changed, 2 insertions(+)
diff --git a/content.tex b/content.tex
index b72bad0..cc292b3 100644
--- a/content.tex
+++ b/content.tex
@@ -2870,6 +2870,8 @@ \chapter{Device Types}\label{sec:Device Types}
\hline
36
Use device ID 36
Signed-off-by: Hao Chen
---
content.tex | 2 ++
1 file changed, 2 insertions(+)
diff --git a/content.tex b/content.tex
index 620c0e2..6bfbba1 100644
--- a/content.tex
+++ b/content.tex
@@ -2846,6 +2846,8 @@ Device ID & Virtio Device\\
\hline
35 &
Use device ID 36
---
content.tex | 2 ++
1 file changed, 2 insertions(+)
diff --git a/content.tex b/content.tex
index 620c0e2..6bfbba1 100644
--- a/content.tex
+++ b/content.tex
@@ -2846,6 +2846,8 @@ Device ID & Virtio Device\\
\hline
35 & Watchdog \\
\hline
+36 &
This patch introduces a new type of device: parameter server. The device
acts as a key-value store and the driver can read from, write to or
subscribe to the properties in the server.
Signed-off-by: Hao Chen
---
conformance.tex | 26 +--
content.tex | 1 +
virtio-ps.tex | 188
about
that. I think it will be great if the device can allocate buffers, but
I didn't see that in the spec. I wonder what will be the current
solution here.
Thanks!
Hao
On Fri, Jun 11, 2021 at 11:44 AM Hao Chen wrote:
>
> On Thu, Jun 10, 2021 at 4:19 PM Hao Chen wrote:
> >
> > Thi
Hi folks,
Could anyone please help us figure out how to allocate the buffer when the
size of the to-be-sent values are unknown?
Thanks!
Hao
On Mon, Oct 4, 2021 at 11:25 AM Hao Chen wrote:
> -- Forwarded message -
> From: Hao Chen
> Date: Wed, Sep 8, 2021 at 1:42 PM
22 matches
Mail list logo
