aboutsummaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* Update Xen version to 4.1.2-rc24.1.2-rc2Keir Fraser2011-09-071-1/+1
|
* bitmap_scnlistprintf() should always zero-terminate its output bufferJan Beulich2011-09-071-3/+4
| | | | | | | | | | | | ... as long as it has non-zero size. So far this would not happen if the passed in CPU mask was empty. Also fix the comment describing the return value to actually match reality. Signed-off-by: Jan Beulich <jbeulich@suse.com> xen-unstable changeset: 23820:ba75234a6f56 xen-unstable date: Wed Sep 07 10:36:55 2011 +0100
* xen: __hvm_pci_intx_assert should check for gsis remapped onto pirqsStefano Stabellini2011-08-311-2/+7
| | | | | | | | | | | | If the isa irq corresponding to a particular gsi is disabled while the gsi is enabled, __hvm_pci_intx_assert will always inject the gsi through the violapic, even if the gsi has been remapped onto a pirq. This patch makes sure that even in this case we inject the notification appropriately. Signed-off-by: Stefano Stabellini <stefano.stabellini@eu.citrix.com> xen-unstable changeset: 23807:2297b90a6a7b xen-unstable date: Wed Aug 31 15:23:34 2011 +0100
* xen: fix hvm_domain_use_pirq's behaviorStefano Stabellini2011-08-313-6/+8
| | | | | | | | | | | | | hvm_domain_use_pirq should return true when the guest is using a certain pirq, no matter if the corresponding event channel is currently enabled or disabled. As an additional complication, qemu is going to request pirqs for passthrough devices even for Xen unaware HVM guests, so we need to wait for an event channel to be connected before considering the pirq of a passthrough device as "in use". Signed-off-by: Stefano Stabellini <stefano.stabellini@eu.citrix.com> xen-unstable changeset: 23806:4226ea1785b5 xen-unstable date: Wed Aug 31 15:23:12 2011 +0100
* IRQ: manually EOI migrating line interruptsAndrew Cooper2011-08-317-18/+29
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When migrating IO-APIC line level interrupts between PCPUs, the migration code rewrites the IO-APIC entry to point to the new CPU/Vector before EOI'ing it. The EOI process says that EOI'ing the Local APIC will cause a broadcast with the vector number, which the IO-APIC must listen to to clear the IRR and Status bits. In the case of migrating, the IO-APIC has already been reprogrammed so the EOI broadcast with the old vector fails to match the new vector, leaving the IO-APIC with an outstanding vector, preventing any more use of that line interrupt. This causes a lockup especially when your root device is using PCI INTA (megaraid_sas driver *ehem*) However, the problem is mostly hidden because send_cleanup_vector() causes a cleanup of all moving vectors on the current PCPU in such a way which does not cause the problem, and if the problem has occured, the writes it makes to the IO-APIC clears the IRR and Status bits which unlocks the problem. This fix is distinctly a temporary hack, waiting on a cleanup of the irq code. It checks for the edge case where we have moved the irq, and manually EOI's the old vector with the IO-APIC which correctly clears the IRR and Status bits. Also, it protects the code which updates irq_cfg by disabling interrupts. Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com> xen-unstable changeset: 23805:7048810180de xen-unstable date: Wed Aug 31 15:19:24 2011 +0100
* vpmu: Add processors Westmere E7-8837 and SandyBridge i5-2500 to the vpmu listDietmar Hahn2011-08-312-1/+4
| | | | | | Signed-off-by: Dietmar Hahn <dietmar.hahn@ts.fujitsu.com> xen-unstable changeset: 23803:51983821efa4 xen-unstable date: Wed Aug 31 15:17:45 2011 +0100
* libxl: Do not SEGV when no 'removable' disk parameter in xenstoreMarek Marczykowski2011-06-051-1/+6
| | | | | | | | | | Just assume disk as not removable when no 'removable' paremeter Signed-off-by: Marek Marczykowski <marmarek@mimuw.edu.pl> xen-unstable changest: 23607:2f63562df1c4 Backport-requested-by: Marek Marczykowski <marmarek@mimuw.edu.pl> Committed-by: Ian Jackson <ian.jackson@eu.citrix.com>
* xen.lowlevel.xl: Return None on empty domain nameMarek Marczykowski2011-06-051-3/+5
| | | | | | | | | | | Previously PyString_FromString(NULL) was called, which caused assertion failure. Signed-off-by: Marek Marczykowski <marmarek@mimuw.edu.pl> xen-unstable changest: 23606:cc2f376d0cd9 Backport-requested-by: Marek Marczykowski <marmarek@mimuw.edu.pl> Committed-by: Ian Jackson <ian.jackson@eu.citrix.com>
* libxl: Allocate memory for strings in libxl_device_diskMarek Marczykowski2011-06-011-2/+2
| | | | | | | | | | | | | Memory for strings in libxl_device_disk must be allocated from outside of libxl__gc to not be freed at the end of function (by libxl__free_all). Fixes xl block-detach Signed-off-by: Marek Marczykowski <marmarek@mimuw.edu.pl> xen-unstable changest: 23603:6656d80b4de4 Backport-requested-by: Marek Marczykowski <marmarek@mimuw.edu.pl> Committed-by: Ian Jackson <ian.jackson@eu.citrix.com>
* libxl: Accept disk name in libxl_devid_to_device_diskMarek Marczykowski2011-06-053-6/+6
| | | | | | | | | | Accept disk name in xl block-detach. Signed-off-by: Marek Marczykowski <marmarek@mimuw.edu.pl> xen-unstable changest: 23604:5d7998be2252 Backport-requested-by: Marek Marczykowski <marmarek@mimuw.edu.pl> Committed-by: Ian Jackson <ian.jackson@eu.citrix.com>
* libxl: Remove frontend and backend devices from xenstore after destroyMarek Marczykowski2011-06-051-11/+5
| | | | | | | | | | | | Cleanup frontend and backend devices from xenstore for all dev types - not only disks. Because backend cleanup moved to libxl__device_destroy, libxl__devices_destroy is somehow simpler. Signed-off-by: Marek Marczykowski <marmarek@mimuw.edu.pl> xen-unstable changest: 23605:ff8d170852b3 Backport-requested-by: Marek Marczykowski <marmarek@mimuw.edu.pl> Committed-by: Ian Jackson <ian.jackson@eu.citrix.com>
* remus: handle exceptions while installing/unstalling net bufferSigned-off-by: Shriram Rajagopalan2011-08-302-10/+28
| | | | | | | | | | Signed-off-by: Shriram Rajagopalan <rshriram@cs.ubc.ca> Acked-by: Ian Jackson <ian.jackson@eu.citrix.com> Committed-by: Ian Jackson <ian.jackson@eu.citrix.com> xen-unstable changeset: 23600:15fc211a13bf Backport-requested-by: Shriram Rajagopalan <rshriram@gmail.com> Committed-by: Ian Jackson <ian.jackson@eu.citrix.com>
* tools: remus: blktap2/block-remus.c - potential write-after-write race fixShriram Rajagopalan2011-08-301-66/+125
| | | | | | | | | | | | | | | | | At the end of a checkpoint, when a new flush (of buffered disk writes) is merged with ongoing flush, we have to make sure that none of the new disk I/O requests overlap with ones in in progress. If it does, hold the request and dont issue I/O until the overlapping one finishes. If we allow the I/O to proceed, we might end up with two overlapping requests in the disk's queue and the disk may not offer any guarantee on which one is written first. Signed-off-by: Shriram Rajagopalan <rshriram@cs.ubc.ca> Committed-by: Ian Jackson <ian.jackson@eu.citrix.com> xen-unstable changeset: 23414:ecff559bf474 Backport-requested-by: Shriram Rajagopalan <rshriram@gmail.com> Committed-by: Ian Jackson <ian.jackson@eu.citrix.com>
* tools: remus: support DRBD disk backendsShriram Rajagopalan2011-08-301-13/+54
| | | | | | | | | | | | | | | | | | | | | | DRBD disk backends can be used instead of tapdisk backends for Remus. This requires a Remus style disk replication protocol (asynchronous replication with output buffering at backup), that is not available in standard DRBD code. A modified version that supports this new replication protocol is available from git://aramis.nss.cs.ubc.ca/drbd-8.3-remus Use of DRBD disk backends provides a means for efficient resynchronization of data after the crashed machine comes back online. Since DRBD allows for online resynchronization, a DRBD backed Remus VM does not have to be stopped or shutdown while the disks are resynchronizing. Once resynchronization is complete, Remus can be started at will. Signed-off-by: Shriram Rajagopalan <rshriram@cs.ubc.ca> Committed-by: Ian Jackson <ian.jackson@eu.citrix.com> xen-unstable changeset: 23413:62c0dfc9efbf Backport-requested-by: Shriram Rajagopalan <rshriram@gmail.com> Committed-by: Ian Jackson <ian.jackson@eu.citrix.com>
* remus: write circumlocution for try..except..finallyJinsong Liu2011-08-301-5/+6
| | | | | | | | | | | | | | | | | | | | | | | Parsing /otc/source/vtd/xen-unstable/tools/python/../../tools/libxl/libxl.idl File "/usr/lib64/python2.4/site-packages/xen/remus/save.py", line 169 finally: ^ SyntaxError: invalid syntax This was introduced in 23195:13ec53a59a42 It is a problem for Python 2.4 and earlier, only. So use try...(try...except)...finally as suggested by Ian Campbell. Signed-off-by: Liu, Jinsong <jinsong.liu@intel.com> Acked-by: Shriram Rajagopalan <rshriram@cs.ubc.ca> Acked-by: Ian Campbell <Ian.Campbell@eu.citrix.com> Acked-by: Ian Jackson <ian.jackson@eu.citrix.com> Committed-by: Ian Jackson <ian.jackson@eu.citrix.com> xen-unstable changeset: 23379:b04e57ec4671 Backport-requested-by: Shriram Rajagopalan <rshriram@gmail.com> Committed-by: Ian Jackson <ian.jackson@eu.citrix.com>
* remus: blackhole replication targetShriram Rajagopalan2011-08-302-7/+22
| | | | | | | | | | | | | | | | The new --null option allows one to test and play with just the memory checkpointing and network buffering aspect of remus, without the need for a second host. The disk is not replicated. All replication data is sent to /dev/null. This option is pretty handy when a user wants to see the page churn for his workload or observe the latency hit though the latter will not be accurate. Signed-off-by: Shriram Rajagopalan <rshriram@cs.ubc.ca> Committed-by: Ian Jackson <ian.jackson@eu.citrix.com> xen-unstable changeset: 23196:29d81623dc14 Backport-requested-by: Shriram Rajagopalan <rshriram@gmail.com> Committed-by: Ian Jackson <ian.jackson@eu.citrix.com>
* remus: fix check for installed qdiscs on ifbShriram Rajagopalan2011-08-301-2/+2
| | | | | | | | | | | | | | current check includes ingress and pfifo_fast. Add mq to the list of allowed qdiscs already installed on ifb. This patch fixes cases where remus fails to start, due to an mq qdisc already present on the vif. Signed-off-by: Shriram Rajagopalan <rshriram@cs.ubc.ca> Committed-by: Ian Jackson <ian.jackson@eu.citrix.com> xen-unstable changeset: 23109:c8ae80a11d47 Backport-requested: Shriram Rajagopalan <rshriram@gmail.com> Committed-by: Ian Jackson <ian.jackson@eu.citrix.com>
* MergeIan Jackson2011-08-304-11/+16
|\
| * x86/mm: Add iommu=sharept parameter for compatibility with 4.2Tim Deegan2011-08-261-0/+2
| | | | | | | | Signed-off-by: Tim Deegan <tim@xen.org>
| * Passthrough: fix iommu_use_hap_pt() to use hap_enabled()Tim Deegan2011-08-231-1/+1
| | | | | | | | | | | | | | | | | | In line with 22924:86000076dcee, paging_mode_hap(d) shouldn't be used in HAP internals that are called during HAP setup. Signed-off-by: Tim Deegan <tim@xen.org> xen-unstable changeset: 23789:1b77cf8305df xen-unstable date: Tue Aug 23 10:54:27 2011 +0100
| * IOMMU: only try to share IOMMU and HAP tables for domains with P2M.Tim Deegan2011-08-233-4/+7
| | | | | | | | | | | | | | | | This makes the check more precise, and brings VTd in line with AMD code. Signed-off-by: Tim Deegan <tim@xen.org> xen-unstable changeset: 23788:9d2a8912597d xen-unstable date: Tue Aug 23 10:43:25 2011 +0100
| * VT-d: Explicitly test EPT capabilities during IOMMU initTim Deegan2011-08-231-6/+6
| | | | | | | | | | | | | | | | because the cached version isn't set up until the EPT init happens. Signed-off-by: Tim Deegan <tim@xen.org> xen-unstable changeset: 23787:41f00cf6b822 xen-unstable date: Tue Aug 23 10:43:20 2011 +0100
| * Update Xen version to 4.1.2-rc2-preKeir Fraser2011-08-251-1/+1
| |
* | xl: print sxp on dry-run of create.Ian Campbell2011-08-301-5/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The help text for xm create's --dry-run says "Dry run - prints the resulting configuration in SXP but does not create the domain." so update xl implementation to match. At least the xendomains initscript relies on this (for better or worse). Signed-off-by: Ian Campbell <ian.campbell@citrix.com> Tested-by: Carsten Schiers <carsten@schiers.de> Acked-by: Ian Jackson <ian.jackson@eu.citrix.com> Committed-by: Ian Jackson <ian.jackson@eu.citrix.com> xen-unstable changeset: 23467:2ae357405850 Backport-requested: Carsten Schiers <carsten@schiers.de> Committed-by: Ian Jackson <ian.jackson@eu.citrix.com>
* | tools: Improved LSB headers in init.d scriptsFabio Fantoni2011-08-303-10/+10
| | | | | | | | | | | | | | | | | | | | | | xendomains service now working also without xend service Signed-off-by: Fabio Fantoni <fabio.fantoni@heliman.it> Committed-by: Ian Jackson <ian.jackson@eu.citrix.com> xen-unstable changeset: 23673:0648846b4d17 Backport-requested: Carsten Schiers <carsten@schiers.de> Committed-by: Ian Jackson <ian.jackson@eu.citrix.com>
* | /etc/init.d/xendomains relies on simple pattern matching from sructuresxl: improve compatibility with xm2011-08-301-5/+5
|/ | | | | | | | | | | | | being printed by "xl list -l" command. so update xl implementation to match. Signed-off-by: Carsten Schiers <carsten@schiers.de> Acked-by: Ian Jackson <ian.jackson@eu.citrix.com> Committed-by: Ian Jackson <ian.jackson@eu.citrix.com> xen-unstable changeset: 23567:c2995f0555af Backported-by: Carsten Schiers <carsten@schiers.de> Committed-by: Ian Jackson <ian.jackson@eu.citrix.com>
* Added signature for changeset 1f21da33dea4Keir Fraser2011-08-251-0/+1
|
* Added tag 4.1.2-rc1 for changeset 1f21da33dea4Keir Fraser2011-08-251-0/+1
|
* 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
generated by cgit v1.2.3 (git 2.25.1) at 2024-06-02 18:42:25 +0000