* Stefan Hajnoczi (stefa...@redhat.com) wrote:
> On Tue, Sep 06, 2022 at 06:33:36PM +0100, Dr. David Alan Gilbert wrote:
> > * Stefan Hajnoczi (stefa...@redhat.com) wrote:
> > > On Sat, Sep 03, 2022 at 07:43:08AM +, Alyssa Ross wrote:
> > > > Hi Alex and everyone
her constraints we need to take into account?
> - can we leverage existing sub-systems to build this support?
>
> I look forward to your thoughts ;-)
>
> --
> Alex Bennée
>
> -
> To unsubscribe, e-mail: virti
* Jason Wang (jasow...@redhat.com) wrote:
>
> 在 2021/8/4 下午5:07, Dr. David Alan Gilbert 写道:
> > * Jason Wang (jasow...@redhat.com) wrote:
> > > 在 2021/8/3 下午8:22, Dr. David Alan Gilbert 写道:
> > > > * Jason Wang (jasow...@redhat.com) wrote:
> > >
* Jason Wang (jasow...@redhat.com) wrote:
>
> 在 2021/8/3 下午8:22, Dr. David Alan Gilbert 写道:
> > * Jason Wang (jasow...@redhat.com) wrote:
> > > 在 2021/8/3 下午6:37, Stefan Hajnoczi 写道:
> > > > On Tue, Aug 03, 2021 at 02:33:20PM +0800, Jason Wang wrote:
> > >
Subscribe: virtio-comment-subscr...@lists.oasis-open.org
> Unsubscribe: virtio-comment-unsubscr...@lists.oasis-open.org
> List help: virtio-comment-h...@lists.oasis-open.org
> List archive: https://lists.oasis-open.org/archives/virtio-comment/
> Feedback License: https://www.o
t;
> -------------
> To unsubscribe, e-mail: virtio-dev-unsubscr...@lists.oasis-open.org
> For additional commands, e-mail: virtio-dev-h...@lists.oasis-open.org
>
--
Dr. David Alan Gilbert / dgilb...@redhat.com / Manchester, UK
-
To unsubscribe, e-mail: virtio-dev-unsubscr...@lists.oasis-open.org
For additional commands, e-mail: virtio-dev-h...@lists.oasis-open.org
* Gerd Hoffmann (kra...@redhat.com) wrote:
> On Mon, Aug 10, 2020 at 05:41:13PM +0100, Dr. David Alan Gilbert wrote:
> > Hi,
> > Is there anywhere that virtio has where host/guest copy/paste would
> > fit?
>
> Well, spice supports it, with spice client and spice gu
, if it didn't it could insert a string
of key events.
It probably needs some design to ensure that whatever we have
would work with existing guests and existing transports like VNC.
Dave
--
Dr. David Alan Gilbert / dgilb...@redhat.com / Manchester, UK
entially the signal that the "DONE" value provides. Same thing for
> the status. We shouldn't be able to migrate unless both of these are
> already in the "DONE" state so if anything I wonder if we shouldn't
> have that as the initial state for the device
* Alex Bennée (alex.ben...@linaro.org) wrote:
>
> Dr. David Alan Gilbert writes:
>
> > * Alex Bennée (alex.ben...@linaro.org) wrote:
> >>
> >> Dr. David Alan Gilbert writes:
> >>
> >> > * Alex Bennée (alex.ben...@linaro.org) wrote:
>
* Alex Bennée (alex.ben...@linaro.org) wrote:
>
> Dr. David Alan Gilbert writes:
>
> > * Alex Bennée (alex.ben...@linaro.org) wrote:
> >> Hi,
> >>
> >> So the context of my question is what sort of common software layer is
> >> required
and probably needs more work).
Dave
> Thoughts?
>
> --
> Alex Bennée
>
> -
> To unsubscribe, e-mail: virtio-dev-unsubscr...@lists.oasis-open.org
> For additional commands, e-mail: virtio-d
e Operation / Device Operation:
> Notification Queue}
> +
> +The driver MUST provide buffers of at least \field{notify_buf_size} bytes.
> +
> +The driver SHOULD replenish notification queue buffers sufficiently quickly
> so
> +that there is always at least one available buffer.
> +
> \subsubsection{Device Operation: DAX Window}\label{sec:Device Types / File
> System Device / Device Operation / Device Operation: DAX Window}
>
> FUSE\_READ and FUSE\_WRITE requests transfer file contents between the
> --
> 2.23.0
>
--
Dr. David Alan Gilbert / dgilb...@redhat.com / Manchester, UK
-
To unsubscribe, e-mail: virtio-dev-unsubscr...@lists.oasis-open.org
For additional commands, e-mail: virtio-dev-h...@lists.oasis-open.org
ormance{\section}{Legacy Interface: Transitional Device and
> Transitional Driver Conformance}\label{sec:Conformance / Legacy Interface:
> Transitional Device and Transitional Driver Conformance}
> A conformant implementation MUST be either transitional or
> non-transitional, s
RTIO_F_IOMMU_PLATFORM as the virtio-pci transport tears down the dma
> mappings for the virtqueue entries after command completion.
>
> Comments, suggestions, ideas?
What about not completing the command while the device is using the
memory?
Dave
> cheers,
> Gerd
>
--
Dr. D
places pointers to the memory it wants to share as elements in
the queue?
Dave
> > My question would be "what is the actual problem you are trying to
> > solve?".
>
> Typical use cases center around sharing graphics data between guest
> and host.
>
> cheers
n use so that it can
> make a decision on what to do with the pages now that it knows they
> are unused.
>
> All this is providing is just a report and it is optional if the
> hypervisor will act on it or not. If the hypervisor takes some sort of
> action on the page, then the expect
* Halil Pasic (pa...@linux.ibm.com) wrote:
> On Tue, 10 Sep 2019 14:09:20 +0100
> "Dr. David Alan Gilbert" wrote:
>
> > * Halil Pasic (pa...@linux.ibm.com) wrote:
> > > On Thu, 29 Aug 2019 14:52:06 +0100
> > > Stefan Hajnoczi wrote:
> >
specification would mean if one were to
> implement this in HW it would not work for s390.
>
> I don't have a anything better to propose, so I intend to vote yes
> for this. I just wanted to make sure, we all are aware of the
> consequences.
T
gt; +};
> > > > +\end{lstlisting}
> > > > +
> > > > +The FUSE protocol documented in \hyperref[intro:FUSE]{FUSE} specifies
> > > > the set
> > > > +of request types and thei
* Nikos Dragazis (ndraga...@arrikto.com) wrote:
> On 12/7/19 3:20 μ.μ., Dr. David Alan Gilbert (git) wrote:
> > From: "Dr. David Alan Gilbert"
> >
> > Define 'virtio_pci_cap64' to allow capabilities to describe
> > memory regions larger tha
gt; > transports SCSI commands, virtio-fs transports FUSE requests and the
> > protocol
> > documentation is not duplicated here.
> >
> > The DAX window allows file contents to be accessed directly from shared
> > memory.
> > This eliminates copying of data, red
* Cornelia Huck (coh...@redhat.com) wrote:
> On Fri, 12 Jul 2019 13:20:01 +0100
> "Dr. David Alan Gilbert (git)" wrote:
>
> > From: "Dr. David Alan Gilbert"
> >
> > Define the PCI capability used for enumerating shared memory regions.
From: "Dr. David Alan Gilbert"
Define an MMIO interface to discover and map shared
memory regions.
Signed-off-by: Dr. David Alan Gilbert
Reviewed-by: Stefan Hajnoczi
Reviewed-by: Cornelia Huck
---
content.tex | 30 ++
1 file changed, 30 insertions(+)
From: "Dr. David Alan Gilbert"
Define the requirements and idea behind shared memory regions.
Signed-off-by: Dr. David Alan Gilbert
Reviewed-by: Stefan Hajnoczi
Reviewed-by: Cornelia Huck
---
conformance.tex | 1 +
content.tex | 2 ++
shared-mem
From: "Dr. David Alan Gilbert"
Define the PCI capability used for enumerating shared memory regions.
Signed-off-by: Dr. David Alan Gilbert
---
conformance.tex | 1 +
content.tex | 22 ++
2 files changed, 23 insertions(+)
diff --git a/conformance.tex b/confo
From: "Dr. David Alan Gilbert"
For the virtio-fs device we require multiple large shared memory
regions. Differentiate these by an 'id' field in the base capability.
Signed-off-by: Dr. David Alan Gilbert
Reviewed-by: Cornelia Huck
---
content.tex | 12 ++--
1 file c
From: "Dr. David Alan Gilbert"
Define 'virtio_pci_cap64' to allow capabilities to describe
memory regions larger than, or with an offset larger than 4GiB.
This will be used by the shared memory region capability.
Signed-off-by: Dr. David Alan Gilbert
Reviewed-by: Cor
From: "Dr. David Alan Gilbert"
This series formalises the idea of shared memory regions I'd
previously discussed and is intended for use with virtio-fs.
I've split it into five parts:
a) A general definition of the idea
b) An addition of an 'id' field to allow multipl
* Cornelia Huck (coh...@redhat.com) wrote:
> On Wed, 10 Jul 2019 19:32:11 +0100
> "Dr. David Alan Gilbert (git)" wrote:
>
> > From: "Dr. David Alan Gilbert"
> >
> > Define the PCI capability used for enumerating shared memory regions.
From: "Dr. David Alan Gilbert"
Define an MMIO interface to discover and map shared
memory regions.
Signed-off-by: Dr. David Alan Gilbert
Reviewed-by: Stefan Hajnoczi
Reviewed-by: Cornelia Huck
---
content.tex | 30 ++
1 file changed, 30 insertions(+)
From: "Dr. David Alan Gilbert"
Define the PCI capability used for enumerating shared memory regions.
Signed-off-by: Dr. David Alan Gilbert
---
content.tex | 22 ++
1 file changed, 22 insertions(+)
diff --git a/content.tex b/content.tex
index d481359..1476
From: "Dr. David Alan Gilbert"
Define 'virtio_pci_cap64' to allow capabilities to describe
memory regions larger than, or with an offset larger than 4GiB.
This will be used by the shared memory region capability.
Signed-off-by: Dr. David Alan Gilbert
Reviewed-by: Cor
From: "Dr. David Alan Gilbert"
For the virtio-fs device we require multiple large shared memory
regions. Differentiate these by an 'id' field in the base capability.
Signed-off-by: Dr. David Alan Gilbert
---
content.tex | 12 ++--
1 file changed, 10 insertions(+), 2
From: "Dr. David Alan Gilbert"
Define the requirements and idea behind shared memory regions.
Signed-off-by: Dr. David Alan Gilbert
Reviewed-by: Stefan Hajnoczi
Reviewed-by: Cornelia Huck
---
conformance.tex | 1 +
content.tex | 2 ++
shared-mem
From: "Dr. David Alan Gilbert"
This series formalises the idea of shared memory regions I'd
previously discussed and is intended for use with virtio-fs.
I've split it into five parts:
a) A general definition of the idea
b) An addition of an 'id' field to allow multipl
* Cornelia Huck (coh...@redhat.com) wrote:
> On Thu, 27 Jun 2019 20:28:29 +0100
> "Dr. David Alan Gilbert (git)" wrote:
>
> > From: "Dr. David Alan Gilbert"
> >
> > Define the PCI capability used for enumerating shared memory regions.
* Cornelia Huck (coh...@redhat.com) wrote:
> On Fri, 28 Jun 2019 14:36:14 +0100
> "Dr. David Alan Gilbert" wrote:
>
> > * Cornelia Huck (coh...@redhat.com) wrote:
> > > On Thu, 27 Jun 2019 20:28:27 +0100
> > > "Dr. David Alan Gilbert (git)"
* Cornelia Huck (coh...@redhat.com) wrote:
> On Thu, 27 Jun 2019 20:28:27 +0100
> "Dr. David Alan Gilbert (git)" wrote:
>
> > From: "Dr. David Alan Gilbert"
> >
> > For the virtio-fs device we require multiple large shared memory
> > regio
From: "Dr. David Alan Gilbert"
Define an MMIO interface to discover and map shared
memory regions.
Signed-off-by: Dr. David Alan Gilbert
Reviewed-by: Stefan Hajnoczi
---
content.tex | 30 ++
1 file changed, 30 insertions(+)
diff --git a/content.tex b/c
From: "Dr. David Alan Gilbert"
This series formalises the idea of shared memory regions I'd
previously discussed and is intended for use with virtio-fs.
I've split it into five parts:
a) A general definition of the idea
b) An addition of an 'id' field to allow multipl
From: "Dr. David Alan Gilbert"
Define the PCI capability used for enumerating shared memory regions.
Signed-off-by: Dr. David Alan Gilbert
---
content.tex | 20
1 file changed, 20 insertions(+)
diff --git a/content.tex b/content.tex
index 63e9179..fcf0
From: "Dr. David Alan Gilbert"
For the virtio-fs device we require multiple large shared memory
regions. Differentiate these by an 'id' field in the base capability.
Signed-off-by: Dr. David Alan Gilbert
---
content.tex | 8 +++-
1 file changed, 7 insertions(+), 1 deletion(-)
From: "Dr. David Alan Gilbert"
Define 'virtio_pci_cap64' to allow capabilities to describe
memory regions larger than, or with an offset larger than 4GiB.
This will be used by the shared memory region capability.
Signed-off-by: Dr. David Alan Gilbert
---
content.tex | 17 ++
From: "Dr. David Alan Gilbert"
Define the requirements and idea behind shared memory regions.
Signed-off-by: Dr. David Alan Gilbert
Reviewed-by: Stefan Hajnoczi
---
conformance.tex | 1 +
content.tex | 2 ++
shared-mem.tex | 42 +
* Michael S. Tsirkin (m...@redhat.com) wrote:
> On Wed, Jun 19, 2019 at 05:06:04PM +0100, Dr. David Alan Gilbert wrote:
> > * Michael S. Tsirkin (m...@redhat.com) wrote:
> > > On Wed, Mar 20, 2019 at 12:07:38PM +0000, Dr. David Alan Gilbert (git)
> > > wrote:
> >
more memory
> without any limit.
>
> If we are in a situation where we need to either kill
> the guest or hit swap, none of the choices is good.
There is a bound; it's cache region size / page size - so
that's ~1M mappings worst case (e.g. 4GB cache, 4kB page size)
That limit can be bought down if we impose a larger granularity
somewhere (and the reality is our kernel uses 2MB mapping chunks I
think).
> > We haven't seen catastrophic problems that bring the system to it's
> > knees.
>
> Because you are not running malicious guests?
Hmm, I didn't realise a process having an excessive number of mappings
could harm any other process.
Dave
> > But we're aware that increasing the number VMAs slows down the
> > lookup. There is currently no imposed limit.
> >
> > Ideas have been discussed to avoid using (so many) VMAs but it seems
> > like that will take some time to develop and get upstream. This will
> > not affect the virtio specification because the device interface doesn't
> > need to know about this.
> >
> > Stefan
>
>
> One way to address this is to expose the # of mappings
> in the config space.
--
Dr. David Alan Gilbert / dgilb...@redhat.com / Manchester, UK
-
To unsubscribe, e-mail: virtio-dev-unsubscr...@lists.oasis-open.org
For additional commands, e-mail: virtio-dev-h...@lists.oasis-open.org
* Michael S. Tsirkin (m...@redhat.com) wrote:
> On Mon, Jun 17, 2019 at 02:36:43PM -0400, Michael S. Tsirkin wrote:
> > On Wed, Mar 20, 2019 at 12:07:39PM +0000, Dr. David Alan Gilbert (git)
> > wrote:
> > > From: "Dr. David Alan Gilbert"
> >
* Michael S. Tsirkin (m...@redhat.com) wrote:
> On Wed, Mar 20, 2019 at 12:07:39PM +0000, Dr. David Alan Gilbert (git) wrote:
> > From: "Dr. David Alan Gilbert"
> >
> > Define the PCI capability used for enumerating shared memory regions.
> >
>
* Michael S. Tsirkin (m...@redhat.com) wrote:
> On Wed, Mar 20, 2019 at 12:07:38PM +0000, Dr. David Alan Gilbert (git) wrote:
> > From: "Dr. David Alan Gilbert"
> >
> > Define the requirements and idea behind shared memory regions.
> >
> > Signed-o
/archives/virtio-dev/201904/msg00022.html
(a) is just a reservation - so should be pretty easy?
(b) I've seen other suggested uses, but I don't think I've
seen any other suggestions for changes.
Dave
--
Dr. David Alan Gilbert / dgilb...@redhat.com / Manchester, UK
o vhost-user device spec with the following shared
> memory resources PATCH:
>
> https://lists.oasis-open.org/archives/virtio-dev/201902/msg00142.html
>
> Cc: Dr. David Alan Gilbert
> Signed-off-by: Nikos Dragazis
> ---
> virtio-vhost-user.tex | 17 -
&g
From: "Dr. David Alan Gilbert"
Define the PCI capability used for enumerating shared memory regions.
Signed-off-by: Dr. David Alan Gilbert
Reviewed-by: Stefan Hajnoczi
Reviewed-by: Cornelia Huck
---
content.tex | 37 +
1 file changed, 37
From: "Dr. David Alan Gilbert"
Define an MMIO interface to discover and map shared
memory regions.
Signed-off-by: Dr. David Alan Gilbert
Reviewed-by: Stefan Hajnoczi
---
content.tex | 30 ++
1 file changed, 30 insertions(+)
diff --git a/content.tex b/c
From: "Dr. David Alan Gilbert"
Define the requirements and idea behind shared memory regions.
Signed-off-by: Dr. David Alan Gilbert
Reviewed-by: Stefan Hajnoczi
---
conformance.tex | 1 +
content.tex | 2 ++
shared-mem.tex | 40
3 fil
From: "Dr. David Alan Gilbert"
This series formalises the idea of shared memory regions I'd
previously discussed and is intended for use with virtio-fs.
I've split it into three parts:
a) A general definition of the idea
b) A definition on virtio-pci using the layout
* Stefan Hajnoczi (stefa...@redhat.com) wrote:
> On Mon, Mar 04, 2019 at 01:25:30PM +0000, Dr. David Alan Gilbert (git) wrote:
> > +\begin{lstlisting}
> > +struct virtio_pci_shm_cap {
> > +struct virtio_pci_cap cap;
> > +u32 offset_hi;
> > +
* Stefan Hajnoczi (stefa...@redhat.com) wrote:
> On Mon, Mar 04, 2019 at 01:25:29PM +0000, Dr. David Alan Gilbert (git) wrote:
> > +\subsection{Addressing within regions}\label{sec:Basic Facilities of a
> > Virtio Device / Shared Memory Regions / Addressing within regions }
>
e_start call is made. Guest reporting must be
> disabled before the migration dirty bitmap is synchronized.
>
> Signed-off-by: Wei Wang
> CC: Michael S. Tsirkin
> CC: Dr. David Alan Gilbert
> CC: Juan Quintela
> CC: Peter Xu
> ---
> hw/virtio/virtio-balloon.c
From: "Dr. David Alan Gilbert"
This series formalises the idea of shared memory regions I'd
previously discussed and is intended for use with virtio-fs.
I've split it into three parts:
a) A general definition of the idea
b) A definition on virtio-pci using the layout
From: "Dr. David Alan Gilbert"
Define the requirements and idea behind shared memory regions.
Signed-off-by: Dr. David Alan Gilbert
---
conformance.tex | 1 +
content.tex | 2 ++
shared-mem.tex | 40
3 files changed, 43 insertions(
From: "Dr. David Alan Gilbert"
Define an MMIO interface to discover and map shared
memory regions.
Signed-off-by: Dr. David Alan Gilbert
---
content.tex | 30 ++
1 file changed, 30 insertions(+)
diff --git a/content.tex b/content.tex
index 9838208..7696
From: "Dr. David Alan Gilbert"
Define the PCI capability used for enumerating shared memory regions.
Signed-off-by: Dr. David Alan Gilbert
Reviewed-by: Stefan Hajnoczi
Reviewed-by: Cornelia Huck
---
content.tex | 37 +
1 file changed, 37
* Cornelia Huck (coh...@redhat.com) wrote:
> On Tue, 26 Feb 2019 15:11:34 +
> "Dr. David Alan Gilbert" wrote:
>
> > * Cornelia Huck (coh...@redhat.com) wrote:
> > > On Fri, 22 Feb 2019 11:54:31 +
> > > "Dr. David Alan Gilbert (git)"
* Stefan Hajnoczi (stefa...@redhat.com) wrote:
> On Wed, Feb 27, 2019 at 02:56:52PM +0100, Cornelia Huck wrote:
> > On Mon, 25 Feb 2019 18:45:06 +0000
> > "Dr. David Alan Gilbert" wrote:
> >
> > > * Stefan Hajnoczi (stefa...@redhat.com) wrote:
> > &g
* Cornelia Huck (coh...@redhat.com) wrote:
> On Fri, 22 Feb 2019 11:54:33 +
> "Dr. David Alan Gilbert (git)" wrote:
>
> > From: "Dr. David Alan Gilbert"
> >
> > Define an MMIO interface to enumerate and map shared
> > memory
* Cornelia Huck (coh...@redhat.com) wrote:
> On Fri, 22 Feb 2019 11:54:31 +
> "Dr. David Alan Gilbert (git)" wrote:
>
> > From: "Dr. David Alan Gilbert"
> >
> > Define the requirements and idea behind shared memory regions.
* Stefan Hajnoczi (stefa...@redhat.com) wrote:
> On Fri, Feb 22, 2019 at 11:54:33AM +0000, Dr. David Alan Gilbert (git) wrote:
> > diff --git a/content.tex b/content.tex
> > index 9838208..c3070bd 100644
> > --- a/content.tex
> > +++ b/content.tex
> > @@ -1726,
From: "Dr. David Alan Gilbert"
Define the PCI capability used for enumerating shared memory regions.
Signed-off-by: Dr. David Alan Gilbert
Reviewed-by: Stefan Hajnoczi
---
content.tex | 37 +
1 file changed, 37 insertions(+)
diff --git a/con
From: "Dr. David Alan Gilbert"
Define the requirements and idea behind shared memory regions.
Signed-off-by: Dr. David Alan Gilbert
---
content.tex| 2 ++
shared-mem.tex | 33 +
2 files changed, 35 insertions(+)
create mode 100644 shared-mem
From: "Dr. David Alan Gilbert"
Define an MMIO interface to enumerate and map shared
memory regions.
Note: This hasn't been implemented.
Signed-off-by: Dr. David Alan Gilbert
---
content.tex | 32
1 file changed, 32 insertions(+)
diff --git a/con
From: "Dr. David Alan Gilbert"
Hi,
This series formalises the idea of shared memory regions I'd
previously discussed and is intended for use with virtio-fs.
I've split it into three parts:
a) A general definition of the idea
b) A definition on virtio-pci using the layout
side the guest that's the problem.
Dave
> cheers,
> Gerd
>
>
> -
> To unsubscribe, e-mail: virtio-dev-unsubscr...@lists.oasis-open.org
> For additional commands, e-mail: virtio-dev-h...@lists.oasis-open
ec out callbacks on host that are
> triggered
> by virtqueue messages, which results in lower latency and makes it easy to
> dispatch to a particular device implementation without polling.
>
> """
>
> On Tue, Feb 12, 2019 at 6:03 AM Michael S. Tsirkin wrote:
>
d be standardized, and userspace
> > drivers would be constructed out of the resulting primitives.
> >
> > > Could you please advise if we can use something else to
> >> > achieve this goal?
> >>
> >> I am not sure what
ght make sense and be enough for at least two of your
device types.
Dave
> Yes, I realize that a guest could think it is using the same device as
> the host advertised (because strings matched) while it is not. We
&g
rtio-pipe to
> pass MMIOs and IRQs
> to control our devices to avoid dealing with kernel drivers at all.
It sounds to me like you want something like a virtio-pipe, with
a shared arena (like specified using the spec change I suggested)
but with either a separate queue, or commands in
o.gl/NJvPBvvFS3S3n9mn6
How do you transmit the glMapBufferRange command from QEMU driver to
host?
Dave
> Thank you.
>
> Regards,
> Roman.
>
> -
> To unsubscribe, e-mail: virtio-dev-unsubscr...@lists.oasis
78 matches
Mail list logo
