Re: [PATCH v5 0/8] chardev: implement backend chardev multiplexing

2024-10-31 Thread Marc-André Lureau
Hi Roman On Thu, Oct 31, 2024 at 3:12 PM Roman Penyaev wrote: > Hi Marc-André, > > In this 5th version of the mux-be series it seems I addressed all the > comments and concerns. Could you please take a look once again? > > I am not sure adding a "mux-be-id" option to all chardevs is the way to g

Re: [PATCH v5 0/8] chardev: implement backend chardev multiplexing

2024-10-31 Thread Roman Penyaev
On Thu, Oct 31, 2024 at 12:34 PM Marc-André Lureau wrote: > > Hi Roman > > On Thu, Oct 31, 2024 at 3:12 PM Roman Penyaev wrote: >> >> Hi Marc-André, >> >> In this 5th version of the mux-be series it seems I addressed all the >> comments and concerns. Could you please take a look once again? >> >

Re: [PATCH v5 0/8] chardev: implement backend chardev multiplexing

2024-10-31 Thread Roman Penyaev
Hi Marc-André, In this 5th version of the mux-be series it seems I addressed all the comments and concerns. Could you please take a look once again? -- Roman On Thu, Oct 17, 2024 at 4:45 PM Roman Penyaev wrote: > > Mux is a character backend (host side) device, which multiplexes > multiple fron

[PATCH v5 0/8] chardev: implement backend chardev multiplexing

2024-10-17 Thread Roman Penyaev
Mux is a character backend (host side) device, which multiplexes multiple frontends with one backend device. The following is a few lines from the QEMU manpage [1]: A multiplexer is a "1:N" device, and here the "1" end is your specified chardev backend, and the "N" end is the various parts o