aboutsummaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* Update Xen version to 4.1.3RELEASE-4.1.3Keir Fraser2012-08-092-2/+2
|
* cpufreq: P state stats aren't available if there is no cpufreq driverDavid Vrabel2012-08-091-0/+2
| | | | | | | | | | | | | If there is no cpufreq driver (e.g., with an AMD Opteron 8212) then reading the P state statistics causes a deadlock as an uninitialized spinlock is locked in do_get_pm_info(). The spinlock is initialized in cpufreq_statistic_init() which is not called if cpufreq_driver == NULL. Signed-off-by: David Vrabel <david.vrabel@citrix.com> Committed-by: Jan Beulich <jbeulich@suse.com> xen-unstable changeset: 25706:7fd5facb6084 xen-unstable date: Fri Aug 03 09:50:28 2012 +0200
* xen: only check for shared pages while any exist on teardownIan Campbell2012-08-091-0/+2
| | | | | | | | | | | Avoids worst case behavour when guest has a large p2m. This is XSA-11 / CVE-2012-3433 Signed-off-by: Tim Deegan <tim@xen.org> Signed-off-by: Ian Campbell <ian.campbell@citrix.com> Tested-by: Olaf Hering <olaf@aepfle.de> Committed-by: Ian Jackson <ian.jackson@eu.citrix.com>
* nestedhvm: fix nested page fault build error on 32-bitIan Campbell2012-08-034-5/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | cc1: warnings being treated as errors hvm.c: In function ‘hvm_hap_nested_page_fault’: hvm.c:1282: error: passing argument 2 of ‘nestedhvm_hap_nested_page_fault’ from incompatible pointer type /local/scratch/ianc/devel/xen-unstable.hg/xen/include/asm/hvm/nestedhvm.h:55: note: expected ‘paddr_t *’ but argument is of type ‘long unsigned int *’ hvm_hap_nested_page_fault takes an unsigned long gpa and passes &gpa to nestedhvm_hap_nested_page_fault which takes a paddr_t *. Since both of the callers of hvm_hap_nested_page_fault (svm_do_nested_pgfault and ept_handle_violation) actually have the gpa which they pass to hvm_hap_nested_page_fault as a paddr_t I think it makes sense to change the argument to hvm_hap_nested_page_fault. The other user of gpa in hvm_hap_nested_page_fault is a call to p2m_mem_access_check, which currently also takes a paddr_t gpa but I think a paddr_t is appropriate there too. Jan points out that this is also an issue for >4GB guests on the 32 bit hypervisor. Signed-off-by: Ian Campbell <ian.campbell@citrix.com> Acked-by: Jan Beulich <jbeulich@suse.com> Acked-by: Tim Deegan <tim@xen.org> Committed-by: Ian Campbell <ian.campbell@citrix.com> xen-unstable changeset: 25724:612898732e66 xen-unstable date: Fri Aug 03 09:54:17 2012 +0100 Backported-by: Keir Fraser <keir@xen.org>
* Intel VT-d: Dump IOMMU supported page sizesSantosh Jodh2012-08-031-0/+9
| | | | | | Signed-off-by: Santosh Jodh <santosh.jodh@citrix.com> xen-unstable changeset: 25725:9ad379939b78 xen-unstable date: Fri Aug 03 10:38:04 2012 +0100
* x86: fix off-by-one in nr_irqs_gsi calculationJan Beulich2012-07-301-1/+1
| | | | | | | | | | highest_gsi() returns the last valid GSI, not a count. Signed-off-by: Jan Beulich <jbeulich@suse.com> Acked-by: Joe Jin <joe.jin@oracle.com> Acked-by: Keir Fraser <keir@xen.org> xen-unstable changeset: 25688:e6266fc76d08 xen-unstable date: Fri Jul 27 12:22:13 2012 +0200
* vt-d: fix wrong addr in IOTLB invalidation descriptorYang Zhang2012-07-301-1/+1
| | | | | | | | | | According to vt-d specs, the addr in IOTLB invalidation descriptor should be 4K page aligned. Signed-off-by: Yang Zhang <yang.z.zhang@Intel.com> Committed-by: Keir Fraser <keir@xen.org> xen-unstable changeset: 25617:75eb78d6cf54 xen-unstable date: Thu Jul 19 15:46:02 2012 +0100
* Revert xen-unstable:25487:baa85434d0ec. Not applicable to 4.1 branch.Keir Fraser2012-07-301-1/+0
|
* Update Xen version to 4.1.3-rc4-preKeir Fraser2012-07-301-1/+1
|
* x86/hvm: don't leave emulator in inconsistent stateJan Beulich2012-07-261-0/+2
| | | | | | | | | | | | | | | | | | | | | | The fact that handle_mmio(), and thus the instruction emulator, is being run through twice for emulations that require involvement of the device model, allows for the second run to see a different guest state than the first one. Since only the MMIO-specific emulation routines update the vCPU's io_state, if they get invoked on the second pass, internal state (and particularly this variable) can be left in a state making successful emulation of a subsequent MMIO operation impossible. Consequently, whenever the emulator invocation returns without requesting a retry of the guest instruction, reset io_state. [ This is a security issue. XSA#10. -iwj ] Signed-off-by: Jan Beulich <jbeulich@suse.com> Acked-by: Keir Fraser <keir@xen.org> Committed-by: Ian Jackson <ian.jackson@eu.citrix.com> xen-unstable changeset: 25682:ffcb24876b4f Committed-by: Ian Jackson <ian.jackson@eu.citrix.com>
* Added signature for changeset 5cdcfed7b5b1Keir Fraser2012-07-221-0/+1
|
* Added tag 4.1.3-rc3 for changeset 5cdcfed7b5b1Keir Fraser2012-07-221-0/+1
|
* Update Xen version to 4.1.3-rc34.1.3-rc3Keir Fraser2012-07-222-2/+2
|
* passthrough: fix xsm-related oversightJan Beulich2012-07-191-1/+1
| | | | | | | | | | Presumably a copy-and-paste mistake, which I also didn't notice while unifying x86's and ia64's respective domctl implementations. Signed-off-by: Jan Beulich <jbeulich@suse.com> Acked-by: Keir Fraser <keir@xen.org> xen-unstable changeset: 25432:d7318231cfe3 xen-unstable date: Thu May 31 10:18:52 2012 +0200
* x86/PCI: fix guest_io_read() when pci_cfg_ok() denies accessJan Beulich2012-07-091-1/+1
| | | | | | | | | | | | | | | | For a multi-byte aligned read, this so far resulted in 0x00ff to be put in the guest's register rather than 0xffff or 0xffffffff, which in turn could confuse bus scanning functions (which, when reading vendor and/or device IDs, expect to get back all zeroes or all ones). As the value gets masked to the read width when merging back into the full result, setting the initial value to all ones should not harm any or the other cases. Signed-off-by: Jan Beulich <jbeulich@suse.com> Acked-by: Keir Fraser <keir@xen.org> xen-unstable changeset: 25489:cc46bd403bc4 xen-unstable date: Fri Jun 22 10:04:30 2012 +0200
* x86/mm: fix mod_l1_entry() return value when encountering r/o MMIO pageJan Beulich2012-07-091-0/+1
| | | | | | | | | | | | | | While putting together the workaround announced in http://lists.xen.org/archives/html/xen-devel/2012-06/msg00709.html, I found that mod_l1_entry(), upon encountering a set bit in mmio_ro_ranges, would return 1 instead of 0 (the removal of the write permission is supposed to be entirely transparent to the caller, even more so to the calling guest). Signed-off-by: Jan Beulich <jbeulich@suse.com> Acked-by: Keir Fraser <keir@xen.org> xen-unstable changeset: 25487:baa85434d0ec xen-unstable date: Thu Jun 21 11:30:59 2012 +0200
* SVM: fix performance decrease with asid assignmentChristoph Egger2012-07-091-1/+2
| | | | | | | | | | Do not clear asid cleanbit unconditionally. This shaves off 100 cycles from the VMRUN instruction. Signed-off-by: Christoph Egger <Christoph.Egger@amd.com> Committed-by: Jan Beulich <jbeulich@suse.com> xen-unstable changeset: 25482:34c725807d21 xen-unstable date: Wed Jun 13 11:51:26 2012 +0200
* xen: Fix schedule()'s grabbing of the schedule lockGeorge Dunlap2012-07-091-3/+4
| | | | | | | | | | | | | | Because the location of the lock can change between the time you read it and the time you grab it, the per-cpu schedule locks need to check after lock acquisition that the lock location hasn't changed, and release and re-try if so. This change was effected throughout the source code, but one very important place was apparently missed: in schedule() itself. Signed-off-by: George Dunlap <george.dunlap@eu.citrix.com> Committed-by: Keir Fraser <keir@xen.org> xen-unstable changeset: 25162:478bec603d3d xen-unstable date: Tue Apr 10 10:41:30 2012 +0100
* x86/cpuidle: deny access to the I/O port used for EM_SYSIOJan Beulich2012-07-091-0/+4
| | | | | | | | | Nothing, not even Dom0, should fiddle with this. Signed-off-by: Jan Beulich <jbeulich@suse.com> Acked-by: Keir Fraser <keir@xen.org> xen-unstable changeset: 24970:33980e36597b xen-unstable date: Tue Mar 06 16:41:41 2012 +0100
* x86/cpuidle: add Westmere-EX support to hw residencies reading logicJan Beulich2012-07-091-0/+1
| | | | | | | | | | This is in accordance with http://software.intel.com/en-us/articles/intel-processor-identification-with-cpuid-model-and-family-numbers/ Signed-off-by: Jan Beulich <jbeulich@suse.com> Acked-by: Haitao Shan <maillists.shan@gmail.com> xen-unstable changeset: 24261:64088ba60263 xen-unstable date: Wed Nov 30 10:23:41 2011 +0100
* xen, vtd: Fix device check for devices behind PCIe-to-PCI bridgesGeorge Dunlap2012-07-091-5/+58
| | | | | | | | | | | | | | | | | | | | On some systems, requests devices behind a PCIe-to-PCI bridge all appear to the IOMMU as though they come from from slot 0, function 0 on that device; so the mapping code much punch a hole for X:0.0 in the IOMMU for such devices. When punching the hole, if that device has already been mapped once, we simply need to check ownership to make sure it's legal. To do so, domain_context_mapping_one() will look up the device for the mapping with pci_get_pdev() and look for the owner. However, if there is no device in X:0.0, this look up will fail. Rather than returning -ENODEV in this situation (causing a failure in mapping the device), try to get the domain ownership from the iommu context mapping itself. Signed-off-by: George Dunlap <george.dunlap@eu.citrix.com> xen-unstable changeset: 23813:5535d7ce2673 xen-unstable date: Mon Sep 05 15:00:46 2011 +0100
* pm: don't truncate processors' ACPI IDs to 8 bitsJan Beulich2012-07-093-4/+10
| | | | | | | | | This is just another adjustment to allow systems with very many CPUs (or unusual ACPI IDs) to be properly power-managed. Signed-off-by: Jan Beulich <jbeulich@novell.com> xen-unstable changeset: 23781:0849b0e59e24 xen-unstable date: Mon Aug 22 10:10:39 2011 +0100
* x86: update Intel CPUID masking code to latest specJan Beulich2012-07-094-4/+34
| | | | | | | | | | | | | | | | | | | | | | ..., which adds masking of the xsave feature leaf. Also add back (and fix to actually make it do what it was supposed to do from the beginning) the printing of what specific masking couldn't be done in case the user requested something the hardware doesn't support. Signed-off-by: Jan Beulich <jbeulich@novell.com> xen-unstable changeset: 23726:fd97ca086df6 xen-unstable date: Tue Jul 19 14:14:51 2011 +0100 x86: add change missing in c/s 23726:fd97ca086df6 The early "do we need to do anything" check needs adjustment, too. Thanks to Haitao Shan for pointing this out. Signed-off-by: Jan Beulich <jbeulich@novell.com> xen-unstable changeset: 23731:48f72b389b04 xen-unstable date: Thu Jul 21 14:34:51 2011 +0100
* tools/pygrub: fix solaris kernel sniffZhigang Wang2012-07-091-2/+5
| | | | | | | | | | | | | | | Solaris 11 build 163+ removes '/platform/i86xpv/kernel/unix' and only the 64-bit PV kernel file '/platform/i86xpv/kernel/amd64/unix' exists. This patch fixes the detection. Signed-off-by: Zhigang Wang <zhigang.x.wang@oracle.com> Signed-off-by: Kurt Hackel <kurt.hackel@oracle.com> Signed-off-by: Frank Che <frank.che@oracle.com> Committed-by: Ian Jackson <ian.jackson@eu.citrix.com> xen-unstable changeset: 23686:7c39a2c0d870 xen-unstable date: Thu Jul 14 18:09:58 2011 +0100
* xen: Fix off-by-one error when parsing command line argumentsAndrew Cooper2012-07-031-1/+1
| | | | | | | | | | | | | | | As Xen currently stands, it will attempt to interpret the first few bytes of the initcall section as a struct kernel_param. The reason that this not caused problems is because in the overflow case, param->name is actually a function pointer to the first initcall, and intepreting it as string is very unlikely to match an ASCII command line parameter name. Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com> Committed-by: Keir Fraser <keir@xen.org> xen-unstable changeset: 25587:2cffb7bf6e57 xen-unstable date: Tue Jul 03 13:38:19 2012 +0100
* x86/nmi: Fix deadlock in unknown_nmi_error()Andrew Cooper2012-07-031-4/+4
| | | | | | | | | | | Additionally, correct the text description to reflect what is being done, and make use of fatal_trap() in preference to kexec_crash() in case an unknown NMI occurs before a kdump kernel has been loaded. Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com> Committed-by: Keir Fraser <keir@xen.org> xen-unstable changeset: 25478:6d1a30dc47e8 xen-unstable date: Mon Jun 11 15:12:50 2012 +0100
* x86_64: Fix off-by-one error setting up the Interrupt Stack TablesAndrew Cooper2012-07-032-4/+6
| | | | | | | | | | | | | | | | | | | | | | The Interrupt Stack Table entries in a 64bit TSS are a 1 based data structure as far as hardware is concerned. As a result, the code setting up stacks in subarch_percpu_traps_init() fills in the wrong IST entries. The result is that the MCE handler executes on the stack set up for NMIs; the NMI handler executes on a stack set up for Double Faults, and Double Faults are executed with a stack pointer set to 0. Once the #DF handler starts to execute, it will usually take a page fault looking up the address at 0xfffffffffffffff8, which will cause a triple fault. If a guest has mapped a page in that location, then it will have some state overwritten, but as the #DF handler always calls panic(), this is not a problem the guest will have time to care about. Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com> Committed-by: Keir Fraser <keir@xen.org> xen-unstable changeset: 25271:54da0329e259 xen-unstable date: Thu May 10 11:04:32 2012 +0100
* tools/ocaml: Fix 2 bit-twiddling bugs and an off-by-oneZheng Li2012-07-031-3/+3
| | | | | | | | | | | | The bit bugs are in ocaml vcpu affinity calls, and the off-by-one error is in the ocaml console ring code Signed-off-by: Zheng Li <zheng.li@eu.citrix.com> Acked-by: Ian Campbell <ian.campbell.com> Committed-by: Ian Jackson <ian.jackson.citrix.com> Acked-by: Jon Ludlam <jonathan.ludlam@eu.citrix.com> xen-unstable changeset: 23940:187d59e32a58 xen-unstable date: Mon Oct 10 16:41:16 2011 +0100
* x86: Make asmlinkage explicitly a no-op, and avoid usage in arch/x86Keir Fraser2012-06-2016-44/+42
| | | | | | Signed-off-by: Keir Fraser <keir@xen.org> xen-unstable changeset: 24511:a141f6d64916 xen-unstable date: Sun Jan 15 22:02:35 2012 +0000
* Update Xen version to 4.1.3-rc3-preKeir Fraser2012-06-201-1/+1
|
* Added signature for changeset acbd36176913Keir Fraser2012-06-181-0/+1
|
* Added tag 4.1.3-rc2 for changeset acbd36176913Keir Fraser2012-06-181-0/+1
|
* Update Xen version to 4.1.3-rc24.1.3-rc2Keir Fraser2012-06-182-2/+2
|
* x86-64: detect processors subject to AMD erratum #121 and refuse to bootJan Beulich2012-06-122-0/+11
| | | | | | | | | | | | | | | Processors with this erratum are subject to a DoS attack by unprivileged guest users. This is XSA-9 / CVE-2012-2934. Signed-off-by: Jan Beulich <JBeulich@suse.com> Signed-off-by: Ian Campbell <ian.campbell@citrix.com> Committed-by: Ian Jackson <ian.jackson@eu.citrix.com> xen-unstable changeset: 25481:422880dc94a4 xen-unstable date: Tue Jun 12 11:33:42 2012 +0100 Committed-by: Ian Jackson <ian.jackson@eu.citrix.com>
* x86-64: fix #GP generation in assembly codeJan Beulich2012-06-123-20/+27
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When guest use of sysenter (64-bit PV guest) or syscall (32-bit PV guest) gets converted into a GP fault (due to no callback having got registered), we must - honor the GP fault handler's request the keep enabled or mask event delivery - not allow TBF_EXCEPTION to remain set past the generation of the (guest) exception in the vCPU's trap_bounce.flags, as that would otherwise allow for the next exception occurring in guest mode, should it happen to get handled in Xen itself, to nevertheless get bounced to the guest kernel. Also, just like compat mode syscall handling already did, native mode sysenter handling should, when converting to #GP, subtract 2 from the RIP present in the frame so that the guest's GP fault handler would see the fault pointing to the offending instruction instead of past it. Finally, since those exception generating code blocks needed to be modified anyway, convert them to make use of UNLIKELY_{START,END}(). [ This bug is security vulnerability, XSA-8 / CVE-2012-0218. ] Signed-off-by: Jan Beulich <jbeulich@suse.com> Acked-by: Keir Fraser <keir@xen.org> Committed-by: Jan Beulich <jbeulich@suse.com> xen-unstable changeset: 25200:80f4113be500 25204:569d6f05e1ef Committed-by: Ian Jackson <ian.jackson@eu.citrix.com>
* x86_64: Do not execute sysret with a non-canonical return addressJan Beulich2012-06-121-0/+11
| | | | | | | | | | | | | | | | | | | Check for non-canonical guest RIP before attempting to execute sysret. If sysret is executed with a non-canonical value in RCX, Intel CPUs take the fault in ring0, but we will necessarily already have switched to the the user's stack pointer. This is a security vulnerability, XSA-7 / CVE-2012-0217. Signed-off-by: Jan Beulich <JBeulich@suse.com> Signed-off-by: Ian Campbell <Ian.Campbell@citrix.com> Signed-off-by: Ian Jackson <ian.jackson@eu.citrix.com> Acked-by: Keir Fraser <keir.xen@gmail.com> Committed-by: Ian Jackson <ian.jackson@eu.citrix.com> xen-unstable changeset: 25480:76eaf5966c05 xen-unstable date: Tue Jun 12 11:33:40 2012 +0100 Committed-by: Ian Jackson <ian.jackson@eu.citrix.com>
* x86/cpuidle: do not flush cache unless entering C3Wei Wang2012-05-252-2/+5
| | | | | | | | | | | Nor is there a need to disable bus master arbitration in that case. Signed-off-by: Wei Wang <wei.wang2@amd.com> Modified-by: Zhang, Yang Z <yang.z.zhang@intel.com> Signed-off-by: Jan Beulich <jbeulich@suse.com> Committed-by: Jan Beulich <jbeulich@suse.com> xen-unstable changeset: 25195:a06e6cdeafe3 xen-unstable date: Mon Apr 16 13:05:28 2012 +0200
* blktap2: Fix naked unchecked uses of read/write/chdir.Keir Fraser2012-05-1412-14/+62
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | These cause warnings under warn_unused_result, and for read/write we ought to deal with partial io results. Signed-off-by: Keir Fraser <keir@xen.org> xen-unstable changeset: 25299:01d64a3dea71 xen-unstable date: Fri May 11 18:30:29 2012 +0100 blktap2: Fix another uninitialised value error gcc -O1 -fno-omit-frame-pointer -m32 -march=i686 -g -fno-strict-aliasing -std=gnu99 -Wall -Wstrict-prototypes -Wdeclaration-after-statement -D__XEN_TOOLS__ -MMD -MF .block-remus.o.d -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -fno-optimize-sibling-calls -mno-tls-direct-seg-refs -Werror -g -Wno-unused -fno-strict-aliasing -I../include -I../drivers -I/home/osstest/build.12828.build-i386/xen-unstable/tools/blktap2/drivers/../../../tools/libxc -I/home/osstest/build.12828.build-i386/xen-unstable/tools/blktap2/drivers/../../../tools/include -D_GNU_SOURCE -DUSE_NFS_LOCKS -c -o block-remus.o block-remus.c block-remus.c: In function 'ramdisk_flush': block-remus.c:508: error: 'buf' may be used uninitialized in this function make[5]: *** [block-remus.o] Error 1 This is because gcc can see that merge_requests doesn't always set *mergedbuf but gcc isn't able to prove that it always does so if merge_requests returns 0 and that in that case the value of ramdisk_flush::buf isn't used. This is too useful a warning to disable, despite the occasional false positive of this form. The conventional approach is to suppress the warning by explicitly initialising the variable to 0. This has just come to light because 25275:27d63b9f111a reenabled optimisation for this area of code, and gcc's data flow analysis (which is required to trigger the uninitialised variable warning) only occurs when optimisation is turned on. Signed-off-by: Ian Jackson <ian.jackson@eu.citrix.com> xen-unstable changeset: 25281:60064411a8a9 xen-unstable date: Thu May 10 14:26:14 2012 +0100 blktap2: Do not build with -O0 Signed-off-by: Keir Fraser <keir@xen.org> xen-unstable changeset: 25275:27d63b9f111a xen-unstable date: Thu May 10 11:22:18 2012 +0100 blktap2: Fix uninitialised value error. Signed-off-by: Keir Fraser <keir@xen.org> xen-unstable changeset: 25274:cb82b5aa73bd xen-unstable date: Thu May 10 11:21:59 2012 +0100 tools/blktap2: fix out of bounds access in block-log.c block-log.c: In function 'ctl_close_sock': block-log.c:363:23: warning: array subscript is above array bounds [-Warray-bounds] Adjust loop condition in ctl_close_sock() to fix warning. Adjust array acccess in ctl_close() to actually access the array member. Signed-off-by: Olaf Hering <olaf@aepfle.de> Acked-by: Ian Jackson <ian.jackson@eu.citrix.com> Committed-by: Keir Fraser <keir@xen.org> xen-unstable changeset: 25273:83a02f225bde xen-unstable date: Thu May 10 11:20:04 2012 +0100 tools/blktap2: fix build errors caused by Werror in vhd_journal_write_entry -O2 -Wall -Werror triggers these warnings: libvhd-journal.c: In function 'vhd_journal_write_entry': libvhd-journal.c:335: warning: statement with no effect Really return the error from vhd_journal_write() to caller. v2: - simplify the patch by just adding the missing return statement Signed-off-by: Olaf Hering <olaf@aepfle.de> Committed-by: Keir Fraser <keir@xen.org> xen-unstable changeset: 25272:ca02580986d2 xen-unstable date: Thu May 10 11:19:05 2012 +0100
* unmodified_drivers: remove inclusion of asm/system.hOlaf Hering2012-05-141-1/+0
| | | | | | | | | | | Allow compilation of PVonHVM drivers with forward-ported xenlinux sources in openSuSE 12.2. Since Linux 3.4 asm/system.h is not present anymore. Remove inclusion of this header, its not needed. Signed-off-by: Olaf Hering <olaf@aepfle.de> Committed-by: Jan Beulich <jbeulich@suse.com> xen-unstable changeset: 25327:cc7a054a5a27 xen-unstable date: Mon May 14 12:04:27 2012 +0200
* unmodified drivers: use upstream sync_bitops if availableJan Beulich2012-05-141-0/+10
| | | | | | | | | | | | The forward ported xenlinux sources in openSuSE 12.2 were switched from the old synch_bitops to the sync_bitops since kernel version 3.3. Add compat macros to use either old or new helpers depending on used kernel source version. Signed-off-by: Jan Beulich <jbeulich@suse.com> Signed-off-by: Olaf Hering <olaf@aepfle.de> xen-unstable changeset: 25069:46bf3ab42baf xen-unstable date: Fri Mar 16 11:35:06 2012 +0100
* unmodified drivers: add pfn_is_ram helper for kdumpOlaf Hering2012-05-141-0/+29
| | | | | | | | | | | | Register pfn_is_ram helper speed up reading /proc/vmcore in the kdump kernel. It is compiled only if the kernel source is recent enough to have the pfn_is_ram helper (v3.0-rc1, commit 997c136f518c5debd63847e78e2a8694f56dcf90). Signed-off-by: Olaf Hering <olaf@aepfle.de> Committed-by: Jan Beulich <jbeulich@suse.com> xen-unstable changeset: 25068:e4460795ee66 xen-unstable date: Fri Mar 16 11:34:41 2012 +0100
* unmodified drivers: hide xen_cpuid_base() in version 2.6.38+Olaf Hering2012-05-141-0/+2
| | | | | | | | | | | | | | | | | | | | | | | | | Allow compilation of PVonHVM drivers with forward-ported xenlinux sources in openSuSE 12.1. xen_cpuid_base() is now in mainline, the copy in the xen tree leads to a compilation error. The current state leads to a compile error: /usr/src/packages/BUILD/xen-4.2.24547/non-dbg/obj/default/platform-pci/platform-pci.c:121: error: redefinition of 'xen_cpuid_base' /usr/src/linux-3.0.13-0.11/arch/x86/include/asm/xen/hypervisor.h:43: error: previous definition of 'xen_cpuid_base' was here The reason is that the kernel sources are searched before the xen sources for asm/hypervisor.h: /usr/src/linux-3.0.13-0.11/arch/x86/include/asm/hypervisor.h /usr/src/packages/BUILD/xen-4.2.24547/non-dbg/obj/default/include/asm/hypervisor.h Signed-off-by: Olaf Hering <olaf@aepfle.de> Acked-by: Jan Beulich <jbeulich@suse.com> Committed-by: Jan Beulich <jbeulich@suse.com> xen-unstable changeset: 25067:05768bd498f2 xen-unstable date: Fri Mar 16 11:34:14 2012 +0100
* unmodified_drivers: update README fromIan Campbell2012-05-141-3/+12
| | | | | | | | | | | | | | | | http://wiki.xen.org/xenwiki/UnmodifiedDrivers Add reference to the fact that these drivers are for "classic-Xen" kernels only and do not work with PVops but point towards the PVHVM functionality in mainstream. Signed-off-by: Ian Campbell <ian.campbell@citrix.com> Acked-by: Ian Jackson <ian.jackson.citrix.com> Committed-by: Ian Jackson <ian.jackson.citrix.com> xen-unstable changeset: 24045:4ed766d70396 xen-unstable date: Wed Oct 26 17:44:03 2011 +0100
* Update Xen version to 4.1.3-rc2-preKeir Fraser2012-05-141-1/+1
|
* Added signature for changeset da64f68730cfKeir Fraser2012-05-071-0/+1
|
* Added tag 4.1.3-rc1 for changeset da64f68730cfKeir Fraser2012-05-071-0/+1
|
* Update Xen version to 4.1.3-rc14.1.3-rc1Keir Fraser2012-05-072-2/+2
|
* svm: Fake out the Bus Unit Config MSR on revF AMD CPUsGeorge Dunlap2012-05-012-0/+15
| | | | | | | | | | | | | | | | | | | | | | | Win2k8 x64 reads this MSR on revF chips, where it wasn't publically available; it uses a magic constant in %rdi as a password, which we don't have in rdmsr_safe(). Since we'll ignore the later writes, just use a plausible value here (the reset value from rev10h chips) if the real CPU didn't provide one. Signed-off-by: George Dunlap <george.dunlap@eu.citrix.com> Committed-by: Keir Fraser <keir@xen.org> xen-unstable changeset: 24990:322300fd2ebd xen-unstable date: Thu Mar 08 09:17:21 2012 +0000 svm: amend c/s 24990:322300fd2ebd (fake BU_CFG MSR on AMD revF) Let's restrict such a hack to the known affected family. Signed-off-by: Jan Beulich <jbeulich@suse.com> Acked-by: Keir Fraser <keir@xen.org> Acked-by: George Dunlap <george.dunlap@eu.citrix.com> xen-unstable changeset: 25058:f47d91cb0faa xen-unstable date: Thu Mar 15 15:09:18 2012 +0100
* x86-64: Fix memory hotplug epfn upper limit test for updating the compat M2P ↵Malcolm Crossley2012-05-011-1/+1
| | | | | | | | | | | | | | | table The epfn is being compared to (RDWR_COMPAT_MPT_VIRT_END - RDWR_COMPAT_MPT_VIRT_START) without a 2 bit shift, resulting in the epfn being compared to the size of the RDWR_COMPAT_MPT table in bytes instead of the maximum page frame number that the RDWR_COMPAT_MPT table can map. Signed-off-by: Malcolm Crossley <malcolm.crossley@citrix.com> Committed-by: Jan Beulich <jbeulich@suse.com> xen-unstable changeset: 25242:b7ce6a88bebb xen-unstable date: Wed Apr 25 12:35:56 2012 +0200
* QEMU_TAG updateIan Jackson2012-04-241-3/+3
|
generated by cgit v1.2.3 (git 2.25.1) at 2024-06-02 23:46:25 +0000