| commit | b64fedcf913456f1039c3026c143d8491d59fcaf | |
| author | Bart Van Assche <bvanassche@acm.org> | |
| Sun, 28 Jun 2015 16:55:45 +0000 (28 16:55 +0000) | ||
| committer | Bart Van Assche <bvanassche@acm.org> | |
| Sun, 28 Jun 2015 16:55:45 +0000 (28 16:55 +0000) | ||
| tree | f82f38eef932fc90f2995dd269a04633f38053fc | treesnapshot (tar.gz zip) |
| parent | 31229b70203e5ed273f0bf001db7071e3b604659 | commitdiff |
xen: Implement the xsm_op hypercall
More recent Xen toolstacks use this for the SID_TO_CONTEXT operation
only, even when XSM is not in use.
XSM is actually an abstraction layer, of which the only current
implementation is FLASK. So this blindly assumes that the backend is
FLASK. Should another XSM backend be invented then we will have to
sort of detecting the correct one.
Signed-off-by: Ian Campbell <ian.campbell@citrix.com>
git-svn-id: svn://svn.valgrind.org/valgrind/trunk@15384
More recent Xen toolstacks use this for the SID_TO_CONTEXT operation
only, even when XSM is not in use.
XSM is actually an abstraction layer, of which the only current
implementation is FLASK. So this blindly assumes that the backend is
FLASK. Should another XSM backend be invented then we will have to
sort of detecting the correct one.
Signed-off-by: Ian Campbell <ian.campbell@citrix.com>
git-svn-id: svn://svn.valgrind.org/valgrind/trunk@15384
| coregrind/m_syswrap/syswrap-xen.c | diffblobblamehistory | |
| include/vki/vki-xen-xsm.h | [new file with mode: 0644] | blob |
| include/vki/vki-xen.h | diffblobblamehistory |