search for: wrmsr_hypervisor_reg

Displaying 5 results from an estimated 5 matches for "wrmsr_hypervisor_reg".

Did you mean: wrmsr_hypervisor_regs
2007 Sep 27
1
Unsigned bug in rdmsr_hypervisor_regs/wrmsr_hypervisor_regs
The code, below, in rdmsr_hypervisor_regs (in xen/arch/x86/traps.c) looks wrong. (The same code is in wrmsr_hypervisor_regs.) int rdmsr_hypervisor_regs( uint32_t idx, uint32_t *eax, uint32_t *edx) { idx -= 0x40000000; if ( idx > 0 ) return 0; ... The intent, apparently, is that the function should return zero if the original idx exceeds 0x40000000. However because idx is unsigned the function w...
2012 Mar 22
1
Question: PV ops Fedora 16 Initialises Hypercall Page Twice?
Xen Developers, I noticed that my PV ops guests cause the hypervisor to invoke hypercall_page_initialise twice from traps.c (i.e. through wrmsr_hypervisor_regs), for different hypercall_page addresses. Looking at the code, I see hvmloader.c causing one of those, in its main. I read the HVM Loader Xen wiki page, Googled, spelunked the source, etc. but cannot find where / why the other hypercall page is being requested. Is the other hypercall page being in...
2007 Dec 10
0
[PATCH] avoid duplication of domain ID in messages
..._id, - regs->error_code); + gdprintk(XENLOG_WARNING, "Unhandled %s fault/trap [#%d] " + "on VCPU %d [ec=%04x]\n", + trapstr(trapnr), trapnr, v->vcpu_id, regs->error_code); return 0; } @@ -570,8 +569,8 @@ int wrmsr_hypervisor_regs( if ( idx > 0 ) { gdprintk(XENLOG_WARNING, - "Dom%d: Out of range index %u to MSR %08x\n", - d->domain_id, idx, 0x40000000); + "Out of range index %u to MSR %08x\n", +...
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