| /xen/tools/xl/ |
| A D | xl_console.c | 86 libxl_device_channel *channels; in main_channellist() local
99 channels = libxl_device_channel_list(ctx, domid, &nb); in main_channellist()
100 if (!channels) in main_channellist()
103 if (!libxl_device_channel_getinfo(ctx, domid, &channels[i], in main_channellist()
105 printf("%-3d %-2d ", channels[i].devid, channelinfo.backend_id); in main_channellist()
109 channels[i].connection)); in main_channellist()
110 switch (channels[i].connection) { in main_channellist()
120 libxl_device_channel_dispose(&channels[i]); in main_channellist()
122 free(channels); in main_channellist()
|
| A D | xl_parse.c | 1216 XLU_ConfigList *channels, *ioports, *irqs, *iomem, *viridian, *dtdevs, in parse_config_data() local
2157 if (!xlu_cfg_get_list (config, "channel", &channels, 0, 0)) { in parse_config_data()
2159 d_config->channels = NULL; in parse_config_data()
2160 while ((buf = xlu_cfg_get_listitem (channels, in parse_config_data()
2167 chn = ARRAY_EXTEND_INIT(d_config->channels, d_config->num_channels, in parse_config_data()
|
| /xen/xen/arch/x86/ |
| A D | emul-i8254.c | 63 struct hvm_hw_pit_channel *c = &pit->hw.channels[channel]; in pit_get_count()
92 struct hvm_hw_pit_channel *s = &pit->hw.channels[channel]; in pit_get_out()
128 struct hvm_hw_pit_channel *s = &pit->hw.channels[channel]; in pit_set_gate()
156 return pit->hw.channels[channel].gate; in pit_get_gate()
169 struct hvm_hw_pit_channel *s = &pit->hw.channels[channel]; in pit_load_count()
258 s = &pit->hw.channels[channel]; in pit_ioport_write()
271 s = &pit->hw.channels[channel]; in pit_ioport_write()
293 s = &pit->hw.channels[addr]; in pit_ioport_write()
323 s = &pit->hw.channels[addr]; in pit_ioport_read()
435 pit_load_count(pit, i, pit->hw.channels[i].count); in pit_load()
[all …]
|
| /xen/tools/misc/ |
| A D | xen-hvmctx.c | 292 i, p.channels[i].count, p.channels[i].latched_count, in dump_pit()
293 p.channels[i].count_latched); in dump_pit()
295 p.channels[i].status, p.channels[i].status_latched); in dump_pit()
297 p.channels[i].read_state, p.channels[i].write_state, in dump_pit()
298 p.channels[i].write_latch, p.channels[i].rw_mode); in dump_pit()
300 p.channels[i].mode, p.channels[i].bcd, p.channels[i].gate); in dump_pit()
|
| /xen/tools/libxl/ |
| A D | libxl_console.c | 496 libxl_device_channel **channels, in libxl__append_channel_list() argument
522 tmp = realloc(*channels, in libxl__append_channel_list()
528 *channels = tmp; in libxl__append_channel_list()
529 next = *channels + *nchannels + devid; in libxl__append_channel_list()
547 libxl_device_channel *channels = NULL; in libxl_device_channel_list() local
552 rc = libxl__append_channel_list(gc, domid, &channels, num); in libxl_device_channel_list()
556 return channels; in libxl_device_channel_list()
562 libxl_device_channel_dispose(&channels[*num]); in libxl_device_channel_list()
564 free(channels); in libxl_device_channel_list()
|
| A D | libxl_types_internal.idl | 48 # A console with a name is called a 'channel', see docs/misc/channels.txt
|
| A D | libxl_types.idl | 954 # see docs/misc/channels.txt
955 ("channels", Array(libxl_device_channel, "num_channels")),
|
| A D | libxl_dm.c | 1243 connection = guest_config->channels[i].connection; in libxl__build_device_model_args_new()
1244 devid = guest_config->channels[i].devid; in libxl__build_device_model_args_new()
1250 path = guest_config->channels[i].u.socket.path; in libxl__build_device_model_args_new()
3738 if (d_config->channels[i].backend_domid == domid) { in libxl__need_xenpv_qemu()
|
| /xen/docs/man/ |
| A D | xen-pv-channel.7.pod | 10 link. Typical uses of channels are
36 =head2 How to use channels: an example
152 Using channels avoids having to use a temporary disk device or network
164 Since channels are identified by names, application authors must ensure their
173 Hotplug and unplug of channels is not currently implemented.
|
| A D | xl.cfg.5.pod.in | 855 Specifies the virtual channels to be provided to the guest. A
857 a serial link. Typical uses for channels include transmitting VM
1332 Limit the guest to using at most N event channels (PV interrupts).
1337 FIFO-based event channel ABI support up to 131,071 event channels.
1440 * number of channels (min/max)
1450 fit its needs. For example, card may define number of channels to be
1474 =item B<channels-min=NUMBER>
1476 The minimum amount of channels.
1478 =item B<channels-max=NUMBER>
1480 The maximum amount of channels.
[all …]
|
| /xen/docs/designs/ |
| A D | non-cooperative-migration.md | 97 setting up grant table entries and event channels to communicate with the
105 channels must be preserved (and remain operational once guest execution is
109 up grant entries and event channels, the backend drivers in the new host
147 to require the guest co-operation to re-open the channels and so it should
175 ### Event channels
177 Event channels are essentially the para-virtual equivalent of interrupts.
194 channels in order to re-establish a protocol connection. Hence, one or more
202 also rely on event channels which are set up by the toolstack. Normally,
204 new pair of event channels for these protocols in the destination domain.
206 running in the source domain. For non-cooperative migration these channels
|
| /xen/tools/flask/policy/modules/ |
| A D | vm_role.cons | 28 # Prevent event channels and grants between different users. This could be
|
| A D | xen.if | 119 # Allow two domain types to communicate using event channels
126 # Allow two domain types to communicate using grants and event channels
135 # and event channels
|
| A D | xen.te | 83 # The object role (object_r) is used for devices, resources, and event channels;
|
| /xen/xen/include/public/io/ |
| A D | sndif.h | 902 } channels; member
|
| /xen/docs/admin-guide/ |
| A D | introduction.rst | 27 Xen also provides a hypercall interface to guests, including event channels
|
| /xen/docs/misc/ |
| A D | pvh.pandoc | 89 Interrupts from paravirtualized devices are delivered using event channels, see
91 event channels. Delivery of those interrupts can be configured in the same way
|
| A D | xsm-flask.txt | 12 - Prevent two domains from communicating via event channels or grants
174 Type transitions are also used to compute the labels of event channels.
180 visible in the labels of domains and associated objects (event channels); when
187 prevent different users from communicating using grants or event channels, while
|
| A D | console.txt | 47 concept with the same name and purpose. The file "channels.txt" describes
48 how to use channels and includes a registry of well-known channel names.
|
| A D | 9pfs.pandoc | 7 completely independent from the communication channels, in fact many
8 clients and servers support multiple channels, usually called
|
| /xen/ |
| A D | .travis.yml | 87 channels:
|
| /xen/tools/firmware/rombios/ |
| A D | rombios.c | 692 ata_channel_t channels[BX_MAX_ATA_INTERFACES];
2491 write_byte(ebda_seg,&EbdaData->ata.channels[channel].irq,0);
2587 write_word(ebda_seg,&EbdaData->ata.channels[0].iobase1,0x1f0);
2588 write_word(ebda_seg,&EbdaData->ata.channels[0].iobase2,0x3f0);
2589 write_byte(ebda_seg,&EbdaData->ata.channels[0].irq,14);
2593 write_word(ebda_seg,&EbdaData->ata.channels[1].iobase1,0x170);
2594 write_word(ebda_seg,&EbdaData->ata.channels[1].iobase2,0x370);
2595 write_byte(ebda_seg,&EbdaData->ata.channels[1].irq,15);
2599 write_word(ebda_seg,&EbdaData->ata.channels[2].iobase1,0x1e8);
2601 write_byte(ebda_seg,&EbdaData->ata.channels[2].irq,12);
[all …]
|
| /xen/xen/common/ |
| A D | Kconfig | 234 it. This will deny any unmediated communication channels (grant tables
235 and event channels) between unprivileged VMs.
280 This allows communication channels to be established that do not
|
| /xen/xen/xsm/flask/policy/ |
| A D | access_vectors | 288 # Class event describes event channels. Interdomain event channels have their
314 # target = domain whose event channels are being reset
|
| /xen/xen/include/public/arch-x86/hvm/ |
| A D | save.h | 486 } channels[3]; /* 3 x 16 bytes */ member
|