Home
last modified time | relevance | path

Searched refs:channel (Results 1 – 25 of 29) sorted by relevance

12

/xen/xen/arch/x86/
A Demul-i8254.c90 static int pit_get_out(PITState *pit, int channel) in pit_get_out() argument
156 return pit->hw.channels[channel].gate; in pit_get_gate()
178 pit->count_load_time[channel] = 0; in pit_load_count()
242 int channel, access; in pit_ioport_write() local
252 channel = val >> 6; in pit_ioport_write()
253 if ( channel == 3 ) in pit_ioport_write()
256 for ( channel = 0; channel < 3; channel++ ) in pit_ioport_write()
258 s = &pit->hw.channels[channel]; in pit_ioport_write()
259 if ( val & (2 << channel) ) in pit_ioport_write()
271 s = &pit->hw.channels[channel]; in pit_ioport_write()
[all …]
/xen/tools/ocaml/libs/eventchn/
A Dxeneventchn.mli17 (** Event channel bindings: see tools/libxc/include/xenctrl.h *)
20 (** An initialised event channel interface. *)
23 (** A local event channel. *)
47 (** Return an initialised event channel interface. On error it
56 (** Notify the given event channel. On error it will throw a
61 channel connected to domid:remote_port. On error it will
65 (** Binds a local event channel to the VIRQ_DOM_EXC
70 (** Binds a local event channel to the specific VIRQ type.
74 (** Unbinds the given event channel. On error it will throw a
78 (** Returns the next event channel to become pending. On error it
[all …]
/xen/docs/man/
A Dxen-pv-channel.7.pod5 xen-pv-channel - Xen PV Channels
9 A channel is a low-bandwidth private byte stream similar to a serial
47 Install a guest as normal (no channel configuration necessary)
53 prepare the guest to communicate over the channel, and also prepare
92 Domain configuration is created for the VM, listing the channel
122 where the "xen-console-setup" script would read the channel name and
123 make a symlink in /dev/xen-channel/org.my.cloud.software.agent.version1
159 before you can use a channel. By default a channel will appear as a device
165 channel names are unique to avoid clashes. We recommend that channel names
167 prevent clashes we recommend authors add their names to our global channel
[all …]
A Dxl.cfg.5.pod.in674 event channel will not be created. Instead the old xend behaviour of
678 The existence of the suspend event channel path can cause problems with
853 =item B<channel=[ "CHANNEL_SPEC_STRING", "CHANNEL_SPEC_STRING", ...]>
856 channel is a low-bandwidth, bidirectional byte stream, which resembles
859 L<xen-pv-channel(7)> for more details.
878 application to the right channel device. There is no formal registry
879 of channel names, so application authors are encouraged to make their
894 data between the channel and the connected socket.
1333 Guests use hypervisor resources for each event channel they use.
1337 FIFO-based event channel ABI support up to 131,071 event channels.
[all …]
/xen/tools/libxl/
A Dlibxl_console.c404 if (channel->devid == -1) in libxl__init_console_from_channel()
405 channel->devid = dev_num; in libxl__init_console_from_channel()
407 if (!channel->name) { in libxl__init_console_from_channel()
412 if (channel->backend_domname) { in libxl__init_console_from_channel()
426 switch (channel->connection) { in libxl__init_console_from_channel()
436 if (!channel->u.socket.path) { in libxl__init_console_from_channel()
448 __func__, channel->connection); in libxl__init_console_from_channel()
452 console->devid = channel->devid; in libxl__init_console_from_channel()
467 libxl_device_channel_init(channel); in libxl__device_channel_from_xenstore()
577 channelinfo->devid = channel->devid; in libxl_device_channel_getinfo()
[all …]
A Dlibxl_types_internal.idl48 # A console with a name is called a 'channel', see docs/misc/channels.txt
A Dlibxl.h2155 const libxl_device_channel *channel,
/xen/tools/ocaml/xenstored/
A Ddisk.ml81 let channel = open_in file in
82 let rec input_line_list channel =
83 let line = try input_line channel with End_of_file -> "" in
85 line :: input_line_list channel
87 close_in channel;
90 input_line_list channel
150 let channel = open_out_gen [ Open_wronly; Open_creat; Open_trunc; ]
152 Store.dump store channel;
153 flush channel;
154 close_out channel;
A Dlogging.ml89 let channel = ref (open_out_gen [Open_append; Open_creat] 0o644 log_file) in
92 try flush !channel; close_out !channel
96 channel := open_out_gen [Open_append; Open_creat] 0o644 log_file in
98 log_rotate channel log_file log_nb_files;
104 output_string !channel s;
105 flush !channel;
A Dxenstored.ml70 let channel = open_out_gen [ Open_wronly; Open_creat; Open_trunc; ]
72 finally (fun () -> Store.dump store channel)
73 (fun () -> close_out channel)
203 let channel = open_in file in
204 finally (fun () -> from_channel store doms cons channel)
205 (fun () -> close_in channel)
227 let channel = open_out_gen [ Open_wronly; Open_creat; Open_trunc; ] 0o600 file in
228 finally (fun () -> to_channel store cons channel)
229 (fun () -> close_out channel)
/xen/docs/designs/
A Dnon-cooperative-migration.md31 channel of communication is generally established using xenstore (the store
83 references (mapping the shared pages) and event channel ports (opening its
145 and some event channel state (particularly if using the *2l* protocol).
179 creates an *inter-domain* event channel between its own domain and the
182 This hypercall allocates an event channel object in the hypervisor and
185 the event channel by specifying it, and the value of `frontend-id`, as
188 this fashion frontend and backend drivers can use the event channel as a
192 Currently no event channel state is preserved on migration, requiring
199 channel objects.
208 avoided and instead be included in the general event channel state
[all …]
A Dxenstore-migration.md218 | `evtchn` | The port number of the interdomain channel used |
/xen/docs/misc/
A Dxenstore-ring.txt50 A xenstore ring is always associated with an event channel. Whenever the
51 ring structure is updated the event channel must be signalled. The
53 time, not only in response to an event channel event. This implies that
97 and reconnect is in progress") and signalling the event channel.
110 - signal the event channel.
A D9pfs.pandoc39 to multiplex operations on a single channel.
130 event-channel-<num> (event-channel-0, event-channel-1, etc)
133 The identifier of the Xen event channel used to signal activity
164 event channel.
179 ring, which are used to setup the rings, and an event channel per ring,
379 - notify the other end via event channel
391 - notify the other end via event channel
A Dconsole.txt46 We call a PV console with a name a "channel", in reference to the libvirt
48 how to use channels and includes a registry of well-known channel names.
50 If the PV console has a name (i.e. it is a "channel") then the name
62 glue the channel to
A Dpvcalls.pandoc116 The identifier of the Xen event channel used to signal activity
169 event channel.
184 will is used to exchange messages over a ring, and an event channel,
321 issues an event channel notification when a notification is required.
375 it needs to notify the frontend and does so via event channel.
433 channel which will be used for notifications of activity on the data
504 - backend unbinds the event channel
506 - frontend frees data ring, indexes page and unbinds event channel
516 (indexes page and data ring) and event channel when creating one of
518 delaying unmapping grants and unbinding the event channel. The
[all …]
A Dxenstore-paths.pandoc50 * EVTCHN -- the decimal representation of an event channel.
182 #### ~/device/suspend/event-channel = ""|EVTCHN [w]
184 The domain's suspend event channel. The toolstack may create this
187 guest and hence it may create the suspend event channel path.
190 event channel port it has acquired. The toolstack is expected to use
192 suspend, to signal the event channel.
202 Note that the use of this event channel suspend protocol is optional
206 below) even if the guest has advertised support for the event channel
330 The event channel used by the domain's connection to XenStore.
A Dxenstore.txt46 Communication with xenstore is via either sockets, or event channel
272 channel is an unbound event channel in <domid> (likewise in
280 The event channel is unbound at the xenstored end and the page
A Dpvh.pandoc41 (console page address, xenstore event channel...) can be obtained
/xen/xen/xsm/flask/policy/
A Daccess_vectors291 # permission checks must pass on both endpoints for an event channel to be
295 # when creating an interdomain event channel endpoint:
296 # source = event channel label
297 # target = remote domain the event channel binds to. This may be a _self or
299 # This permission is checked when creating an unbound event channel and when the
300 # interdomain event channel is established.
304 # target = event channel label
308 # when creating an interdomain event channel endpoint:
309 # source = the domain creating the channel (which might not be an endpoint)
310 # target = event channel label
/xen/xen/include/public/io/
A Dvscsiif.h270 uint16_t channel, id, lun; /* (virtual) device specification */ member
/xen/xen/include/asm-x86/
A Dedd.h63 u8 channel; member
/xen/tools/firmware/rombios/
A Drombios.c2484 Bit8u channel, device;
2487 for (channel=0; channel<BX_MAX_ATA_INTERFACES; channel++) {
2621 channel = device / 2;
2904 channel = device / 2;
2970 Bit8u channel, slave;
2973 channel = device / 2;
3119 Bit8u channel, slave;
3122 channel = device / 2;
3270 Bit8u channel, slave;
3274 channel = device / 2;
[all …]
/xen/tools/flask/policy/modules/
A Dxen.if111 # This allows an event channel to be created from domains with labels
/xen/xen/arch/x86/efi/
A Defi-boot.h419 params->interface_path.pci.channel = in efi_arch_edd()

Completed in 42 milliseconds

12