aboutsummaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* Update Xen version to 4.1.2-rc14.1.2-rc1Keir Fraser2011-08-252-2/+2
|
* x86: don't limit dom0's maximum reservation by the available memoryDavid Vrabel2011-08-241-1/+1
| | | | | | | | | | | | | | Set dom0's initial maximum reservation using the max value supplied in the dom0_mem command line option without limiting it by the available memory. This allows dom0 to make use of any hotplugged memory without having to also adjust the maximum reservation. Signed-off-by: David Vrabel <david.vrabel@citrix.com> Acked-by: Jan Beulich <jbeulich@novell.com> xen-unstable changeset: 23790:1515138fbd7b xen-unstable date: Wed Aug 24 09:33:10 2011 +0100
* x86: use 'dom0_mem' to limit the number of pages for dom0David Vrabel2011-08-221-0/+2
| | | | | | | | | | | Use the 'dom0_mem' command line option to set the maximum number of pages for dom0. dom0 can use then use the XENMEM_maximum_reservation memory op to automatically find this limit and reduce the size of any page tables etc. Signed-off-by: David Vrabel <david.vrabel@citrix.com> xen-unstable changeset: 23779:c56dd5eb0fa2 xen-unstable date: Mon Aug 22 10:05:27 2011 +0100
* cpuidle: initialize default Cstate informationKevin Tian2011-08-222-57/+114
| | | | | | | | | | | C0/C1 should be always available when cpuidle is enabled in Xen. When there's case that Dom0 doesn't register ACPI Cstate information, e.g. due to BIOS issue or acpi processor module is not installed, this patch provides basic C0/C1 information available to xenpm tool. Signed-off-by: Kevin Tian <kevin.tian@intel.com> xen-unstable changeset: 23662:2faba14bac13 xen-unstable date: Fri Jul 08 08:32:37 2011 +0100
* x86/KEXEC: disable hpet legacy broadcasts earlierAndrew Cooper2011-08-192-3/+4
| | | | | | | | | | | | | | | | | | | | | On x2apic machines which booted in xapic mode, hpet_disable_legacy_broadcast() sends an event check IPI to all online processors. This leads to a protection fault as the genapic blindly pokes x2apic MSRs while the local apic is in xapic mode. One option is to change genapic when we shut down the local apic, but there are still problems with trying to IPI processors in the online processor map which are actually sitting in NMI loops Another option is to have each CPU take itself out of the online CPU map during the NMI shootdown. Realistically however, disabling hpet legacy broadcasts earlier in the kexec path is the easiest fix to the problem. Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com> xen-unstable changeset: 23776:0ddb4481f883 xen-unstable date: Fri Aug 19 09:58:22 2011 +0100
* x86/PCI-MSI: properly determine VF BAR valuesJan Beulich2011-08-166-71/+195
| | | | | | | | | | | | | | | | | | | | | | As was discussed a couple of times on this list, SR-IOV virtual functions have their BARs read as zero - the physical function's SR-IOV capability structure must be consulted instead. The bogus warnings people complained about are being eliminated with this change. Signed-off-by: Jan Beulich <jbeulich@novell.com> xen-unstable changeset: 23766:8d6edc3d26d2 xen-unstable date: Sat Aug 13 10:14:58 2011 +0100 PCI: consolidate interface for adding devices The functionality of pci_add_device_ext() can be easily folded into pci_add_device(), and eliminates the need to change two functions for future adjustments. Signed-off-by: Jan Beulich <jbeulich@novell.com> xen-unstable changeset: 23725:4dc6a9ba90d6 xen-unstable date: Tue Jul 19 14:14:08 2011 +0100
* x86: IRQ fix incorrect logic in __clear_irq_vectorAndrew Cooper2011-08-161-0/+1
| | | | | | | | | | | | | | | | In the old code, tmp_mask is the cpu_and of cfg->cpu_mask and cpu_online_map. However, in the usual case of moving an IRQ from one PCPU to another because the scheduler decides its a good idea, cfg->cpu_mask and cfg->old_cpu_mask do not intersect. This causes the old cpu vector_irq table to keep the irq reference when it shouldn't. This leads to a resource leak if a domain is shut down wile an irq has a move pending, which results in Xen's create_irq() eventually failing with -ENOSPC when all vector_irq tables are full of stale references. Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com> xen-unstable changeset: 23765:68b903bb1b01 xen-unstable date: Sat Aug 13 10:14:28 2011 +0100
* VT-d: don't reject valid DMAR/ATSR tables on systems with multiple PCI segmentsJan Beulich2011-08-161-4/+6
| | | | | | | | | | | | | | | | On multi-PCI-segment systems, each segment has to be expected to have an include-all DRHD and an all-ports ATSR, so the firmware consistency check incorrectly rejects valid configurations there (which is particularly problematic when the firmware also pre-enabled x2apic mode, as the system will panic in that case due to being unable to enable interrupt remapping). Thus constrain the check to just segment 0 for now; once full multi-segment support is there (which I'm working on), it can be revisited whether we'd want to track this per segment, or whether we trust the firmware of such large systems. Signed-off-by: Jan Beulich <jbeulich@novell.com> xen-unstable changeset: 23763:8f647d409196 xen-unstable date: Sat Aug 13 10:12:49 2011 +0100
* Revert 23092:0f2b9b6c5a74Keir Fraser2011-08-161-1/+7
| | | | | | It has broken unmodified Windows HVM guests for some users: Signed-off-by: Keir Fraser <keir@xen.org>
* Passthrough: disable bus-mastering on any card that causes an IOMMU fault.Tim Deegan2011-08-122-2/+22
| | | | | | | | | This stops the card from raising back-to-back faults and live-locking the CPU that handles them. Signed-off-by: Tim Deegan <tim@xen.org> Acked-by: Wei Wang2 <wei.wang2@amd.com> Acked-by: Allen M Kay <allen.m.kay@intel.com>
* VT-d: always clean up dpci timers.Tim Deegan2011-07-251-3/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | If a VM has all its PCI devices deassigned, need_iommu(d) becomes false but it might still have DPCI EOI timers that were init_timer()d but not yet kill_timer()d. That causes xen to crash later because the linked list of inactive timers gets corrupted, e.g.: (XEN) Xen call trace: (XEN) [<ffff82c480126256>] set_timer+0x1c2/0x24f (XEN) [<ffff82c48011fbf8>] schedule+0x129/0x5dd (XEN) [<ffff82c480122c1e>] __do_softirq+0x7e/0x89 (XEN) [<ffff82c480122c9d>] do_softirq+0x26/0x28 (XEN) [<ffff82c480153c85>] idle_loop+0x5a/0x5c (XEN) (XEN) (XEN) **************************************** (XEN) Panic on CPU 0: (XEN) Assertion 'entry->next->prev == entry' failed at /local/scratch/tdeegan/xen-unstable.hg/xen/include:172 (XEN) **************************************** The following patch makes sure that the domain destruction path always clears up the DPCI state even if !needs_iommu(d). Signed-off-by: Tim Deegan <Tim.Deegan@citrix.com> xen-unstable changeset: 23746:aa54b8175954 xen-unstable date: Mon Jul 25 16:41:33 2011 +0100
* xend: remove PCI device listing from NetBSD, since it's LinuxRoger Pau Monne2011-07-231-0/+1
| | | | | | | | specific code. Signed-off-by: Roger Pau Monne <roger.pau@entel.upc.edu> xen-unstable changeset: 23738:88847c424eec xen-unstable date: Sat Jul 23 08:58:37 2011 +0100
* xen: Fix sedf schedulerGeorge Dunlap2011-07-231-10/+15
| | | | | | | | | Update the sedf scheduler to be compatible with the most recent generic scheduler interface changes. Signed-off-by: George Dunlap <george.dunlap@eu.citrix.com> xen-unstable changeset: 23732:3795d79c740b xen-unstable date: Thu Jul 21 14:35:31 2011 +0100
* xend NetBSD init script: fixed problem when restarting xendRoger Pau Monne2011-07-211-2/+5
| | | | | | | | | | When restarting xend, the rc.d script was unable to find the pid of the running xend, so no process was restarted. Signed-off-by: Roger Pau Monne <roger.pau@entel.upc.edu> Committed-by: Ian Jackson <ian.jackson@eu.citrix.com> xen-unstable changeset: 23712:e298ce67777e xen-unstable date: Mon Jul 18 14:38:31 2011 +0100
* tools: xencommons NetBSD init script: Multiple bugfixes and improvementsRoger Pau Monne2011-07-211-12/+33
| | | | | | | | | | | | | | | Added a cleanup of the xenstore database, to purge old entries, prevented the restart of xenstore and set Domain-0 name. Also replaced the sleep 5 (wait for xenstore to come up) with the method used in the linux init script. Signed-off-by: Roger Pau Monne <roger.pau@entel.upc.edu> Acked-by: Ian Campbell <ian.campbell@citrix.com> Acked-by: Christoph Egger <Christoph.Egger@amd.com> Acked-by: Ian Jackson <ian.jackson@eu.citrix.com> Committed-by: Ian Jackson <ian.jackson@eu.citrix.com> xen-unstable changeset: 23699:6fe9f26bb9ae xen-unstable date: Fri Jul 15 18:22:03 2011 +0100
* xend: NetBSD portability fix for LVM raw volume namesRoger Pau Monne2011-07-211-1/+1
| | | | | | | | | | | | | | Xen 4.1.1 was incorrectly passing /dev/rmapper/vg-lvname to pygrub (notice the r in front of mapper), when it should pass /dev/mapper/rvg-lvname (add the r to the last file) when using NetBSD. I've patched it to work correctly. I'm attaching a unified diff with the patch made against Xen 4.1.1 (it's a really simple modification). From: Roger Pau Monne <roger.pau@entel.upc.edu> Signed-off-by: Ian Jackson <ian.jackson@eu.citrix.com> Committed-by: Ian Jackson <ian.jackson@eu.citrix.com> xen-unstable changeset: 23629:89ce3439686b xen-unstable date: Tue Jun 28 13:56:53 2011 +0100
* tools/ocaml: ask compiler for correct libraryMike McClurg2011-07-211-1/+1
| | | | | | | | | | | | | | | OCaml libraries will live in /usr/local/ if the user compiles OCaml from source. This patch asks the OCaml compiler where we should look for libraries. NB: it may be that we should do the same thing for the NetBSD case, but I don't have a BSD box to test this out. Signed-off-by: Mike McClurg <mike.mcclurg@citrix.com> Signed-off-by: Ian Jackson <ian.jackson@eu.citrix.com> Committed-by: Ian Jackson <ian.jackson@eu.citrix.com> xen-unstable changeset: 23566:7e5b54d1643e xen-unstable date: Tue Jun 21 18:01:51 2011 +0100
* hvmloader: Switch to absolute addressing for calling hypercall stubs.Keir Fraser2011-07-204-269/+270
| | | | | | | | | | | | | | | | | | This is clearer and less fragile than trying to make relative calls work. In particular, the old approach failed if _start was not == HVMLOADER_PHYSICAL_ADDRESS. This was the case for some modern toolchains which reorder functions. Signed-off-by: Keir Fraser <keir@xen.org> xen-unstable changeset: 23730:dd5eecf739d1 xen-unstable date: Wed Jul 20 15:02:16 2011 +0100 hvmloader: Remove hard tabs from source files. Signed-off-by: Keir Fraser <keir@xen.org> xen-unstable changeset: 23729:4f1109af9c63 xen-unstable date: Wed Jul 20 14:52:16 2011 +0100
* libxc: remove obsolete comment.Ian Campbell2011-07-201-4/+0
| | | | | | | | Seems to predate Xen 3.0... Signed-off-by: Ian Campbell <ian.campbell@citrix.com> xen-unstable changeset: 23707:9afeab10a65d xen-unstable date: Sat Jul 16 09:18:45 2011 +0100
* x86: fix guest migration after c/s 20892:d311d1efc25eJan Beulich2011-07-161-1/+1
| | | | | | | | | | | | | | Guests would not manage to run successfully after being migrated to a host having sufficiently much more memory than the host they were originally started on. Subsequently the plan is to re-enable the changes behavior under the control of a guest kernel announced feature flag. Signed-off-by: Jan Beulich <jbeulich@novell.com> Acked-by: Ian Campbell <ian.campbell@citrix.com> xen-unstable changeset: 23706:3dd399873c9e xen-unstable date: Sat Jul 16 09:18:21 2011 +0100
* xen/libxc: set CPUID topology leaf as unsupported for PV guestsDavid Vrabel2011-07-162-0/+2
| | | | | | | | | | | | | | | | | The result of a CPUID Extended Topology Enumeration leaf for PV guests is invalid as the level in ECX is ignored. This can cause some guests to loop endlessly when trying to enumerate the topology. Since the physical topology isn't useful to PV guests set the topology leaf as unsupported. Guests affected include Linux kernels prior 2.6.32 where a workaround was applied ("xen: mask extended topology info in cpu", 82d6469916c6fcfa345636a49004c9d1753905d1). Signed-off-by: David Vrabel <david.vrabel@citrix.com> xen-unstable changeset: 23700:867bb675b57b xen-unstable date: Sat Jul 16 09:05:45 2011 +0100
* [IA64] kexec: fix ia64 buildKUWAMURA Shin'ya2011-07-081-1/+1
| | | | | | | | | | | | 23408:1fc3347850c7 causes the following error: machine_kexec.c:106: error: static declaration of 'machine_kexec_get_xen' follows non-static declaration /xen-unstable.hg/xen/include/xen/kexec.h:39: error: previous declaration of 'machine_kexec_get_xen' was here Signed-off-by: KUWAMURA Shin'ya <kuwa@jp.fujitsu.com> xen-unstable changeset: 23667:4c70f4c5a8a3 xen-unstable date: Fri Jul 08 08:39:26 2011 +0100
* KEXEC: disconnect all PCI devices from the PCI bus on crashAndrew Cooper2011-07-083-0/+24
| | | | | | | | | | | | | | | | | | | | | | In the case of a crash, IOMMU DMA remapping gets turned off so that the kdump kernel may boot. However, this is warned as being dangerous in the VTD specification if a DMA transaction is in progress. Also, in the case of a crash, DMA transactions and interrupts from peripheral devices such as network cards are likely to keep coming in. Without DMA remapping enabled, the transactions will be writing over low memory, corrupting the crash state, and perhaps even the kdump reserved memory. Therefore, on the crash path, we can disconnect all PCI devices from their respective buses so that they are no longer able to be DMA busmasters. This reduces the risk of DMA transactions corrupting state (and will also reduce spurious interrupts arriving to the kdump kernel) until the kdump kernel and properly reset the PCI devices. Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com> xen-unstable changeset: 23666:b96f8bdcaa15 xen-unstable date: Fri Jul 08 08:38:35 2011 +0100
* x86/hvm: Don't expose CPUID time leaf when not using PVRDTSCPPaul Durrant2011-07-081-2/+10
| | | | | | | | | | | | Some versions of Oracle's Solaris PV drivers make a check that the maximal Xen hypervisor CPUID leaf is <= base leaf + 2 and refuse to work if this is not the case. The addition of the time leaf makes the maximal leaf == base leaf + 3 so this patch introduces a workaround that obscures the time leaf unless PVRDTSCP is in operation. Signed-off-by: Paul Durrant <paul.durrant@citrix.com> xen-unstable changeset: 23661:8fe6f4be18aa xen-unstable date: Fri Jul 08 08:31:10 2011 +0100
* x86 cpu: Fix bug: unify cpu_dev attr as __cpuinitdataLiu, Jinsong2011-07-084-5/+5
| | | | | | | | | | | | Currently different x86 cpu define different attr for cpu_dev. Some cpu define as __initdata, this would be risk under cpu hotplug. This patch fix the bug, unify them as __cpuinitdata, as what AMD cpu define now. Signed-off-by: Liu, Jinsong <jinsong.liu@intel.com> Shan, Haitao <haitao.shan@intel.com> xen-unstable changeset: 23659:7fe0331986c5 xen-unstable date: Fri Jul 08 08:30:41 2011 +0100
* x86: fix boot-time watchdog test.Tim Deegan2011-06-281-1/+11
| | | | | | | | | | | | Since the perf counter that the LAPIC NMI watchdog uses only runs while the core isn't halted, and all APs are idle at this point in the boot process, it's possible that remote CPUs won't see any NMIs during the 10-tick waiting period. Force all CPUs to busy-wait so we know the timers are running. Signed-off-by: Tim Deegan <Tim.Deegan@citrix.com> xen-unstable changeset: 23612:6c7a23e08a04 xen-unstable date: Tue Jun 28 09:16:13 2011 +0100
* xen-detect: Fix cpuid asm for 32-bit PIC compilation.Keir Fraser2011-06-231-17/+20
| | | | | | Signed-off-by: Keir Fraser <keir@xen.org> xen-unstable changeset: 23553:eca057e4475c xen-unstable date: Fri Jun 17 08:08:13 2011 +0100
* tasklets: Switch a few tasklets to run in softirq context.Keir Fraser2011-06-234-7/+11
| | | | | | | | | There are a couple of others which may also be safe. I've converted only the most obvious one. Signed-off-by: Keir Fraser <keir@xen.org> xen-unstable changeset: 23552:7b4a45a4075d xen-unstable date: Thu Jun 16 16:57:22 2011 +0100
* tasklets: Allow tasklets to be created that run in softirq context.Keir Fraser2011-06-233-28/+84
| | | | | | | | | Where this is safe, it can reduce latency and cpu overhead compared with scheduling the idle vcpu to perform the same tasklet work. Signed-off-by: Keir Fraser <keir@xen.org> xen-unstable changeset: 23551:3ff057cbb16b xen-unstable date: Thu Jun 16 16:56:31 2011 +0100
* pv-on-hvm: hvm_domain_use_pirq return positive no matter if the evtchn is boundStefano Stabellini2011-06-231-7/+1
| | | | | | | | | | | | This patch fixes PV on HVM interrupt remapping with recent Linux kernels and upstream qemu. hvm_domain_use_pirq should return positive even if the evtchn is not currently bound. If it doesn't assert_irq ends up injecting legacy interrupts even after the guest disabled the irq. Signed-off-by: Stefano Stabellini <stefano.stabellini@eu.citrix.com> xen-unstable changeset: 23550:fb5f0febeddc xen-unstable date: Thu Jun 16 16:17:35 2011 +0100
* Protect xen/stdarg.h for multiple inclusion.Keir Fraser2011-06-231-0/+5
| | | | | | Signed-off-by: Keir Fraser <keir@xen.org> xen-unstable changeset: 23549:a574bf2f5059 xen-unstable date: Thu Jun 16 16:14:51 2011 +0100
* x86: Backport CPUID feature passthroughs from xen-unstableKeir Fraser2011-06-235-3/+13
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Enable RDWRGSFS feature support for HVM guests Write/read FS/GS base instructions enable user level code to read/write FS & GS segment base registers for thread local storage. Signed-off-by: Yang, Wei <wei.y.yang@intel.com> xen-unstable changeset: 23539:8c75f35d55f6 xen-unstable date: Wed Jun 15 16:06:48 2011 +0100 x86: Pass through ERMS CPUID feature for HVM and PV guests This patch exposes ERMS feature to HVM and PV guests. The REP MOVSB/STOSB instruction can enhance fast strings attempts to move as much of the data with larger size load/stores as possible. Signed-off-by: Yang, Wei <wei.y.yang@intel.com> xen-unstable changeset: 23516:f4a47275aebf xen-unstable date: Tue Jun 14 13:13:18 2011 +0100 x86/hvm: Make DRNG feature visible in CPUID This patch exposes DRNG feature to HVM guests. The RDRAND instruction can provide software with sequences of random numbers generated from white noise. Signed-off-by: Yang, Wei <wei.y.yang@intel.com> xen-unstable changeset: 23510:864a3dd1d9b4 xen-unstable date: Tue Jun 14 12:44:48 2011 +0100
* x86/hvm: add SMEP support to HVM guestKeir Fraser2011-06-235-5/+35
| | | | | | | | | | | | | | | | | | | | | Intel new CPU supports SMEP (Supervisor Mode Execution Protection). SMEP prevents software operating with CPL < 3 (supervisor mode) from fetching instructions from any linear address with a valid translation for which the U/S flag (bit 2) is 1 in every paging-structure entry controlling the translation for the linear address. This patch adds SMEP support to HVM guest. Signed-off-by: Yang Wei <wei.y.yang@intel.com> Signed-off-by: Shan Haitao <haitao.shan@intel.com> Signed-off-by: Li Xin <xin.li@intel.com> Signed-off-by: Tim Deegan <Tim.Deegan@citrix.com> xen-unstable changeset: 23504:c34604d5a293 xen-unstable date: Mon Jun 06 13:46:48 2011 +0100
* x86: Enable Supervisor Mode Execution Protection (SMEP)Keir Fraser2011-06-235-27/+75
| | | | | | | | | | | | | | | | | | | | Intel new CPU supports SMEP (Supervisor Mode Execution Protection). SMEP prevents software operating with CPL < 3 (supervisor mode) from fetching instructions from any linear address with a valid translation for which the U/S flag (bit 2) is 1 in every paging-structure entry controlling the translation for the linear address. This patch enables SMEP in Xen to protect Xen hypervisor from executing pv guest instructions, whose translation paging-structure entries' U/S flags are all set. Signed-off-by: Yang Wei <wei.y.yang@intel.com> Signed-off-by: Shan Haitao <haitao.shan@intel.com> Signed-off-by: Li Xin <xin.li@intel.com> Signed-off-by: Keir Fraser <keir@xen.org> xen-unstable changeset: 23481:0c0884fd8b49 xen-unstable date: Fri Jun 03 21:39:00 2011 +0100
* kexec: Backport fixes from xen-unstableKeir Fraser2011-06-2315-8/+189
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | KEXEC: prevent panic on the kexec path when talking to the DMAR hardware Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com> xen-unstable changeset: 23547:b5955b9fc26c xen-unstable date: Thu Jun 16 16:11:13 2011 +0100 KEXEC: correctly revert x2apic state when kexecing Introduce the boolean variable 'kexecing' which indicates to functions whether we are on the kexec path or not. This is used by disable_local_APIC() to try and revert the APIC mode back to how it was found on boot. We also need some fudging of the x2apic_enabled variable. It is used in multiple places over the codebase to mean multiple things, including: What did the user specifify on the command line? Did the BIOS boot me in x2apic mode? Is the BSP Local APIC in x2apic mode? What mode is my Local APIC in? Therefore, set it up to prevent a protection fault when disabling the IOAPICs. (In this case, it is used in the "What mode is my Local APIC in?" case, so the processor doesnt suffer a protection fault because of trying to use x2apic MSRs when it should be using xapic MMIO) Finally, make sure that interrupts are disabled when jumping into the purgatory code. It would be bad to service interrupts in the Xen context when the next kernel is booting. Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com> xen-unstable changeset: 23542:23c068b10923 xen-unstable date: Wed Jun 15 16:16:41 2011 +0100 IOMMU: add crash_shutdown iommu_op The kdump kernel has problems booting with interrupt/dma remapping enabled, so we need a new iommu_ops called crash_shutdown which is basically suspend but doesn't need to bother saving state. Make sure that crash_shutdown is called on the kexec path. Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com> xen-unstable changeset: 23541:c6307ddd3ab1 xen-unstable date: Wed Jun 15 16:10:11 2011 +0100 IOMMU VTD BUG: disable Extended Interrupt Mode when disabling Interupt Remapping Experimental evidence shows that Extended Interrupt Mode remains in effect even after Interrupt Remapping is disabled in each DMAR Global Command Register. A consiquence of this is that when we switch from x2apic mode back to xapic mode, and disable interrupt remapping for the kdump kernel, interrupts passing through the IO APICs are in x2apic format as opposed xapic. This causes a triple fault in the kexec kernel. As EIM is explicitly set up each time Interrup Remapping is enabled, it is safe for us to clobber this when taring down. Also, change the header definition of IRTA_REG_EIME_SHIFT. It caused verbose and error-prone code, and was only used in 1 place before. We now have IRTA_EIME which is the specific bit in the register. Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com> xen-unstable changeset: 23540:96f53d2b966e xen-unstable date: Wed Jun 15 16:07:45 2011 +0100 IOMMU VTD BUG: disable Extended Interrupt Mode when disabling Interrupt Remapping Experimental evidence shows that Extended Interrupt Mode remains in effect even after Interrupt Remapping is disabled in each DMAR Global Command Register. A consiquence of this is that when we switch from x2apic mode back to xapic mode, and disable interrupt remapping for the kdump kernel, interrupts passing through the IO APICs are in x2apic format as opposed xapic. This causes a triple fault in the kexec kernel. As EIM is explicitly set up each time Interrup Remapping is enabled, it is safe for us to clobber this when taring down. Also, change the header definition of IRTA_REG_EIME_SHIFT. It caused verbose and error-prone code, and was only used in 1 place before. We now have IRTA_EIME which is the specific bit in the register. Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com> xen-unstable changeset: 23515:337520d94cba xen-unstable date: Tue Jun 14 13:04:09 2011 +0100 x86/apic: record local APIC state on boot Xen does not store the boot local APIC state which leads to problems when shutting down for a kexec jump. This patch records the boot state so we can return to the boot state when kexecing. Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com> Signed-off-by: Keir Fraser <keir@xen.org> Acked-by: Jan Beulich <jbeulich@novell.com> xen-unstable changeset: 23514:d04608ad70f8 xen-unstable date: Tue Jun 14 13:02:00 2011 +0100 x86/kexec: nmi_shootdown_cpus() should leave irqs disabled Signed-off-by: Keir Fraser <keir@xen.org> xen-unstable changeset: 23513:595a0c0804a9 xen-unstable date: Tue Jun 14 12:49:41 2011 +0100
* tools/hotplug/Linux: start all xen daemons in runlevel 2Fabio Fantoni2011-06-213-6/+6
| | | | Signed-off-by: Fabio Fantoni <fabio.fantoni@heliman.it>
* x86_emulate: Fix decode of FUCOMIP %stN.Keir Fraser2011-06-151-1/+1
| | | | | | Signed-off-by: Keir Fraser <keir@xen.org> xen-unstable changeset: 23546:d25f2c114ace xen-unstable date: Wed Jun 15 20:33:58 2011 +0100
* x86-64: fix incorrect assertion in __maddr_to_virt()Jan Beulich2011-06-151-1/+1
| | | | | | | | | | When memory map sparseness reduction is in use, machine address ranges can't validly be compared directly against the total size of the direct mapping range. Signed-off-by: Jan Beulich <jbeulich@novell.com> xen-unstable changeset: 23543:a8edfacd4b5e xen-unstable date: Wed Jun 15 20:24:09 2011 +0100
* x86/hvm: Crash domain rather than guest on unexpected PIO IO stateGeorge Dunlap2011-06-151-1/+3
| | | | | | | | | | | | | | | | | Under certain conditions, if an IO gets into an unexpected state, hvmemul_do_io can return X86EMUL_UNHANDLEABLE. Unfortunately, handle_pio() does not expect this state, and calls BUG() if it sees it, crashing the host. Other HVM io-related code crashes the guest in this case. This patch makes handle_pio() do the same. The crash was seen when executing crash_guest in dom0 to forcibly crash the guest. Signed-off-by: George Dunlap <george.dunlap@eu.citrix.com> xen-unstable changeset: 23538:35b4220c98bc xen-unstable date: Wed Jun 15 16:05:14 2011 +0100
* x86/apic: fix potential Protection Fault during shutdownAndrew Cooper2011-06-151-1/+2
| | | | | | | | | | | | | | | | | | | | | This is a rare case, but if the BIOS is set to uniprocessor, and Xen is booted with 'lapic x2apic', Xen will switch into x2apic mode, which will cause a protection fault when disabling the local APIC. This leads to a general protection fault as this code is also in the fault handler. When x2apic mode is enabled, the only tranlsation which does not result in a protection fault is to clear both the EN and EXTD bits, which is safe to do in all cases, even if you are in xapic mode rather than x2apic mode. The linux code from which this is derrived is protected by an if ( ! x2apic_mode ...) clause which is how they get away with it. Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com> Acked-by: Jan Beulich <jbeulich@novell.com> xen-unstable changeset: 23512:0feb98534a87 xen-unstable date: Tue Jun 14 12:47:45 2011 +0100
* x86: Fix argument checking in (privileged) function cpu_add().Keir Fraser2011-06-151-1/+3
| | | | | | | | Thanks to John McDermott <john.mcdermott@nrl.navy.mil> for spotting. Signed-off-by: Keir Fraser <keir@xen.org> xen-unstable changeset: 23505:5a557fda70a9 xen-unstable date: Fri Jun 10 08:08:44 2011 +0100
* Update Xen version to 4.1.2-rc1-preKeir Fraser2011-06-151-1/+1
|
* Added signature for changeset ab0e3dac2c63Keir Fraser2011-06-141-0/+1
|
* Added tag RELEASE-4.1.1 for changeset ab0e3dac2c63Keir Fraser2011-06-141-0/+1
|
* Update Xen version to 4.1.1RELEASE-4.1.1Keir Fraser2011-06-142-2/+2
|
* Added signature for changeset e302291362a4Keir Fraser2011-06-031-0/+1
|
* Added tag 4.1.1-rc2 for changeset e302291362a4Keir Fraser2011-06-031-0/+1
|
* Update Xen version to 4.1.1-rc24.1.1-rc2Keir Fraser2011-06-032-2/+2
|
* x86: Hide CPUID leaf 7 from PV guests.Keir Fraser2011-06-023-1/+19
| | | | | | | | Except for the whitelisted FSGSBASE feature. Signed-off-by: Keir Fraser <keir@xen.org> xen-unstable changeset: 23461:5839e797a130 xen-unstable date: Thu Jun 02 14:39:50 2011 +0100
* x86: Replace ad-hoc bitmaskof() macro with single cpufeat_mask() defn.Keir Fraser2011-06-024-9/+7
| | | | | | Signed-off-by: Keir Fraser <keir@xen.org> xen-unstable changeset: 23460:c72869c8ae02 xen-unstable date: Thu Jun 02 14:34:34 2011 +0100
generated by cgit v1.2.3 (git 2.25.1) at 2024-06-02 18:47:41 +0000