From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: virtio-dev-return-6896-cohuck=redhat.com@lists.oasis-open.org Sender: List-Post: List-Help: List-Unsubscribe: List-Subscribe: Received: from lists.oasis-open.org (oasis-open.org [10.110.1.242]) by lists.oasis-open.org (Postfix) with ESMTP id BE58A985FC3 for ; Fri, 6 Mar 2020 20:34:16 +0000 (UTC) References: <874kv15o4q.fsf@linaro.org> <20200306191427.GA132@matiasv.localdomain> From: Alex =?utf-8?Q?Benn=C3=A9e?= In-reply-to: <20200306191427.GA132@matiasv.localdomain> Date: Fri, 06 Mar 2020 20:34:12 +0000 Message-ID: <87y2sd43zv.fsf@linaro.org> MIME-Version: 1.0 Subject: Re: [virtio-dev] Backend libraries for VirtIO device emulation Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable To: Matias Ezequiel Vara Larsen Cc: virtio-dev@lists.oasis-open.org List-ID: Matias Ezequiel Vara Larsen writes: > Hello Alex, > On Fri, Mar 06, 2020 at 06:33:57PM +0000, Alex Benn=C3=A9e wrote: >> Hi, >>=20 >> So the context of my question is what sort of common software layer is >> required to implement a virtio backend entirely in userspace? >>=20 >> Thoughts? > > I am currently investigating the use of metamodeling to capture virtio > concepts. The work is still a draft but you can give a look at > https://github.com/MatiasVara/virtioml. One of the ideas is to base on a > metamodel to generate the code for different targets, e.g., rust, > c, etc. For the moment, I just played by generating the c header. This > could be extended to other languages. Thanks for the pointer, I shall have a look. --=20 Alex Benn=C3=A9e --------------------------------------------------------------------- To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org