aboutsummaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* Update Xen version to 4.0.2-rc24.0.2-rc2Keir Fraser2011-02-102-2/+2
|
* amd iommu: Fix a xen crash after pci-attachKeir Fraser2011-02-101-0/+6
| | | | | | | | | | pci-detach triggers IO page table deallocation if the last passthru device has been removed from pdev list, and this will result a BUG on amd systems for next pci-attach. This patch fixes this issue. Signed-off-by: Wei Wang <wei.wang2@amd.com> xen-unstable changeset: 22872:cba9a84d32fb xen-unstable date: Sun Feb 06 16:54:01 2011 +0000
* x86/hvm: don't let domains call HVMOP_set_mem_type on themselves.Tim Deegan2011-02-091-0/+4
| | | | | | Signed-off-by: Tim Deegan <Tim.Deegan@citrix.com> xen-unstable changeset: 22879:098c8a6483c9 xen-unstable date: Mon Feb 07 09:39:59 2011 +0000
* Revert 21334:993458f6c5a0 (xen-unstable 22071:c5aed2e049bc).Keir Fraser2011-02-071-6/+0
| | | | Signed-off-by: Keir Fraser <keir@xen.org>
* trace: Change trace_var argument to void*, to match __trace_varKeir Fraser2011-02-061-1/+1
| | | | | | Signed-off-by: George Dunlap <george.dunlap@eu.citrix.com> xen-unstable changeset: 22877:575d2f40acc4 xen-unstable date: Sun Feb 06 17:22:44 2011 +0000
* hvm amd: Fix 32bit guest VM save/restore issues associated with SYSENTER MSRsKeir Fraser2011-02-061-15/+26
| | | | | | | | | | | | This patch turn-on SYSENTER MSRs interception for 32bit guest VMs on AMD CPUs. With it, hvm_svm.guest_sysenter_xx fields always contain the canonical version of SYSENTER MSRs and are used in guest save/restore. The data fields in VMCB save area are updated as necessary. Reported-by: James Harper <james.harper@bendigoit.com.au> Signed-off-by: Wei Huang <wei.huang2@amd.com> xen-unstable changeset: 22873:186162762071 xen-unstable date: Sun Feb 06 17:03:09 2011 +0000
* x86: Fix pirq teardown on domain destruction.Wei Gang2011-01-261-3/+0
| | | | | | | | | | | The privilege check in unmap_domain_pirq() fails since the teardown completes in RCU (idle domain) context. We can remove the check since it is covered in physdev_op() already, which is the only potentially unprivileged caller. Signed-off-by: Wei Gang <gang.wei@intel.com> xen-unstable changeset: 22816:e7f44fb4ecc3 xen-unstable date: Wed Jan 26 08:54:12 2011 +0000
* x86: blacklist new AMD CPUID bits for PV domainsKeir Fraser2011-01-264-0/+20
| | | | | | | | | | | | | | there are some new CPUID bits (and leaves) which Dom0 and PV domains should not see to avoid trouble, since we don't emulate the features. The most prominent one is a topology leaf, which contains information specific to the physical CPU, not the virtual one. To avoid confusion (and possibly crashes) due to a confused Dom0 scheduler simply disable these bits. Signed-off-by: Andre Przywara <andre.przywara@amd.com> Signed-off-by: Keir Fraser <keir@xen.org> xen-unstable changeset: 22815:4785c70c2b6d xen-unstable date: Wed Jan 26 08:45:40 2011 +0000
* x86: Do not pollute namespace with asm defns of PERFC_*.Keir Fraser2011-01-267-11/+11
| | | | | | | | This fixes the build with perfc=y. Signed-off-by: Keir Fraser <keir@xen.org> xen-unstable changeset: 22814:b9017fdaad4d xen-unstable date: Wed Jan 26 08:35:24 2011 +0000
* x86/tsc: remove misleading printk on HVM restore path.Keir Fraser2011-01-251-5/+0
| | | | | | | | This warning no longer corresponds to what the code actually does. Signed-off-by: Tim Deegan <Tim.Deegan@citrix.com> xen-unstable changeset: 22800:c50ae9d5dda4 xen-unstable date: Tue Jan 25 14:05:25 2011 +0000
* x86_emulate: set the operand size for SMSW/reg writeback.Keir Fraser2011-01-211-2/+1
| | | | | | | | | Otherwise it defaults to 0 bytes. Signed-off-by: Tim Deegan <Tim.Deegan@citrix.com> Signed-off-by: Keir Fraser <keir@xen.org> xen-unstable changeset: 22782:fe8a177ae9cb xen-unstable date: Wed Jan 19 15:29:04 2011 +0000
* xen: fix XEN_DOMCTL_memory_mapping to not return with domain RCU lock heldKeir Fraser2011-01-181-4/+4
| | | | | | | | Broken in 20358:ecc649ec3675 Signed-off-by: Ian Campbell <ian.campbell@citrix.com> xen-unstable changeset: 22775:e4688c57c230 xen-unstable date: Tue Jan 18 09:04:04 2011 +0000
* xen: stringify assertion condition for printing sooner.Keir Fraser2011-01-182-3/+3
| | | | | | | | | | | | | | | So that: (XEN) Assertion '!(((*({ unsigned long __ptr; __asm__ ("" : "=r"(__ptr) : "0"(&per_cpu____preempt_count)); (typeof(&per_cpu____preempt_count)) (__ptr + (get_cpu_info()->per_cpu_offset)); }))) || ((irq_stat[(((get_cpu_info()->processor_id)1... becomes: (XEN) Assertion '"!in_atomic()"' failed at softirq.c:61 Signed-off-by: Ian Campbell <ian.campbell@citrix.com> xen-unstable changeset: 22774:96441daf4a5b xen-unstable date: Tue Jan 18 09:01:57 2011 +0000
* pv-drivers: use PCI interfaces to request IO and MEM resources on platform ↵Keir Fraser2011-01-141-13/+9
| | | | | | | | | | | | | | | | device This is the correct interface to use and something has broken the use of the previous incorrect interface (which fails because the request conflicts with the resources assigned for the PCI device itself instead of nesting like the PCI interfaces do). pci_request_region() has been available since at least Linux 2.6.5. Signed-off-by: Ian Campbell <ian.campbell@citrix.com> Signed-off-by: Jan Beulich <jbeulich@novell.com> xen-unstable changeset: 22747:7bc5e072d986 xen-unstable date: Fri Jan 14 08:02:26 2011 +0000
* kexec: fix ia64 build for 21300:8bdf09baff30KUWAMURA Shin'ya2011-01-141-0/+5
| | | | | | | | | | On ia64, 21300:8bdf09baff30 introduces the following error: xen/common/kexec.c:490: undefined reference to `continue_hypercall_on_cpu' The function continue_hypercall_on_cpu() is defined only on x86. Signed-off-by: KUWAMURA Shin'ya <kuwa@jp.fujitsu.com>
* VT-d: fix ia64 buildKeir Fraser2011-01-141-0/+8
| | | | | | | | The identifier `dest_LowestPrio' is defined on only x86. Signed-off-by: KUWAMURA Shin'ya <kuwa@jp.fujitsu.com> xen-unstable changeset: 22092:e0ec7b10f8ce xen-unstable date: Thu Sep 02 13:36:23 2010 +0100
* stubdom: Fix stubdom-dm using "grep" improperlyJohn Weekes2011-01-141-1/+1
| | | | | | | | | | | | | | | | | | | | stubdom-dm uses "grep" on "xm list" output to determine whether it is already running. The existing behavior is to use "grep $domname-dm" but this will result in a false-positive in the case of another domU running whose name ends with the full new name; for instance, if "abctest-dm" is running, a new "test-dm" will spin forever, waiting for it the end. Any easy fix is to have it use "grep -w" instead of "grep", searching for the whole word only. It also might be worth considering a switch to "xl list" from "xm list", here and in other places. Signed-off-by: John Weekes <lists.xen@nuclearfallout.net> Committed-by: Ian Jackson <ian.jackson@eu.citrix.com> xen-unstable changeset: 22714:6852e3e7ef58 xen-unstable date: Tue Jan 11 16:42:41 2011 +0000
* x86: don't crash when a CPU cannot be brought online during bootKeir Fraser2011-01-111-4/+7
| | | | | | | x86_cpu_to_apicid[] gets set to BAD_APICID when bringup of a secondary CPU fails, yet srat_detect_node() wants to use this as array index. Signed-off-by: Jan Beulich <jbeulich@novell.com>
* Update Xen version to 4.0.2-rc2-preKeir Fraser2011-01-111-1/+1
|
* Added signature for changeset 0bd829255a3fKeir Fraser2011-01-101-0/+1
|
* Added tag 4.0.2-rc1 for changeset 0bd829255a3fKeir Fraser2011-01-101-0/+1
|
* 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
generated by cgit v1.2.3 (git 2.25.1) at 2024-06-12 06:02:31 +0000