aboutsummaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* Update Xen version to 4.0.2-rc14.0.2-rc1Keir Fraser2011-01-102-2/+3
|
* x86: Fix atomic_write*() macros to correctly inform GCC that memoryKeir Fraser2011-01-081-2/+2
| | | | | | | | | | | | | it knows about is being written to. The bug is a copy-and-paste error from inline asm that writes to I/O memory. In that case, as with asm for accessign guest memory, specifying memory as a read-only parameter is acceptable because the memory cannot alias with anything that GCC reads directly. Signed-off-by: Keir Fraser <keir@xen.org> xen-unstable changeset: 22683:533d6e5c0099 xen-unstable date: Sat Jan 08 10:05:55 2011 +0000
* Update my email address to long-term stable address.Keir Fraser2011-01-0711-11/+11
| | | | | | Signed-off-by: Keir Fraser <keir@xen.org> xen-unstable changeset: 22675:0ab058a55c24 xen-unstable date: Fri Jan 07 13:30:04 2011 +0000
* kexec: correct _domain offset info in elf-notesKeir Fraser2011-01-062-4/+8
| | | | | | | | | | | | | The hypervisor writes some data structure infos into the elf note section of the vmcore to enable interpretation of the xen structures by kexec/kdump. The info of the offset of _domain in page_info was just wrong on non-ia64 systems. Signed-off-by: Juergen Gross <juergen.gross@ts.fujitsu.com> xen-unstable changeset: 22666:cb756381087c xen-unstable date: Thu Jan 06 19:02:36 2011 +0000
* Update QEMU_TAGKeir Fraser2011-01-061-4/+3
|
* relax vCPU pinned checksKeir Fraser2011-01-053-2/+4
| | | | | | | | | | | | | Both writing of certain MSRs and VCPUOP_get_physid make sense also for dynamically (perhaps temporarily) pinned vcpus. Likely a couple of other MSR writes (MSR_K8_HWCR, MSR_AMD64_NB_CFG, MSR_FAM10H_MMIO_CONF_BASE) would make sense to be restricted by an is_pinned() check too, possibly also some MSR reads. Signed-off-by: Jan Beulich <jbeulich@novell.com> xen-unstable changeset: 22649:39194f457534 xen-unstable date: Wed Jan 05 09:57:15 2011 +0000
* VT-d: fix and improve print_vtd_entries()Keir Fraser2010-12-241-18/+19
| | | | | | | | | | | | | | | | | | | | Fix leaking of mapped domain pages (root_entry and ctxt_entry when falling out of the level traversing loop). Do this by re-arranging things slightly so that a mapping is retained only as long as it really is needed. Fix the failure to use map_domain_page() in the level traversing loop of the function. Add a mssing return statement in one of the error paths. Also I wonder whether not being able to call print_vtd_entries() from iommu_page_fault_do_one() in ix86 is still correct, now that map_domain_page() is IRQ safe. Signed-off-by: Jan Beulich <jbeulich@novell.com> xen-unstable changeset: 22632:7cc87dcf30a1 xen-unstable date: Fri Dec 24 10:14:01 2010 +0000
* re-add calls accidentally deleted from run_all_nonirq_keyhandlers()Keir Fraser2010-12-241-0/+4
| | | | | | | | | | | | c/s 22538:a3a29e67aa7e, having got applied in a form different from the one submitted, resulted in the calls to console_{start,end}_log_everything() getting removed without replacement. Add them back since, other than run_all_keyhandlers(), this doesn't run with log-everything already in effect. Signed-off-by: Jan Beulich <jbeulich@novell.com> xen-unstable changeset: 22631:dca1b7cf2e2c xen-unstable date: Fri Dec 24 10:12:58 2010 +0000
* x86 hvm ept: Remove EPT guest linear address validationKeir Fraser2010-12-241-2/+1
| | | | | | | | | | | | | | For EPT violation resulting from an attempt to load the guest PDPTEs as part of the execution of the MOV CR instruction, the EPT_GLA_VALID is not valid. This situation should not happen in most situation, since we always populate guest memory. But this is not ture for PAE guest under the PoD/Page sharing situation. In that situation, a page pointed by CR3 may be un-populated, and we need handle it in such situation. Signed-off-by: Jiang, Yunhong <yunhong.jiang@intel.com> xen-unstable changeset: 22574:b5418c045d02 xen-unstable date: Tue Dec 21 18:09:34 2010 +0000
* tools/python: fix xm list for Python 2.7Keir Fraser2010-12-202-1/+10
| | | | | | | | | | | | This patch fixes Unexpected error: <type 'exceptions.AttributeError'> This is due to xmlrpc changes in Python 2.7. This patch should fixe it for both old and new versions. Signed-off-by: Michael Young <m.a.young@durham.ac.uk> Signed-off-by: Ian Jackson <ian.jackson@eu.citrix.com> xen-unstable changeset: 22045:2940165380de xen-unstable date: Thu Aug 19 17:09:30 2010 +0100
* tools: fetch remote changesets when force refetching/resetting qemuKeir Fraser2010-12-171-0/+1
| | | | | | | | | | | This makes "make tools/ioemu-dir-force-update" usable for picking up an entirely new QEMU_TAG. Signed-off-by: Ian Campbell <ian.campbell@citrix.com> Acked-by: Ian Jackson <ian.jackson@eu.citrix.com> Signed-off-by: Ian Jackson <ian.jackson@eu.citrix.com> xen-unstable changeset: 22425:d6c2695f05eb xen-unstable date: Tue Nov 23 19:29:13 2010 +0000
* tools: provide explicit target for refetching/resetting qemuKeir Fraser2010-12-172-0/+12
| | | | | | | | | | | | | | | This patch adds an explicit update mechanism: make tools/ioemu-dir-force-update This isn't brilliant but is better than doing "cd tools/ioemu-remote && git reset --hard <sha1...>" by hand. Note that invoking this target will destroy all working tree changes made to qemu-xen. Acked-by: Ian Jackson <ian.jackson@eu.citrix.com> Signed-off-by: Ian Jackson <ian.jackson@eu.citrix.com> xen-unstable changeset: 22381:2bedffabbcab xen-unstable date: Tue Nov 09 18:15:25 2010 +0000
* tools/python: Replace python string exceptions with ValueError exceptionsKeir Fraser2010-12-174-4/+4
| | | | | | | | | | | | | | | | | | | There are at least some syntax errors when trying to use the xen utils with python2.6. The attached patch changes these string exception into ValueErrors: - tools/python/xen/util/bugtool.py (getBugTitle) - tools/python/xen/xend (class XendBase): not catched - tools/python/xen/xm/xenapi_create.py (sxp2xmlconvert_sxp_to_xml): the method already raises a ValueError for similiar condition. - tools/python/xen/xm/main.py (xm_network_attach): not catched. For all but maybe the first one, the replacement of the string exceptions into ValueErrors seems to be safe. Signed-off-by: Ian Jackson <ian.jackson@eu.citrix.com> xen-unstable changeset: 22153:95c90bd63aed xen-unstable date: Tue Sep 14 17:46:21 2010 +0100
* tools/hotplug/Linux: Avoid dependency on iptables conntrack module.Keir Fraser2010-12-171-4/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Checking for RELATED,ESTABLISHED traffic being sent to a domU requires connection tracking, which adds unexpected (to most users) load to dom0. Heavily loaded systems can fill the conntrack tables. So avoid this, be more liberal in what we accept, and leave it to domU to police its own input. Signed-off-by: Keir Fraser <keir@xen.org> xen-unstable changeset: 22573:ff1b80ccecd9 xen-unstable date: Fri Dec 17 16:12:37 2010 +0000 tools/hotplug/Linux: supply --physdev-is-bridged in iptables runes With newer (pvops) kernels logs get flooded with this iptables warning: physdev match: using --physdev-out in the OUTPUT, FORWARD and POSTROUTING chains for non-bridged traffic is not supported anymore Using the --physdev-is-bridged option prevents this. See also: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=571634#10 Signed-off-by: Sander Eikelenboom <linux@eikelenboom.it> Signed-off-by: Ian Jackson <ian.jackson@eu.citrix.com> xen-unstable changeset: 22385:b0fe8260cefa xen-unstable date: Wed Nov 10 14:37:19 2010 +0000
* x86, atomic: Fix 32-bit version of atomic_write64().Keir Fraser2010-12-171-1/+1
| | | | | | Signed-off-by: Keir Fraser <keir@xen.org> xen-unstable changeset: 22572:e3fd86244491 xen-unstable date: Fri Dec 17 14:16:41 2010 +0000
* vtd: Reinstate ACPI DMAR on system shutdown or S3/S4/S5.Keir Fraser2010-12-176-16/+42
| | | | | | Signed-off-by: Keir Fraser <keir@xen.org> xen-unstable changeset: 22570:f2dba7ff0828 xen-unstable date: Fri Dec 17 10:46:43 2010 +0000
* xentrace: Clean up initialisation.Keir Fraser2010-12-161-59/+47
| | | | | | | | Allocate no memory and print no debug messages when disabled. Signed-off-by: Keir Fraser <keir@xen.org> xen-unstable changeset: 22567:f5f3cf4e001f xen-unstable date: Thu Dec 16 20:07:03 2010 +0000
* x86: Define pte_{read,write}[_atomic] in terms of atomic_readNKeir Fraser2010-12-162-16/+8
| | | | | | Signed-off-by: Keir Fraser <keir@xen.org> xen-unstable changeset: 22565:1cc551716430 xen-unstable date: Thu Dec 16 19:36:35 2010 +0000
* x86: Define atomic_{read,write}{8,16,32,64} accessor functions.Keir Fraser2010-12-163-14/+42
| | | | | | | | | | | | These absolutely guarantee to read/write a uint*_t with a single atomic processor instruction. Also re-define atomic_read/atomic_write (act on atomic_t) similarly. Signed-off-by: Keir Fraser <keir@xen.org> xen-unstable changeset: 22564:aa33ab320f7e xen-unstable date: Thu Dec 16 19:29:08 2010 +0000
* vtd: Require unmap_vtd_domain_page() on a couple of early exit paths.Keir Fraser2010-12-161-0/+2
| | | | | | | From: Jan Beulich <JBeulich@novell.com> Signed-off-by: Keir Fraser <keir@xen.org> xen-unstable changeset: 22549:aa18b8ddaf05 xen-unstable date: Thu Dec 16 15:38:57 2010 +0000
* x86/32on64: zero-extend hypercall index before use in memory access (debug ↵Keir Fraser2010-12-151-1/+2
| | | | | | | | mode only) Signed-off-by: Jan Beulich <jbeulich@novell.com> xen-unstable changeset: 22540:d8279118b4bb xen-unstable date: Wed Dec 15 12:10:31 2010 +0000
* x86-64: fix restoring of hypercall arguments after trace calloutKeir Fraser2010-12-151-2/+2
| | | | | | Signed-off-by: Jan Beulich <jbeulich@novell.com> xen-unstable changeset: 22539:20c65aa19075 xen-unstable date: Wed Dec 15 12:09:41 2010 +0000
* Reduce side effects of handling '*' debug keyKeir Fraser2010-12-153-4/+17
| | | | | | | | | NMI watchdog should be suppressed when dumping IRQ handlers. Softirqs should be handled periodically while processing non-IRQ handlers. Signed-off-by: Jan Beulich <jbeulich@novell.com> xen-unstable changeset: 22538:a3a29e67aa7e xen-unstable date: Wed Dec 15 12:04:34 2010 +0000
* ept: Remove lock in ept_get_entry, replace with access-once semantics.Keir Fraser2010-12-151-16/+24
| | | | | | | | | | | | | | | | | | | | | | | | This mirrors the RVI/shadow situation, where p2m read access is lockless because it's done in the hardware (linear map of the p2m table). This fixes the original bug (call it bug A) without introducing bug B (a deadlock). Bug A was caused by a race when updating p2m entries: between testing if it's valid, and testing if it's populate-on-demand, it may have been changed from populate-on-demand to valid. My original patch simply introduced a lock into ept_get_entry, but that caused bug B, caused by circular locking order: p2m_change_type [grabs p2m lock] -> set_p2m_entry -> ept_set_entry -> ept_set_middle_level -> p2m_alloc [grabs hap lock] write cr4 -> hap_update_paging_modes [grabes hap lock] -> hap_update_cr3 -> gfn_to_mfn -> ept_get_entry -> [grabs p2m lock] Signed-off-by: George Dunlap <george.dunlap@eu.citrix.com> xen-unstable changeset: 22526:7a5ee3800417 xen-unstable date: Wed Dec 15 10:47:05 2010 +0000
* tmem: two wrongs (or three lefts and a wrong) make a rightKeir Fraser2010-12-151-4/+4
| | | | | | | | | | | | These two bugs apparently complement each other enough that they escaped problems in my testing, but eventually gum up the works and are obviously horribly wrong. Found while developing tmem for native Linux. Signed-off-by: Dan Magenheimer <dan.magenheimer@oracle.com> xen-unstable changeset: 22525:01f3b3509023 xen-unstable date: Wed Dec 15 10:27:18 2010 +0000
* x86/iommu: account for necessary allocations when calculating Dom0'sKeir Fraser2010-12-151-0/+9
| | | | | | | | | | | | | | | | | | | | initial allocation size As of c/s 21812:e382656e4dcc, IOMMU related allocations for Dom0 happen only after it got all of its memory allocated, and hence the reserve (mainly for setting up its swiotlb) may get exhausted without accounting for the necessary allocations up front. While not precise, the estimate has been found to be within a couple of pages for the systems it got tested on. For the calculation to be reasonably correct, this depends on the patch titled "x86/iommu: don't map RAM holes above 4G" sent out yesterday. Signed-off-by: Jan Beulich <jbeulich@novell.com> xen-unstable changeset: 22506:618ba64260fa xen-unstable date: Tue Dec 14 09:54:10 2010 +0000
* x86 acpi: Follow Windows behaviour more closely during reset.Keir Fraser2010-12-152-8/+20
| | | | | | | | | | | | | | | | | | | This follows some changes proposed for upstream Linux: 1. Do not check the FADT reset register size/offset 2. Try ACPI poking twice during our reset attempt sequence Hopefully this will help us reset reliably on a wider range of platforms. Signed-off-by: Keir Fraser <keir@xen.org> xen-unstable changeset: 22482:91e0556f4d46 xen-unstable date: Fri Dec 10 11:32:19 2010 +0000 x86: acpi: Fix reboot attempt sequence. Signed-off-by: Keir Fraser <keir@xen.org> xen-unstable changeset: 22483:901c118b363e xen-unstable date: Fri Dec 10 16:40:05 2010 +0000
* tmem: Use of 'new' clashes with C++ reserved namespace.Keir Fraser2010-12-104-18/+18
| | | | | | | | Rename to 'creat', which does not conflict. Signed-off-by: Keir Fraser <keir@xen.org> xen-unstable changeset: 22481:0353037c6b95 xen-unstable date: Fri Dec 10 11:01:19 2010 +0000
* hvm: Fix merging error in hvm_op.hKeir Fraser2010-12-101-3/+4
| | | | | | | | | | | | | | | | | A couple of new hvm_op commands were erroneously ifdef'ed to be accessible only to the toolstack. Signed-off-by: Tim Deegan <Tim.Deegan@citrix.com> xen-unstable changeset: 22082:0eb89b465e46 xen-unstable date: Wed Sep 01 10:17:29 2010 +0100 hvm_op: Remove use of uint64_aligned_t from guest header file. Manually pad to the required alignment instead. Signed-off-by: Keir Fraser <keir.fraser@citrix.com> xen-unstable changeset: 22090:4a628af0355c xen-unstable date: Thu Sep 02 13:30:26 2010 +0100
* x86 hvm: Add a new HVMOP to get the current Xen system timeKeir Fraser2010-12-102-0/+17
| | | | | | | | | | Xen absolute system time, so that it can use SCHEDOP_poll in a sensible fashion. HVM PV drivers can't use the normal PV clock because they might have TSC offsets that hey don't know about. Signed-off-by: Tim Deegan <Tim.Deegan@citrix.com> xen-unstable changeset: 21772:2662f9c881fa xen-unstable date: Fri Jul 09 17:16:03 2010 +0100
* x86: time: tsc_set_info() must skip the idle domain.Keir Fraser2010-12-091-1/+1
| | | | | | Signed-off-by: Keir Fraser <keir@xen.org> xen-unstable changeset: 22473:a04430925a8b xen-unstable date: Thu Dec 09 16:15:10 2010 +0000
* Move IDLE_DOMAIN_ID defn to public header, and change DOMID_INVALID to fix ↵Keir Fraser2010-12-097-10/+12
| | | | | | | | clash. Signed-off-by: Keir Fraser <keir@xen.org> xen-unstable changeset: 22472:5ac189556629 xen-unstable ldate: Thu Dec 09 10:09:59 2010 +0000
* x86: Simplify tsc_set_info() slightly -- no domain has id DOMID_INVALID.Keir Fraser2010-12-091-1/+2
| | | | | | Signed-off-by: Keir Fraser <keir@xen.org> xen-unstable changeset: 22471:c9abf5fc5c52 xen-unstable date: Thu Dec 09 09:57:08 2010 +0000
* x86:vlapic: Fix possible guest tick losing after save/restoreKeir Fraser2010-12-091-1/+1
| | | | | | | | | Guest vcpu may totally lose all ticks if the vlapic->pt.irq was not restored during save/restore process. Fix it. Signed-off-by: Wei Gang <gang.wei@intel.com> xen-unstable changeset: 22470:0c97247c64d6 xen-unstable date: Thu Dec 09 08:34:59 2010 +0000
* x86/mm: change ASSERTs to BUG_ONs in mem_sharing.cKeir Fraser2010-12-091-2/+2
| | | | | | | | | | | These two ASSERTs have important side-effects so make them into BUG_ONs consistent with the rest of the file. Bug found by Jui-Hao Chiang <juihaochiang@gmail.com>. Signed-off-by: Tim Deegan <Tim.Deegan@citrix.com> xen-unstable changeset: 22467:89116f28083f xen-unstable date: Wed Dec 08 10:46:31 2010 +0000
* x86: remove BUG_ON() from QUIRK_IOAPIC_*_REGSEL handlerKeir Fraser2010-12-071-1/+4
| | | | | | | | | | | | | | | | | | Since (non-pvops, 32-bit only up to 2.6.27) Linux would report "BAD" unconditionally on all SiS chipset versions (it only looks for a PCI device at 0000:00:00.0 with SiS as the vendor), we must not crash if the report on a 64-bit hypervisor doesn't match the #define (which is zero). While we could honor the quirk indication even on 64-bit, it doesn't seem worthwhile, as there's no evidence that newer SiS chipsets (supporting 64-bit CPUs) are actually affected. This should also address bug 1687 (mis-reported, however, afaict). Signed-off-by: Jan Beulich <jbeulich@novell.com> xen-unstable changeset: 22466:bfd13358b8bf xen-unstable date: Tue Dec 07 18:32:04 2010 +0000
* x86: fix IRQ migration when using directed EOI (broken with c/s 20465)Keir Fraser2010-12-011-6/+19
| | | | | | | | | | | | | In directed-EOI mode, there is no chance to do the migration in mask_and_ack_level_ioapic_irq(), as the remote IRR bit can't possibly be clear after issuing the EOI to the LAPIC. Consequently, there's no point to even try. Instead, migration must be done in end_level_ioapic_irq(), and it requires masking the interrupt source prior to issuing the EOI to the IO-APIC. Signed-off-by: Jan Beulich <jbeulich@novell.com> xen-unstable changeset: 22452:62bf12040b0f xen-unstable date: Wed Dec 01 20:10:27 2010 +0000
* x86 hvm: Do not overwrite boot-cpu capability data on VMX/SVM startup.Keir Fraser2010-11-302-6/+0
| | | | | | | | | | | | | | | | Apparently required back in the earliest days of Xen, we now properly initialise CPU capabilities early during bootstrap. Re-writing capability data later now causes problems if specific features have been deliberately masked out. Thanks to Weidong Han at Intel for finding such a bug where XSAVE feature is masked out by default, but then erroneously written back during VMX initialisation. This would cause memory corruption problems during boot for XSAVE-capable systems. Signed-off-by: Keir Fraser <keir@xen.org> xen-unstable changeset: 22451:8420b82c22c2 xen-unstable date: Tue Nov 30 11:34:08 2010 +0000
* x86: tighten filter on ptwr_do_page_fault()Keir Fraser2010-11-291-7/+14
| | | | | | | | | | | | | | | Even not-so-recent Linux may, due to post-2.6.18 changes to the process creation code, cause quite a number (depending on environment and argument size) of faulting accesses to user space originating from kernel mode. Generally those happen for non-present pages and would lead to a nested page fault from guest_get_eff_l1e(). They can be avoided by checking for PFEC_page_present as long as the guest isn't running on shadow page tables. Signed-off-by: Jan Beulich <jbeulich@novell.com> Signed-off-by: Keir Fraser <keir@xen.org> xen-unstable changeset: 22449:3afb5ecbf69f xen-unstable date: Mon Nov 29 14:40:55 2010 +0000
* x86-64: don't crash Xen upon direct pv guest access to GDT/LDT mapping areaKeir Fraser2010-11-291-3/+9
| | | | | | | | | | | | | | | | | | | | | | | | | | handle_gdt_ldt_mapping_fault() is intended to deal with indirect accesses (i.e. those caused by descriptor loads) to the GDT/LDT mapping area only. While for 32-bit segment limits indeed prevent the function being entered for direct accesses (i.e. a #GP fault will be raised even before the address translation gets done, on 64-bit even user mode accesses would lead to control reaching the BUG_ON() at the beginning of that function. Fortunately the fix is simple: Since the guest kernel runs in ring 3, any guest direct access will have the "user mode" bit set, whereas descriptor loads always do the translations to access the actual descriptors as kernel mode ones. Signed-off-by: Jan Beulich <jbeulich@novell.com> Further, relax the BUG_ON() in handle_gdt_ldt_mapping_fault() to a check-and-bail. This avoids any problems in future, if we don't execute x86_64 guest kernels in ring 3 (e.g., because we use a lightweight HVM container). Signed-off-by: Keir Fraser <keir@xen.org> xen-unstable changeset: 22448:5cd9612db2bb xen-unstable date: Mon Nov 29 14:34:32 2010 +0000
* x86 hvm: Fix VPMU issue on Nehalem cpusKeir Fraser2010-11-221-0/+67
| | | | | | | | | Fix an issue on Nehalem cpus where performance counter overflows may lead to endless interrupt loops on this cpu. Signed-off-by: Dietmar Hahn <dietmar.hahn@ts.fujitsu.com> xen-unstable changeset: 22417:c0c1f5f0745e xen-unstable date: Mon Nov 22 19:16:34 2010 +0000
* x86: Check for MWAIT in CPUID before using it in ACPI idle code.Keir Fraser2010-11-221-1/+2
| | | | | | Signed-off-by: Keir Fraser <keir@xen.org> xen-unstable changeset: 22416:0cc4ed1ce1f3 xen-unstable date: Mon Nov 22 19:13:00 2010 +0000
* amd iommu: Fix HV crash with 32bit pv_ops kernelKeir Fraser2010-11-162-3/+2
| | | | | | | Signed-off-by: Wei Wang <wei.wang2@amd.com> Tested-by: Conny Seidel <conny.seidel@amd.com> xen-unstable changeset: 22389:9b2ca938cfe6 xen-unstable date: Tue Nov 16 11:28:33 2010 +0000
* x86: Automatically EOI guest-bound interrupts if guest takes too long.Keir Fraser2010-11-161-17/+62
| | | | | | Signed-off-by: Keir Fraser <keir.fraser@citrix.com> xen-unstable changeset: 22051:59ff5820534f xen-unstable date: Sun Aug 22 09:37:08 2010 +0100
* hvmloader: fix off-by-one-bit error when initialising PCI devicesKeir Fraser2010-11-101-7/+5
| | | | | | | | | | | | | | | | | | | | | | | hvmloader is responsible for - amoungst other things - initialising the PCI device BARs prior to loading the guest BIOS. The previous code only probed for devfn up to 128. The lower 3 bits are function IDs so this meant that only devices in slots 0-15 were actually being initialized. Signed-off-by: Alex Zeffertt <alex.zeffertt@eu.citrix.com> Acked-by: Gianni Tedesco <gianni.tedesco@citrix.com> xen-unstable changeset: 22383:cba667fb80cf xen-unstable date: Wed Nov 10 13:58:16 2010 +0000 hvmloader: Fix 22383:cba667fb80cf iterating over defns 0..255 We need to declare devfn as wider than 8 bits for a loop 0<devfn<256 to terminate. Signed-off-by: Keir Fraser <keir@xen.org> xen-unstable changeset: 22384:c19e3371f31b xen-unstable date: Wed Nov 10 14:15:23 2010 +0000
* x86 hvm: Fix MTRR physaddr-width check.Keir Fraser2010-11-093-32/+31
| | | | | | | | | Should be checking against physaddr width presented to teh guest, rather than the host physaddr width. Signed-off-by: Keir Fraser <keir@xen.org> xen-unstable changeset: 22374:9997a1418633 xen-unstable date: Tue Nov 09 11:48:43 2010 +0000
* tools: gdbsx: Check return of write()Keir Fraser2010-11-081-2/+8
| | | | | | | | | | Not checking leads to warn_unused_result checks triggering in some libraries and compilers. Combined with -Werror this breaks the build. Signed-off-by: Gianni Tedesco <gianni.tedesco@citrix.com> Signed-off-by: Ian Jackson <ian.jackson@eu.citrix.com> xen-unstable changeset: 22349:3f98881703aa xen-unstable date: Wed Nov 03 11:58:25 2010 +0000
* Fix "Error: Device 51952 not connected" error when using pygrubKeir Fraser2010-11-081-3/+6
| | | | | | | | | | | | | | | | | | | | | | | | The following is the process of booting a DomU with 'mounted-blktap2' (VHD for example) and 'pygrub' as bootloader: 1. Connect boot-device to Dom0 as '/dev/xpvd' 2. Pygrub get info for load DomU 3. Disconnect boot-device from Dom0 4. Boot DomU During step 3 the created device is disconnected from Dom0, but xenstore does not scrape away after the device is disconnected so you get the following error:     "Error: Device /dev/xvdp (51952, tap2) is already connected." During step 3 xend calls destroyDevice always with 'tap' as argument. Signed-off-by: eXeC001er <execooler@gmail.com> Signed-off-by: Stefano Stabellini <stefano.stabellini@eu.citrix.com> xen-unstable changeset: 21999:cd5b4135fe03 xen-unstable date: Mon Aug 16 17:11:30 2010 +0100
* tools/xenpaging: Add _XOPEN_SOURCE to fix build problems with recent gccKeir Fraser2010-11-081-0/+1
| | | | | | | | | | This patch fixes compilation issues with gcc version 4.1.2 20061115 (prerelease) (Debian 4.1.1-21). Signed-off-by: Daniel Kiper <dkiper@net-space.pl> Signed-off-by: Ian Jackson <ian.jackson@eu.citrix.com> xen-unstable changeset: 22023:af6799abc6e9 xen-unstable date: Wed Aug 18 16:48:25 2010 +0100
* VT-d: fix device assignment failure (regression from Xen c/s 19805:2f1fa2215e60)Keir Fraser2010-11-031-15/+8
| | | | | | | | | | | | | | If the device at <secbus>:00.0 is the device the mapping operation was initiated for, trying to map it a second time will fail, and hence this second mapping attempt must be prevented (as was done prior to said c/s). While at it, simplify the code a little, too. Signed-off-by: Jan Beulich <jbeulich@novell.com> Acked-by: Weidong Han <weidong.han@intel.com> xen-unstable changeset: 22348:2dfba250c50b xen-unstable date: Wed Nov 03 08:18:51 2010 +0000
generated by cgit v1.2.3 (git 2.25.1) at 2024-06-02 23:08:53 +0000