From: "Alex Bennée" <alex.bennee@linaro.org>
To: Christopher Clark <christopher.w.clark@gmail.com>
Cc: "AKASHI Takahiro" <takahiro.akashi@linaro.org>,
"Wei Chen" <Wei.Chen@arm.com>, "Paul Durrant" <paul@xen.org>,
"Stratos Mailing List" <stratos-dev@op-lists.linaro.org>,
virtio-dev@lists.oasis-open.org,
"Stefano Stabellini" <sstabellini@kernel.org>,
"Jan Kiszka" <jan.kiszka@siemens.com>,
"Arnd Bergmann" <arnd.bergmann@linaro.org>,
"Juergen Gross" <jgross@suse.com>,
"Julien Grall" <julien@xen.org>,
"Carl van Schaik" <cvanscha@qti.qualcomm.com>,
"Bertrand Marquis" <Bertrand.Marquis@arm.com>,
"Stefan Hajnoczi" <stefanha@redhat.com>,
"Artem Mygaiev" <Artem_Mygaiev@epam.com>,
Xen-devel <xen-devel@lists.xen.org>,
"Oleksandr Tyshchenko" <olekstysh@gmail.com>,
"Oleksandr Tyshchenko" <Oleksandr_Tyshchenko@epam.com>,
"Elena Afanasova" <eafanasova@gmail.com>,
"James McKenzie" <james@bromium.com>,
"Andrew Cooper" <andrew.cooper3@citrix.com>,
"Rich Persaud" <persaur@gmail.com>,
"Daniel Smith" <dpsmith@apertussolutions.com>,
"Jason Andryuk" <jandryuk@gmail.com>,
"eric chanudet" <eric.chanudet@gmail.com>,
"Roger Pau Monné" <roger.pau@citrix.com>
Subject: [virtio-dev] Re: [Stratos-dev] Enabling hypervisor agnosticism for VirtIO backends
Date: Fri, 10 Sep 2021 10:35:52 +0100 [thread overview]
Message-ID: <87o890wyqe.fsf@linaro.org> (raw)
In-Reply-To: <CACMJ4GaJyAnguzAEH87DSNN_+GhEa5jRbw11hVj-yWMAXx8V7w@mail.gmail.com>
Christopher Clark <christopher.w.clark@gmail.com> writes:
> On Sun, Sep 5, 2021 at 7:24 PM AKASHI Takahiro via Stratos-dev <stratos-dev@op-lists.linaro.org> wrote:
>
> Alex,
>
> On Fri, Sep 03, 2021 at 10:28:06AM +0100, Alex Benn??e wrote:
<snip>
>
> In configuration phase of virtio device, the latency won't be a big matter.
> In device operations (i.e. read/write to block devices), if we can
> resolve 'mmap' issue, as Oleksandr is proposing right now, the only issue is
> how efficiently we can deliver notification to the opposite side. Right?
> And this is a very common problem whatever approach we would take.
>
> Anyhow, if we do care the latency in my approach, most of virtio-proxy-
> related code can be re-implemented just as a stub (or shim?) library
> since the protocols are defined as RPCs.
> In this case, however, we would lose the benefit of providing "single binary"
> BE.
> (I know this is is an arguable requirement, though.)
The proposal for a single binary would always require something to shim
between hypervisors. This is still an area of discussion though. Having
a compile time selectable approach is practically unavoidable for "bare
metal" backends though because there are no other processes/layers that
communication with the hypervisor can be delegated to.
>
> # Would we better discuss what "hypervisor-agnosticism" means?
>
> Is there a call that you could recommend that we join to discuss this and the topics of this thread?
> There is definitely interest in pursuing a new interface for Argo that can be implemented in other hypervisors and enable guest binary
> portability between them, at least on the same hardware architecture,
> with VirtIO transport as a primary use case.
There is indeed ;-)
We have a regular open call every two week for the Stratos project which
you are welcome to attend. You can find the details on the project
overview page:
https://linaro.atlassian.net/wiki/spaces/STR/overview
we regularly have teams from outside the project present their work as well.
> The notes from the Xen Summit Design Session on VirtIO Cross-Project BoF for Xen and Guest OS, which include context about the
> several separate approaches to VirtIO on Xen, have now been posted here:
> https://lists.xenproject.org/archives/html/xen-devel/2021-09/msg00472.html
Thanks for the link - looks like a very detailed summary.
>
> Christopher
>
>
> -Takahiro Akashi
--
Alex Bennée
---------------------------------------------------------------------
To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org
WARNING: multiple messages have this Message-ID (diff)
From: "Alex Bennée" <alex.bennee@linaro.org>
To: Christopher Clark <christopher.w.clark@gmail.com>
Cc: "AKASHI Takahiro" <takahiro.akashi@linaro.org>,
"Wei Chen" <Wei.Chen@arm.com>, "Paul Durrant" <paul@xen.org>,
"Stratos Mailing List" <stratos-dev@op-lists.linaro.org>,
virtio-dev@lists.oasis-open.org,
"Stefano Stabellini" <sstabellini@kernel.org>,
"Jan Kiszka" <jan.kiszka@siemens.com>,
"Arnd Bergmann" <arnd.bergmann@linaro.org>,
"Juergen Gross" <jgross@suse.com>,
"Julien Grall" <julien@xen.org>,
"Carl van Schaik" <cvanscha@qti.qualcomm.com>,
"Bertrand Marquis" <Bertrand.Marquis@arm.com>,
"Stefan Hajnoczi" <stefanha@redhat.com>,
"Artem Mygaiev" <Artem_Mygaiev@epam.com>,
Xen-devel <xen-devel@lists.xen.org>,
"Oleksandr Tyshchenko" <olekstysh@gmail.com>,
"Oleksandr Tyshchenko" <Oleksandr_Tyshchenko@epam.com>,
"Elena Afanasova" <eafanasova@gmail.com>,
"James McKenzie" <james@bromium.com>,
"Andrew Cooper" <andrew.cooper3@citrix.com>,
"Rich Persaud" <persaur@gmail.com>,
"Daniel Smith" <dpsmith@apertussolutions.com>,
"Jason Andryuk" <jandryuk@gmail.com>,
"eric chanudet" <eric.chanudet@gmail.com>,
"Roger Pau Monné" <roger.pau@citrix.com>
Subject: Re: [Stratos-dev] Enabling hypervisor agnosticism for VirtIO backends
Date: Fri, 10 Sep 2021 10:35:52 +0100 [thread overview]
Message-ID: <87o890wyqe.fsf@linaro.org> (raw)
In-Reply-To: <CACMJ4GaJyAnguzAEH87DSNN_+GhEa5jRbw11hVj-yWMAXx8V7w@mail.gmail.com>
Christopher Clark <christopher.w.clark@gmail.com> writes:
> On Sun, Sep 5, 2021 at 7:24 PM AKASHI Takahiro via Stratos-dev <stratos-dev@op-lists.linaro.org> wrote:
>
> Alex,
>
> On Fri, Sep 03, 2021 at 10:28:06AM +0100, Alex Benn??e wrote:
<snip>
>
> In configuration phase of virtio device, the latency won't be a big matter.
> In device operations (i.e. read/write to block devices), if we can
> resolve 'mmap' issue, as Oleksandr is proposing right now, the only issue is
> how efficiently we can deliver notification to the opposite side. Right?
> And this is a very common problem whatever approach we would take.
>
> Anyhow, if we do care the latency in my approach, most of virtio-proxy-
> related code can be re-implemented just as a stub (or shim?) library
> since the protocols are defined as RPCs.
> In this case, however, we would lose the benefit of providing "single binary"
> BE.
> (I know this is is an arguable requirement, though.)
The proposal for a single binary would always require something to shim
between hypervisors. This is still an area of discussion though. Having
a compile time selectable approach is practically unavoidable for "bare
metal" backends though because there are no other processes/layers that
communication with the hypervisor can be delegated to.
>
> # Would we better discuss what "hypervisor-agnosticism" means?
>
> Is there a call that you could recommend that we join to discuss this and the topics of this thread?
> There is definitely interest in pursuing a new interface for Argo that can be implemented in other hypervisors and enable guest binary
> portability between them, at least on the same hardware architecture,
> with VirtIO transport as a primary use case.
There is indeed ;-)
We have a regular open call every two week for the Stratos project which
you are welcome to attend. You can find the details on the project
overview page:
https://linaro.atlassian.net/wiki/spaces/STR/overview
we regularly have teams from outside the project present their work as well.
> The notes from the Xen Summit Design Session on VirtIO Cross-Project BoF for Xen and Guest OS, which include context about the
> several separate approaches to VirtIO on Xen, have now been posted here:
> https://lists.xenproject.org/archives/html/xen-devel/2021-09/msg00472.html
Thanks for the link - looks like a very detailed summary.
>
> Christopher
>
>
> -Takahiro Akashi
--
Alex Bennée
next prev parent reply other threads:[~2021-09-10 9:45 UTC|newest]
Thread overview: 66+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-04 9:04 [virtio-dev] Enabling hypervisor agnosticism for VirtIO backends Alex Bennée
2021-08-04 19:20 ` Stefano Stabellini
2021-08-11 6:27 ` AKASHI Takahiro
2021-08-14 15:37 ` Oleksandr Tyshchenko
2021-08-16 10:04 ` Wei Chen
2021-08-17 8:07 ` AKASHI Takahiro
2021-08-17 8:39 ` Wei Chen
2021-08-18 5:38 ` AKASHI Takahiro
2021-08-18 8:35 ` Wei Chen
2021-08-20 6:41 ` AKASHI Takahiro
2021-08-26 9:40 ` AKASHI Takahiro
2021-08-26 12:10 ` Wei Chen
2021-08-30 19:36 ` Christopher Clark
2021-08-30 19:53 ` [virtio-dev] " Christopher Clark
2021-08-30 19:53 ` Christopher Clark
2021-09-02 7:19 ` AKASHI Takahiro
2021-09-07 0:57 ` [virtio-dev] " Christopher Clark
2021-09-07 0:57 ` Christopher Clark
2021-09-07 11:55 ` AKASHI Takahiro
2021-09-07 18:09 ` [virtio-dev] " Christopher Clark
2021-09-07 18:09 ` Christopher Clark
2021-09-10 3:12 ` AKASHI Takahiro
2021-08-31 6:18 ` AKASHI Takahiro
2021-09-01 11:12 ` Wei Chen
2021-09-01 12:29 ` AKASHI Takahiro
2021-09-01 16:26 ` Oleksandr Tyshchenko
2021-09-02 1:30 ` Wei Chen
2021-09-02 1:50 ` Wei Chen
[not found] ` <0100017b33e585a5-06d4248e-b1a7-485e-800c-7ead89e5f916-000000@email.amazonses.com>
2021-08-12 7:55 ` [Stratos-dev] " François Ozog
2021-08-13 5:10 ` AKASHI Takahiro
2021-09-01 8:57 ` [virtio-dev] " Alex Bennée
2021-09-01 8:57 ` Alex Bennée
2021-08-17 10:41 ` [virtio-dev] " Stefan Hajnoczi
2021-08-17 10:41 ` Stefan Hajnoczi
2021-08-23 6:25 ` AKASHI Takahiro
2021-08-23 9:58 ` [virtio-dev] " Stefan Hajnoczi
2021-08-23 9:58 ` Stefan Hajnoczi
2021-08-25 10:29 ` AKASHI Takahiro
2021-08-25 15:02 ` [virtio-dev] " Stefan Hajnoczi
2021-08-25 15:02 ` Stefan Hajnoczi
2021-09-01 12:53 ` [virtio-dev] " Alex Bennée
2021-09-01 12:53 ` Alex Bennée
2021-09-02 9:12 ` [virtio-dev] " Stefan Hajnoczi
2021-09-02 9:12 ` Stefan Hajnoczi
2021-09-03 8:06 ` AKASHI Takahiro
2021-09-03 9:28 ` [virtio-dev] " Alex Bennée
2021-09-03 9:28 ` Alex Bennée
2021-09-06 2:23 ` AKASHI Takahiro
2021-09-07 2:41 ` [virtio-dev] Re: [Stratos-dev] " Christopher Clark
2021-09-07 2:41 ` Christopher Clark
2021-09-10 2:50 ` AKASHI Takahiro
2021-09-10 9:35 ` Alex Bennée [this message]
2021-09-10 9:35 ` Alex Bennée
2021-09-13 23:51 ` Stefano Stabellini
2021-09-14 6:08 ` [Stratos-dev] " François Ozog
2021-09-14 14:25 ` [virtio-dev] " Alex Bennée
2021-09-14 14:25 ` Alex Bennée
2021-09-14 17:38 ` [Stratos-dev] " Trilok Soni
2021-09-15 3:29 ` Stefano Stabellini
2021-09-15 23:50 ` Trilok Soni
2021-09-16 2:11 ` Stefano Stabellini
2021-08-05 15:48 ` [virtio-dev] " Stefan Hajnoczi
2021-08-19 9:11 ` [virtio-dev] " Matias Ezequiel Vara Larsen
[not found] ` <20210820060558.GB13452@laputa>
2021-08-21 14:08 ` Matias Ezequiel Vara Larsen
[not found] ` <20210823012029.GB40863@laputa>
2021-10-04 11:33 ` Matias Ezequiel Vara Larsen
2021-09-01 8:43 ` Alex Bennée
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=87o890wyqe.fsf@linaro.org \
--to=alex.bennee@linaro.org \
--cc=Artem_Mygaiev@epam.com \
--cc=Bertrand.Marquis@arm.com \
--cc=Oleksandr_Tyshchenko@epam.com \
--cc=Wei.Chen@arm.com \
--cc=andrew.cooper3@citrix.com \
--cc=arnd.bergmann@linaro.org \
--cc=christopher.w.clark@gmail.com \
--cc=cvanscha@qti.qualcomm.com \
--cc=dpsmith@apertussolutions.com \
--cc=eafanasova@gmail.com \
--cc=eric.chanudet@gmail.com \
--cc=james@bromium.com \
--cc=jan.kiszka@siemens.com \
--cc=jandryuk@gmail.com \
--cc=jgross@suse.com \
--cc=julien@xen.org \
--cc=olekstysh@gmail.com \
--cc=paul@xen.org \
--cc=persaur@gmail.com \
--cc=roger.pau@citrix.com \
--cc=sstabellini@kernel.org \
--cc=stefanha@redhat.com \
--cc=stratos-dev@op-lists.linaro.org \
--cc=takahiro.akashi@linaro.org \
--cc=virtio-dev@lists.oasis-open.org \
--cc=xen-devel@lists.xen.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.