Searched refs:introduce (Results 1 – 16 of 16) sorted by relevance
85 There is a caveat -- an incorrect live patch can introduce a guest->host90 No, although an incorrect live patch can introduce a guest user->guest98 There is a caveat -- an incorrect live patch can introduce an105 Once again, there is a caveat that an incorrect live patch can introduce
40 established COS. Intel Xeon processor E5 v4 family (and some others) introduce
242 bool introduce = false; in access_node() local281 introduce = true; in access_node()308 if (introduce && type == NODE_ACCESS_DELETE) in access_node()
35 introduce: domid -> nativeint -> int -> unit; RecordField56 introduce = (fun id mfn port -> Xsraw.introduce id mfn port con);
45 introduce : domid -> nativeint -> int -> unit; RecordField
49 val introduce : int -> nativeint -> int -> con -> unit val
47 let introduce domid mfn port con = function
226 let introduce domid mfn port con = function227 ack (sync (Queueop.introduce domid mfn port) con)
19 agnostic, that future versions will not need to introduce
16 New kernel releases often introduce new config symbols. Often more
125 So we introduce user configurable parameters to specify RDM resource and
740 It is possible to introduce new commands without changing the protocol747 request structure without disrupting the current ABI is to introduce a
282 for it is always consumed by other vCPUs incorrectly. So we need introduce
1004 If supporting hotpatches that introduce additional exception-locations1048 As such the ELF payload can introduce new .rodata, .bss, and .data sections.
229 introduce security vulnerabilities.
238 | Xenbus.Xb.Op.Introduce -> "introduce"
Completed in 18 milliseconds