aboutsummaryrefslogtreecommitdiffstats
path: root/tools
Commit message (Collapse)AuthorAgeFilesLines
* x86/emulator: workaround for AMD erratum 573Jan Beulich2012-03-071-0/+2
| | | | | | | | | | | | | | | | | | | The only cases where we might end up emulating fsincos (as any other x87 operations without memory operands) are - when a HVM guest is in real mode (not applicable on AMD) - between two half page table updates in PAE mode (unlikely, and not doing the emulation here does affect only performance, not correctness) - when a guest maliciously (or erroneously) modifies an (MMIO or page table update) instruction under emulation (unspecified behavior) Hence, in order to avoid the erratum to cause harm to the entire host, don't emulate fsincos on the affected AMD CPU families. Signed-off-by: Jan Beulich <jbeulich@suse.com> Acked-by: Keir Fraser <keir@xen.org> xen-unstable changeset: 24417:1452fb248cd5 xen-unstable date: Fri Dec 16 15:45:40 2011 +0100
* tools/libxc: Fix x86_32 build breakage in previous changeset.Keir Fraser2011-12-062-15/+18
| | | | | | | | | | | | | | | | | | | Signed-off-by: Keir Fraser <keir@xen.org> xen-unstable changeset: 24345:491c3ebf1d37 xen-unstable date: Fri Dec 02 08:40:02 2011 -0800 tools/x86_64: Fix cpuid() inline asm to not clobber stack's red zone Pushing stuff onto the stack on x86-64 when we do not specify -mno-red-zone is unsafe. Since the complicated asm is due to register pressure on i386, we simply implement an all-new simpler alternative for x86-64. Signed-off-by: Keir Fraser <keir@xen.org> Acked-by: Jan Beulich <jbeulich@novell.com> xen-unstable changeset: 24344:72f4e4cb7440 xen-unstable date: Fri Dec 02 06:31:14 2011 -0800
* hvmloader: Switch to absolute addressing for calling hypercall stubs.Keir Fraser2011-07-204-266/+268
| | | | | | | | | | | | | | | | | | 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
* tools/hotplug/Linux: start all xen daemons in runlevel 2Fabio Fantoni2011-07-183-6/+6
| | | | | | | | Backported from xen-4.1-testing.hg 23086:9b5fbd8ff152 -iwj. Signed-off-by: Fabio Fantoni <fabio.fantoni@heliman.it> Signed-off-by: Ian Jackson <ian.jackson@eu.citrix.com> Committed-by: Ian Jackson <ian.jackson@eu.citrix.com>
* xen/libxc: set CPUID topology leaf as unsupported for PV guestsDavid Vrabel2011-07-161-0/+1
| | | | | | | | | | | | | | | | | 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
* 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
* x86: Hide CPUID leaf 7 from PV guests.Keir Fraser2011-06-031-0/+1
| | | | | | Signed-off-by: Keir Fraser <keir@xen.org> xen-unstable changeset: 23461:5839e797a130 xen-unstable date: Thu Jun 02 14:39:50 2011 +0100
* libxc: obtain correct length of p2m during core dumpingMarkus Gross2011-05-281-2/+1
| | | | | | | | | | | | | | | | | | | | | | | | | while implementing core dumping functionality for the libxl driver of libvirt, I discovered an issue with mapping pages of a pv guest. After dumping the core of a pv guest the domain was not cleared up properly and some pages were not unmapped. This issue is similar to the one reported here: http://lists.xensource.com/archives/html/xen-devel/2011-05/msg01314.html In xc_domain_dumpcore_via_callback in the file xc_core.c the function xc_core_arch_map_p2m is called to map P2M_FL_ENTRIES pages to the variable p2m. But to unmap the pages later, the dinfo->p2m_size has to be set accordingly. This was not done, instead a variable named p2m_size was set. This way P2M_FL_ENTRIES was always zero and the pages were left mapped. Signed-off-by: Ian Jackson <ian.jackson@eu.citrix.com> Acked-by: Ian Jackson <ian.jackson@eu.citrix.com> Committed-by: Ian Jackson <ian.jackson@eu.citrix.com> xen-unstable changeset: 23374:8bd7b5e98f2a xen-unstable date: Tue May 24 15:00:16 2011 +0100
* libxc: after saving, unmap correct amount for live_m2pJim Fehlig2011-05-281-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | With some help from Olaf, I've finally got to the bottom of an issue I came across while trying to implement save/restore in the libvirt libxenlight driver. After issuing the save operation, the saved domain was not being cleaned up properly and left in this state from xl's perspective xen33:# xl list Name ID Mem VCPUs State Time(s) Domain-0 0 6821 8 r----- 122.5 (null) 2 2 2 --pssd 10.8 Checking the libvirtd /proc/$pid/maps I found this 7f3798984000-7f3798b86000 r--s 00002000 00:03 4026532097 /proc/xen/privcmd So not all all pages belonging to the domain were unmapped from libvirtd. In tools/libxc/xc_domain_save.c we found that P2M_FL_ENTRIES were being mapped but only P2M_FLL_ENTRIES were being unmapped. The attached patch changes the unmapping to use the same P2M_FL_ENTRIES macro. I'm not too familiar with this code though so posting here for review. I suspect this was not noticed before since most (all?) processes doing save terminate after the save and are not long-running like libvirtd. Ian Campbell writes: > Looks like I introduced this in 18558:ccf0205255e1, sorry! > > I guess it is also wrong in the error path out of map_and_save_p2m_table > and so we also need [another hunk]. This change should be backported to relevant earlier trees. -iwj From: Jim Fehlig <jfehlig@novell.com> From: Ian Campbell <Ian.Campbell@citrix.com> Signed-off-by: Ian Jackson <ian.jackson@eu.citrix.com> Cc: Olaf Hering <olaf@aepfle.de> Acked-by: Ian Campbell <Ian.Campbell@citrix.com> Acked-by: Ian Jackson <ian.jackson@eu.citrix.com> Committed-by: Ian Jackson <ian.jackson@eu.citrix.com> xen-unstable changeset: 23373:171007b4e2c4 xen-unstable date: Tue May 24 14:50:00 2011 +0100
* x86: clear CPUID output of leaf 0xd for Dom0 when xsave is disabledKeir Fraser2011-05-201-0/+1
| | | | | | | | | | | | | | | | | Linux starting with 2.6.36 uses the XSAVEOPT instruction and has certain code paths that look only at the feature bit reported through CPUID leaf 0xd sub-leaf 1 (i.e. without qualifying the check with one evaluating leaf 4 output). Consequently the hypervisor ought to mimic actual hardware in clearing leaf 0xd output when not supporting xsave. Signed-off-by: Jan Beulich <jbeulich@novell.com> xen-unstable changeset: 23353:a768a10d32b4 xen-unstable date: Fri May 20 08:54:45 2011 +0100 Make this unconditional for 4.0 (no pv xsave support) and fix for domU guests as well (this was already okay in 4.1 and later). Signed-off-by: Keir Fraser <keir@xen.org>
* tools/xm-test: portability fix: Avoid using == in /bin/sh scriptChristoph Egger2011-05-121-1/+1
| | | | | | | From: David Brownlee <abs@netbsd.org> Signed-off-by: Christoph Egger <Christoph.Egger@amd.com> xen-unstable changeset: 23328:6767d92dff13 xen-unstable date: Thu May 12 08:55:12 2011 +0100
* libxc: [CVE-2011-1583] pv kernel image validationIan Jackson2011-05-091-42/+93
| | | | | | | | | | | | | | | | | | | | | | The functions which interpret the kernel image supplied for a paravirtualised guest, and decompress it into memory when booting the domain, are incautious. Specifically: (i) Integer overflow in the decompression loop memory allocator might result in overrunning the buffer used for the decompressed image; (ii) Integer overflows and lack of checking of certain length fields can result in the loader reading its own address space beyond the size of the supplied kernel image file. (iii) Lack of error checking in the decompression loop can lead to an infinite loop. This patch fixes these problems. CVE-2011-1583. Signed-off-by: Ian Campbell <Ian.Campbell@eu.citrix.com> Signed-off-by: Ian Jackson <ian.jackson@eu.citrix.com> Committed-by: Ian Jackson <ian.jackson@eu.citrix.com>
* tools/blktap, blktap2: include <sys/mount.h> instead of <linux/fs.h>Ian Campbell2011-03-262-3/+3
| | | | | | | | | | | | | | The former is a userspace sanitised header which contains the definitions we need. In some distros linux/fs.h defines WRITE which conflicts with blktaps own use of that name. Also there is no reason to use <linux/errno.h> over the more normal <errno.h>. Signed-off-by: Ian Campbell <ian.campbell@citrix.com> Committed-by: Ian Jackson <ian.jackson@eu.citrix.com> xen-unstable changeset: 22765:0dbad563a659 xen-unstable date: Mon Jan 17 17:14:20 2011 +0000
* init.d: Fix xencommons init script chkconfig configurationKeir Fraser2011-03-251-1/+1
| | | | | | | | | | | | | | | | Fix the xencommons init script chkconfig configuration since the priority was missing here and chkconfig was complaining about invalid chkconfig script so I added both start and stop priorities to the chkconfig line and it was working fine, the script was successfully added to chkconfig when using `chkconfig --add xencommons` and management using the chkconfig utility was now possible. Tested on RHEL-5 Server with Xen-4.1-unstable installed, running on PVops kernel 2.6.32.15 and it was working fine. Signed-off-by: Michal Novotny <minovotn@redhat.com> xen-unstable changeset: 21657:e2f5e4f3481c xen-unstable date: Tue Jun 22 16:22:30 2010 +0100
* libxc: fix incorrect scanning of pfn array in pagebuf during migrationShriram Rajagopalan2011-03-141-4/+4
| | | | | | | | | | | | | | | | | | | | | | xc_domain_restore.c:apply_batch function makes two passes over the pfn_types array in pagebuf to allocate the needed MFNs. The curbatch parameter to this function specifies the array offset in pfn_types, from where the current scan should begin. But this variable is not taken into account (index always starts at 0) during the two passes. While this [bug] does not manifest itsef during save/restore or live migration, under Remus, xc_domain_restore fails due to corrupt guest page tables. (This appears to have been broken by 21588:6c3d8aec202d which reverted two changesets from before Remus support was added and hence reintroduced some none-Remus compatible bits.) Signed-off-by: Shriram Rajagopalan <rshriram@cs.ubc.ca> Acked-by: Ian Campbell <ian.campbell@citrix.com> Acked-by: Ian Jackson <ian.jackson@eu.citrix.com> Committed-by: Ian Jackson <ian.jackson@eu.citrix.com> xen-unstable changeset: 22967:5bc39222773d xen-unstable date: Thu Mar 03 16:55:27 2011 +0000
* tools: provide startup script for libxlIan Jackson2011-03-102-0/+83
| | | | | | | | | | | | | | | | | | | | | | | In Xen 4.0 there is no /etc/init.d/xencommons. This means that in most situations you don't get xenstored, and xl doesn't work, unless you do something shonky like starting and then immediately stopping xend. To test xl, my automatic testing system therefore provides its own init script to start xenstored and xenconsoled. This script was created by borrowing from /etc/init.d/xend and other init scripts in various versions of xen.hg. Here it is[1], as a new "xencommons" script. The user will still have to add appropriate rc links, and only a script for Linux is provided. We do not want to backport the refactoring of /etc/init.d/xend, so xend users should not enable this script. [1] Copied from osstest.git#78c59993ab536b8c39c5a00a xenlightdaemons. Signed-off-by: Ian Jackson <ian.jackson@eu.citrix.com> Acked-by: Ian Campbell <Ian.Campbell@eu.citrix.com>
* x86, libxc: Fix xc_translate_foreign_address() for PV guests ofKeir Fraser2011-03-082-3/+5
| | | | | | | | | different bitness than dom0 (32-bit vs 64-bit). Original patch by: Paolo Bonzini <pbonzini@redhat.com> Signed-off-by: Keir Fraser <keir@xen.org> xen-unstable changeset: 22966:de49500f344a xen-unstable date: Thu Mar 03 17:46:44 2011 +0000
* [IA64] fix missing header: asm/fpswa.hKUWAMURA Shin'ya2011-02-181-0/+1
| | | | | | | | | | This patch fixes the following error in recent kernel: ia64/asm/dom_fw_common.h:47:23: error: asm/fpswa.h: No such file or directory Signed-off-by: KUWAMURA Shin'ya <kuwa@jp.fujitsu.com> xen-unstable changeset: 22941:d12a28ef91b9 xen-unstable date: Fri Feb 18 10:21:19 2011 +0000
* x86: blacklist new AMD CPUID bits for PV domainsKeir Fraser2011-01-262-0/+10
| | | | | | | | | | | | | | 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
* Update my email address to long-term stable address.Keir Fraser2011-01-074-4/+4
| | | | | | Signed-off-by: Keir Fraser <keir@xen.org> xen-unstable changeset: 22675:0ab058a55c24 xen-unstable date: Fri Jan 07 13:30:04 2011 +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-171-0/+8
| | | | | | | | | | | | | | | 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
* tmem: Use of 'new' clashes with C++ reserved namespace.Keir Fraser2010-12-101-8/+8
| | | | | | | | 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
* hvmloader: fix off-by-one-bit error when initialising PCI devicesKeir Fraser2010-11-101-7/+5
| | | | | | | | | | | | | | | | | | | | | | | hvmloader is responsible for - amoungst other things - initialising the PCI device BARs prior to loading the guest BIOS. The previous code only probed for devfn up to 128. The lower 3 bits are function IDs so this meant that only devices in slots 0-15 were actually being initialized. Signed-off-by: Alex Zeffertt <alex.zeffertt@eu.citrix.com> Acked-by: Gianni Tedesco <gianni.tedesco@citrix.com> xen-unstable changeset: 22383:cba667fb80cf xen-unstable date: Wed Nov 10 13:58:16 2010 +0000 hvmloader: Fix 22383:cba667fb80cf iterating over defns 0..255 We need to declare devfn as wider than 8 bits for a loop 0<devfn<256 to terminate. Signed-off-by: Keir Fraser <keir@xen.org> xen-unstable changeset: 22384:c19e3371f31b xen-unstable date: Wed Nov 10 14:15:23 2010 +0000
* tools: gdbsx: Check return of write()Keir Fraser2010-11-081-2/+8
| | | | | | | | | | Not checking leads to warn_unused_result checks triggering in some libraries and compilers. Combined with -Werror this breaks the build. Signed-off-by: Gianni Tedesco <gianni.tedesco@citrix.com> Signed-off-by: Ian Jackson <ian.jackson@eu.citrix.com> xen-unstable changeset: 22349:3f98881703aa xen-unstable date: Wed Nov 03 11:58:25 2010 +0000
* Fix "Error: Device 51952 not connected" error when using pygrubKeir Fraser2010-11-081-3/+6
| | | | | | | | | | | | | | | | | | | | | | | | The following is the process of booting a DomU with 'mounted-blktap2' (VHD for example) and 'pygrub' as bootloader: 1. Connect boot-device to Dom0 as '/dev/xpvd' 2. Pygrub get info for load DomU 3. Disconnect boot-device from Dom0 4. Boot DomU During step 3 the created device is disconnected from Dom0, but xenstore does not scrape away after the device is disconnected so you get the following error:     "Error: Device /dev/xvdp (51952, tap2) is already connected." During step 3 xend calls destroyDevice always with 'tap' as argument. Signed-off-by: eXeC001er <execooler@gmail.com> Signed-off-by: Stefano Stabellini <stefano.stabellini@eu.citrix.com> xen-unstable changeset: 21999:cd5b4135fe03 xen-unstable date: Mon Aug 16 17:11:30 2010 +0100
* tools/xenpaging: Add _XOPEN_SOURCE to fix build problems with recent gccKeir Fraser2010-11-081-0/+1
| | | | | | | | | | This patch fixes compilation issues with gcc version 4.1.2 20061115 (prerelease) (Debian 4.1.1-21). Signed-off-by: Daniel Kiper <dkiper@net-space.pl> Signed-off-by: Ian Jackson <ian.jackson@eu.citrix.com> xen-unstable changeset: 22023:af6799abc6e9 xen-unstable date: Wed Aug 18 16:48:25 2010 +0100
* pygrub: support grub2 "(hdX,msdosY)" partition syntaxKeir Fraser2010-10-291-0/+2
| | | | | | | | | | This appeared in Debian Squeeze at some point. Signed-off-by: Ian Campbell <ian.campbell@citrix.com> Signed-off-by: Stefano Stabellini <stefano.stabellini@eu.citrix.com> committer: Stefano Stabellini <stefano.stabellini@eu.citrix.com> xen-unstable changeset: 22238:6eaab8297681 xen-unstable date: Wed Oct 13 11:45:26 2010 +0100
* Fix fd leak in xenstoreKeir Fraser2010-09-151-0/+2
| | | | | | | | Missing from commit 'libxl: Backported stuff from unstable' Without this change, xs_daemon_open/xs_daemon_close will leak file descriptors. Signed-off-by: Olaf Hering <olaf@aepfle.de>
* tmem (tools): move to new ABI version to handle long object-idsKeir Fraser2010-09-132-11/+70
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | After a great deal of discussion and review with linux kernel developers, it appears there are "next-generation" filesystems (such as btrfs, xfs, Lustre) that will not be able to use tmem due to an ABI limitation... a field that represents a unique file identifier is 64-bits in the tmem ABI and may need to be as large as 192-bits. So to support these guest filesystems, the tmem ABI must be revised, from "v0" to "v1". I *think* it is still the case that tmem is experimental and is not used anywhere yet in production. The tmem ABI is designed to support multiple revisions, so the Xen tmem implementation could be updated to handle both v0 and v1. However this is a bit messy and would require data structures for both v0 and v1 to appear in public Xen header files. I am inclined to update the Xen tmem implementation to only support v1 and gracefully fail v0. This would result in only a performance loss (as if tmem were disabled) for newly launched tmem-v0-enabled guests, but live-migration between old tmem-v0 Xen and new tmem-v1 Xen machines would fail, and saved tmem-v0 guests will not be able to be restored on a tmem-v1 Xen machine. I would plan to update both pre-4.0.2 and unstable (future 4.1) to only support v1. I believe these restrictions are reasonable at this point in the tmem lifecycle, though they may not be reasonable in the near future; should the tmem ABI need to be revised from v1 to v2, I understand backwards compatibility will be required. Signed-off-by: Dan Magenheimer <dan.magenheimer@oracle.com> xen-unstable changeset: 22137:fd2e5008c2e0 xen-unstable date: Mon Sep 13 17:11:04 2010 +0100
* tools/debugger/gdbsx: use MTF flag for HVM guests for single stepKeir Fraser2010-09-131-0/+14
| | | | | | | | | | | | The attached patch first tries the MTF flag for HVM guest single step, reverting to manually setting the TF flag if MTF fails. Tested on 4.0.1. Compile tested on unstable. Signed-off-by: mukesh.rathor@oracle.com Signed-off-by: Ian Jackson <ian.jackson@eu.citrix.com> xen-unstable changeset: 22115:cd87550cea5e xen-unstable date: Tue Sep 07 19:17:16 2010 +0100
* blktap2: make protocol specific usage of shared sring explicitKeir Fraser2010-08-151-1/+1
| | | | | | | | | | | | | | | | | I don't think protocol specific data really belongs in this header but since it is already there and we seem to be stuck with it let's at least make the users explicit lest people get caught out by future new fields moving the pad field around. This is the Xen portion of this change. The kernel portion will be sent separately. There is no dependency between the two. Signed-off-by: Ian Campbell <ian.campbell@citrix.com> Cc: Jeremy Fitzhardinge <jeremy@goop.org> Cc: Daniel Stodden <daniel.stodden@citrix.com> Cc: Dongxiao Xu <dongxiao.xu@intel.com> xen-unstable changeset: feee0abed6aa xen-unstable date: Fri Jul 02 18:58:02 2010 +0100
* [Xen-devel] [PATCH] PoD: Fix domain build populate-on-demand cacheKeir Fraser2010-08-131-9/+4
| | | | | | | | | | | allocation Rather than trying to count the number of PoD entries we're putting in, we simply pass the target # of pages - the vga hole, and let the hypervisor do the calculation. Signed-off-by: George Dunlap <george.dunlap@eu.citrix.com> Signed-off-by: Stefano Stabellini <stefano.stabellini@eu.citrix.com> xen-unstable changeset: 6f059a340cdf xen-unstable date: Wed Aug 11 15:56:21 2010 +0100
* xl: Fix xl vcpu-list output on machines with more than 16 coresKeir Fraser2010-08-131-1/+1
| | | | | | | Signed-off-by: Andre Przywara <andre.przywara@amd.com> Signed-off-by: Stefano Stabellini <stefano.stabellini@eu.citrix.com> xen-unstable changeset: cb71d0d30f0c xen-unstable date: Tue Aug 10 15:35:13 2010 +0100
* xc: fix segfault in pv domain create if kernel is an invalid imageKeir Fraser2010-08-131-0/+1
| | | | | | | | | | | | If libelf calls elf_err() or elf_msg() before elf_set_log() has been called then it could potentially read an uninitialised log handling callback function pointer from struct elf_binary. Fix this in libxc by zeroing the structure before calling elf_init(). Signed-off-by: Gianni Tedesco <gianni.tedesco@citrix.com> Signed-off-by: Stefano Stabellini <stefano.stabellini@eu.citrix.com> xen-unstable changeset: 1d67dd785ef4 xen-unstable date: Mon Aug 09 17:43:18 2010 +0100
* gdbsx: Install into correct directory $(SBINDIR)Keir Fraser2010-08-021-4/+2
| | | | | | Signed-off-by: Christoph Egger <Christoph.Egger@amd.com> xen-unstable changeset: 21903:668f71224241 xen-unstable date: Mon Aug 02 16:58:50 2010 +0100
* libxl: fix fstat implicit declaration build errorKeir Fraser2010-08-021-0/+1
| | | | | | | Signed-off-by: Zhigang Wang <zhigang.x.wang@oracle.com> Committed-by: Ian Jackson <ian.jackson@eu.citrix.com> xen-unstable changeset: 21895:de62cfdd7b9f xen-unstable date: Fri Jul 30 14:28:39 2010 +0100
* tools/libxl: usbdevice should imply usbKeir Fraser2010-08-021-1/+1
| | | | | | | Signed-off-by: Stefano Stabellini <stefano.stabellini@eu.citrix.com> Committed-by: Ian Jackson <ian.jackson@eu.citrix.com> xen-unstable changeset: 21844:ef495616b946 xen-unstable date: Fri Jul 23 16:58:35 2010 +0100
* Without this we leak an fd on each domain shutdown and eventually runKeir Fraser2010-08-021-0/+5
| | | | | | | | | | | out of file descriptors meaning new the console of new domains are not logged. Seems to have been accidentally removed in 16638:28921e83000b. Signed-off-by: Ian Campbell <ian.campbell@citrix.com> xen-unstable changeset: 21818:9ccd024065c5 xen-unstable date: Mon Jul 19 12:21:24 2010 +0100
* Before this patch only log messages with precisely priorityKeir Fraser2010-08-021-2/+4
| | | | | | | | | | | | | | | | LOG_WARNING (or precisely LOG_DEBUG if -v) would be logged. xenconsoled only actually logs using LOG_ERR and LOG_DEBUG so for the most part we would have been logging absolutely nothing up until now. Linux provides a LOG_UPTO macro but I'm not sure how portable that is so I have opencoded the list of levels. Do I get some sort of prize for fixing a bug introduced in 2005? Signed-off-by: Ian Campbell <ian.campbell@citrix.com> xen-unstable changeset: 21814:91ce0b0953ca xen-unstable date: Fri Jul 16 12:10:56 2010 +0100
* xenconsole: do not exit if a pty device is missingKeir Fraser2010-08-021-0/+2
| | | | | | | | | This can just mean we have raced with the bootloader exiting and if we continue we will likely see the real domain console show up. Signed-off-by: Ian Campbell <ian.campbell@citrix.com> xen-unstable changeset: 21797:c18f43ed379e xen-unstable date: Wed Jul 14 16:36:47 2010 +0100
* gdbsx: Always build -- remove build-time config option.Keir Fraser2010-08-021-0/+12
| | | | | | | | | | | | | | | | | | | | | | Signed-off-by: Keir Fraser <keir.fraser@citrix.com> xen-unstable changeset: 21702:2846fd19945c xen-unstable date: Fri Jul 02 18:52:12 2010 +0100 tools/debugger/gdbsx: build enabled by default Submitted-by: Bruce Edge <bruce.edge@gmail.com> Signed-off-by: Ian Jackson <ian.jackson@eu.citrix.com> xen-unstable changeset: 21752:29e545151078 xen-unstable date: Thu Jul 08 16:50:34 2010 +0100 tools/debugger/gdbsx: enabled by only x86 The changeset 21752:29e545151078 breaks ia64, since gdbsx supports only x86. Signed-off-by: KUWAMURA Shin'ya <kuwa@jp.fujitsu.com> xen-unstable changeset: 21788:8429a8a23241 xen-unstable date: Tue Jul 13 19:08:48 2010 +0100
* x86: Add -fno-exceptions to list of possibly-supported CFLAGS for embedded ↵Keir Fraser2010-07-252-8/+2
| | | | | | | | targets. Signed-off-by: Keir Fraser <keir.fraser@citrix.com> xen-unstable changeset: 21860:2b768d52bc7f xen-unstable date: Sun Jul 25 22:20:47 2010 +0100
* xm: Do not check path of kernel if bootloader is specifiedKeir Fraser2010-07-161-2/+10
| | | | | | | | | | | When create DomU, if bootloader is specified, 'kernel/ramdisk' will be used by bootloader when boots DomU. So it is needless to check the path is existent or not. Signed-off-by: Yu Zhiguo <yuzg@cn.fujitsu.com> Acked-by: Ian Campbell <ian.campbell@citrix.com> xen-unstable changeset: 21807:6fdb00dc93a5 xen-unstable date: Thu Jul 15 16:32:50 2010 +0100
* gdbsx: update README and remove space in q packetKeir Fraser2010-07-162-6/+6
| | | | | | | | | | Newer version of gdb, version 7*, seems to have bug where it is not parsing thread list from gdbsx properly. Getting rid of the space in thread list works around it. It's ok with older gdb also. Signed-off-by: Mukesh Rathor <mukesh.rathor@oracle.com> xen-unstable changeset: 21806:bb3b28cb7208 xen-unstable date: Thu Jul 15 16:30:24 2010 +0100
* xl: start numbering vifs from 0Keir Fraser2010-07-161-1/+1
| | | | | | Signed-off-by: Stefano Stabellini <stefano.stabellini@eu.citrix.com> xen-unstable changeset: 21805:2047364f0bdf xen-unstable date: Wed Jul 14 16:46:49 2010 +0100
* xl: default timer_mode to 1Keir Fraser2010-07-161-1/+1
| | | | | | Signed-off-by: Stefano Stabellini <stefano.stabellini@eu.citrix.com> xen-unstable changeset: 21794:843978ef0dee xen-unstable date: Wed Jul 14 16:31:59 2010 +0100
generated by cgit v1.2.3 (git 2.25.1) at 2024-06-29 12:08:31 +0000