Searched refs:seen (Results 1 – 14 of 14) sorted by relevance
| /xen/xen/common/ |
| A D | spinlock.c | 48 union lock_debug seen, new = { 0 }; in check_lock() local
51 seen.val = cmpxchg(&debug->val, LOCK_DEBUG_INITVAL, new.val); in check_lock()
53 if ( !seen.unseen && seen.irq_safe == !irq_safe ) in check_lock()
56 seen.irq_safe, irq_safe); in check_lock()
|
| /xen/scripts/ |
| A D | add_maintainers.pl | 484 my %seen;
488 $seen{lc($item)} = 1;
491 unless ($seen{lc($item)}++) {
|
| /xen/xen/tools/ |
| A D | gen-cpuid.py | 298 seen = [feat]
311 if f in seen:
315 seen.append(f)
318 state.deep_deps[feat] = seen[1:]
|
| /xen/xen/include/xen/ |
| A D | sched.h | 573 int old, seen = atomic_read(&d->refcnt); in get_domain() local
576 old = seen; in get_domain()
579 seen = atomic_cmpxchg(&d->refcnt, old, old + 1); in get_domain()
581 while ( unlikely(seen != old) ); in get_domain()
|
| /xen/ |
| A D | CHANGELOG.md | 28 - The CPUID data seen by a guest on boot is now moved in the migration
|
| /xen/docs/misc/ |
| A D | stubdom.txt | 148 - set the path to menu.lst, as seen from the domU, in extra:
179 will be seen by PV-GRUB as (hd0), not (hd0,6), since GRUB will not see any
|
| A D | xsm-flask.txt | 31 such management domains are (in such a design) to be seen as
|
| A D | xen-command-line.pandoc | 746 However, as PV dom0's have always seen host CPUID data in the past, there
|
| /xen/stubdom/ |
| A D | pciutils.patch | 228 …a->warning("%04x:%02x:%02x.%d: Invalid 64-bit address seen for BAR %d.", d->domain, d->bus, d->dev…
|
| /xen/docs/man/ |
| A D | xl-disk-configuration.5.pod | 125 Virtual device as seen by the guest (also referred to as guest drive
|
| A D | xen-tscmode.7.pod | 229 as will be seen in the next section.
|
| A D | xl.cfg.5.pod.in | 846 correctly map the input keys into keycodes seen by the guest. The
2437 correctly map the input keys into keycodes seen by the guest. The
|
| A D | xl.1.pod.in | 1015 In which it can be seen that the OL5 guest still has 847MB of claimed
|
| /xen/docs/designs/ |
| A D | argo.pandoc | 391 In the above example, it can be seen that it is safe to acquire the `L3` lock
|
Completed in 37 milliseconds