13. September 2022 #892
dimakuv
started this conversation in
Meeting notes
Replies: 2 comments
-
|
Beta Was this translation helpful? Give feedback.
0 replies
-
Discuss how to respond to queries at [[email protected]] and should we look at expanding that list to be beyond maintainers to get some additional support. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Agenda
(please write your proposed agenda items in comments under this discussion)
Download statistics
We want to have some download statistics, just to have a general idea of how popular Gramine is and what are the trends.
Woju opposed the idea to install GitHub plugins. But he said he could do smth like what they do for Qubes: https://www.qubes-os.org/statistics/.
Woju: there are problems with GitHub default counting approaches, they break privacy. Qubes has an "estimated package downloads" graph (actually, IP addresses that downloaded the packages). The detailed log is never released and is periodically cleaned. But if people are behind a corporate proxy (with a single IP for thousands of employees), then the diagram is very much skewed. So the vertical bar is not really accurate, but the trends and ratio of releases reflect reality. Two problems: Dockerhub downloads are not tracked (but Dockerhub has smth called the "Pulls" number), and once Gramine is included in OS repos, also can't count those downloads.
Woju: changes that we need:
TODO(Woju): will look into how to implement this for our gramineproject.io website.
How to respond to queries at [email protected]
Mona: The traffic increased in the mailing list. We need to have timely replies.
Dmitrii: maybe redirect people from mailing lists to GitHub Discussions?
Michal will create a form that asks users do they want to create an Issue or to create a Discussion. This will effectively move people away from mailing lists to GitHub.
Mona: let's update our pages to direct users not to mailing lists, but to GitHub Discussions.
TODO(Michal): update.
PAL VMA booking removal + EDMM integration
Two cases:
PalVirtualMemoryAlloc
function -- it only has current requested permissions. It is possible to have overlapping regions, and for it we have different cases: for new region, everything as normal; for overlapping region, somehow need to pass the previous permissions (for those already-allocated pages).Borys: no clear solution for case 2. Allocating memory is a two-step process: first bookkeep, then call PAL API. Currently if we have overlapping alloc, then it is PAL's job -- and in Linux PAL the host does everything, in Linux SGXv1 PAL there is nothing to do.
Don: the LibOS notices overlapping regions, and splits one PAL
PalVirtualMemoryAlloc
call into several calls. Borys: this sounds complicated, e.g. we need to put all this under one lock acquisition, butPalVirtualMemoryAlloc
itself can ask LibOS for more memory allocation (Dmitrii doesn't see why this could be needed). Borys: one more problem, LibOS bookkeeping itself might need memory, so it allocates some internal object, so it bookkeeps this memory.TODO(Vijay): implement the idea of LibOS only giving non-overlapping memory regions to PAL. So, for overlapped region LibOS must issue: PAL unmap + PAL map.
Beta Was this translation helpful? Give feedback.
All reactions