OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

virtio-dev message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: Re: [virtio-dev] Memory sharing device

Hi Gerd,

> virtio-gpu specifically needs that to support vulkan and opengl
> extensions for coherent buffers, which must be allocated by the host gpu
> driver.  It's WIP still.

the proposed spec says:

+Shared memory regions MUST NOT be used to control the operation
+of the device, nor to stream data; those should still be performed
+using virtqueues.

Is there a strong reason to prohibit using memory regions for control purposes?
Our long term goal is to have as few kernel drivers as possible and to move
"drivers" into userspace. If we go with the virtqueues, is there
general a purpose
device/driver to talk between our host and guest to support custom hardware
(with own blobs)? Could you please advise if we can use something else to
achieve this goal?

I saw there were registers added, could you please elaborate how new address
regions are added and associated with the host memory (and backwards)?

We allocate a region from the guest first and pass its offset to the
host to plug
real RAM into it and then we mmap this offset:


Thank you.


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]