On 09.07.19 12:11, Ralf Ramsauer wrote:
> Hi Jan,
> 
> On 7/9/19 7:36 AM, Jan Kiszka wrote:
>> Hi all,
>>
>> long-announced, I feel like it's finally in a good shape to publish it: The 
>> new
>> version of something I would call "ivshmem 2.0" is now available in
>> wip/ivshmem2. Highlights of this:
> 
> Cool, thanks! Will try it.
> 
>>
>>  - vmexit-free peer state table in shared memory
>>  - all key features of current QEMU's ivshmem, specifically
>>    - multi-peer support
>>    - multi-vector support
>>  - unidirectional shared memory (optional)
>>  - UIO-friendly one-shot interrupt mode (optional)
> 
> I saw there's now a FEATURES register. Should we maybe also introduce a
> version/revision register for more invasive changes that go beyong
> adding a feature? Or will handling of different versions be done via
> vendor/device-ID (as I suggest that's the case at the moment).
> 

As this is a PCI(-only) device, we do have that already: The revision ID in the
PCI config space. It's specified to be "2" for now.

Jan

-- 
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux

-- 
You received this message because you are subscribed to the Google Groups 
"Jailhouse" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jailhouse-dev/5fda803a-d8d3-379a-66fd-a22bb46fb778%40siemens.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to