[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [PATCH 1/3] shared memory: Define shared memory regions
On Wed, Feb 13, 2019 at 10:44:27AM +0000, Dr. David Alan Gilbert wrote: > * Stefan Hajnoczi (stefanha@redhat.com) wrote: > > On Fri, Jan 11, 2019 at 11:41:58AM +0000, Dr. David Alan Gilbert (git) wrote: > > We start with an overview of device initialization, then expand on the > > > diff --git a/shared-mem.tex b/shared-mem.tex > > > new file mode 100644 > > > index 0000000..6da249c > > > --- /dev/null > > > +++ b/shared-mem.tex > > > @@ -0,0 +1,25 @@ > > > +\section{Shared Memory Regions}\label{sec:Basic Facilities of a Virtio Device / Shared Memory Regions} > > > + > > > +Shared memory regions are an additional facility > > > +available to devices that need a region of memory that's > > > +continuously shared between the host and the guest, rather > > > +than passed between them in the way virtqueue elements are. > > > + > > > +Example uses include shared caches and version pools for versioned > > > +data structures. > > > > Another motivation for shared memory regions is to accommodate memory > > resources that must be allocated by the device rather than the driver. > > > > For example, some GPU hardware restrictions make it impossible for the > > driver to select a suitable RAM region. > > I've added: > > The region is chosen by the host and presented to the guest, as > such it is useful in situations where the memory is accessed on > the host by other libraries that can't safely access guest RAM. Great! "libraries" can be made more general: s/libraries/components/
Attachment:
signature.asc
Description: PGP signature
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]