Displaying 6 results from an estimated 6 matches for "memory_exchange".
2017 Apr 04
4
Bug#859560: xen: CVE-2017-7228: x86: broken check in memory_exchange() permits PV guest breakout (XSA-212)
Source: xen
Version: 4.8.1~pre.2017.01.23-1
Severity: grave
Tags: security upstream
Justification: user security hole
Hi,
the following vulnerability was published for xen.
CVE-2017-7228[0]:
| An issue (known as XSA-212) was discovered in Xen, with fixes available
| for 4.8.x, 4.7.x, 4.6.x, 4.5.x, and 4.4.x. The earlier XSA-29 fix
| introduced an insufficient check on XENMEM_exchange input,
2006 Jul 26
5
[Fwd: stack overflow "cause" found]
...vmx_vmexit_handler: 632
0xffff8300001313ff arch_do_dom0_op: 552
0xffff8300001327f3 arch_do_dom0_op: 552
0xffff830000158660 emulate_privileged_op: 520
0xffff83000015a06c emulate_privileged_op: 520
0xffff830000114ce9 memory_exchange: 488
0xffff83000011598a memory_exchange: 488
0xffff83000010ce29 do_event_channel_op: 464
0xffff83000014b033 do_mmu_update: 456
0xffff83000014bd28 do_mmu_update: 456
0xffff8300001224a2 sedf_adjust_wei...
2008 May 19
21
[PATCH 0/5] VT-d support for PV guests
Hi,
I''ve added some preliminary support for VT-d for paravirtualized
guests. This must be enabled using an ''iommu_pv'' boot parameter
(disabled by default).
I''ve added some python bindigs to allow xend to assign PCI devices to
IOMMU for PV guests. For HVM guests this is handled in ioemu. Not
sure if it makes sense to handle both cases in one place.
The
2012 Nov 15
1
[RFC/PATCH v4] XENMEM_claim_pages (subop of existing) hypercall
...get_knownalive_domain(e);
page_list_add_tail(page, &e->page_list);
page_set_owner(page, e);
diff --git a/xen/common/memory.c b/xen/common/memory.c
index 83e2666..a9d91c1 100644
--- a/xen/common/memory.c
+++ b/xen/common/memory.c
@@ -454,7 +454,7 @@ static long memory_exchange(XEN_GUEST_HANDLE_PARAM(xen_memory_exchange_t) arg)
(j * (1UL << exch.out.extent_order)));
spin_lock(&d->page_alloc_lock);
- d->tot_pages -= dec_count;
+ domain_decrease_tot_pages(d, dec_count);...
2012 Aug 10
18
[PATCH v2 0/5] ARM hypercall ABI: 64 bit ready
Hi all,
this patch series makes the necessary changes to make sure that the
current ARM hypercall ABI can be used as-is on 64 bit ARM platforms:
- it defines xen_ulong_t as uint64_t on ARM;
- it introduces a new macro to handle guest pointers, called
XEN_GUEST_HANDLE_PARAM (that has size 4 bytes on aarch and is going to
have size 8 bytes on aarch64);
- it replaces all the occurrences of
2012 Aug 16
27
[PATCH v3 0/6] ARM hypercall ABI: 64 bit ready
Hi all,
this patch series makes the necessary changes to make sure that the
current ARM hypercall ABI can be used as-is on 64 bit ARM platforms:
- it defines xen_ulong_t as uint64_t on ARM;
- it introduces a new macro to handle guest pointers, called
XEN_GUEST_HANDLE_PARAM (that has size 4 bytes on aarch and is going to
have size 8 bytes on aarch64);
- it replaces all the occurrences of