Subject: [sv-cc] Date: Mon, 24 Mar 2003 13:01:02 -0500
From: Francoise Martinolle (fm@cadence.com)
Date: Mon Mar 24 2003 - 10:01:54 PST
John,
I think that your comment in this paragraph brings up the problem that different users using the same id may get the user-data of each other.
Therefore we should recommended that always the user application (whether
it is an IP provider of a regular user), requests a unique id from DPI by calling the new function.
We don't need to reserve the id 0 for module scope, if the user application
does not need different ids for all the functions, it just requests a new id
and uses it for all its user data. Reserving 0 for module scope and IP providers only is dangerous if you have 2 or more vendor ip instances
in the same module scope.
This is the paragraph I am taling about in your write up.
- While storage of user data for ID=0 can be combined with storage
for specific ID's, it is recommended that vendor supplied C
model IP always use allocated ID's and that only end-user
applications use ID=0.
different
This archive was generated by hypermail 2b28 : Mon Mar 24 2003 - 10:02:26 PST