| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
| |
Signed-off-by: Keir Fraser <keir.fraser@citrix.com>
xen-unstable changeset: 21446:93410e5e4ad8
xen-unstable date: Sat May 22 06:36:41 2010 +0100
|
|
|
|
|
|
|
|
|
|
|
| |
On my system, I'm getting SIGSEGVs in xentop because
xenstat_node_domain() is returning NULL. Skip the loop if it does
rather than crashing.
Signed-off-by: Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com>
Signed-off-by: Keir Fraser <keir.fraser@citrix.com>
xen-unstable changeset: 21439:11a3bf0e568e
xen-unstable date: Thu May 20 14:10:07 2010 +0100
|
|
|
|
|
|
|
|
|
|
| |
init_vmcs_config()
The function shoudl only have single-domain effect.
Signed-off-by: Keir Fraser <keir.fraser@citrix.com>
xen-unstable changeset: 21435:c414129c8e12
xen-unstable date: Wed May 19 20:46:05 2010 +0100
|
|
|
|
|
|
| |
Signed-off-by: Keir Fraser <keir.fraser@citrix.com>
xen-unstable changeset: 21432:f71b641aa327
xen-unstable date: Wed May 19 18:38:19 2010 +0100
|
|
|
|
|
|
|
|
|
|
|
|
| |
PV superpages currently do not work with live migration. They fall
over dead when the shadow page table is enabled for dirty tracking.
The HVM support for superpages in this code has been tested and found
to work just fine for PV superpages. This patch modifies the test
macro to allow the code to work with PV superpages.
Signed-off-by: Keir Fraser <keir.fraser@citrix.com>
xen-unstable changeset: 21409:2c0c08b4770f
xen-unstable date: Tue May 18 11:24:04 2010 +0100
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This patches implements the workaround of AMD erratum 383 on family
10h CPUs. It destroys the guest VM when a MC error with a special
pattern is detected. Without this patch, a guest VM failure can
potentially crash Xen hypervisor and the whole system. The erratum
will be published in next version of guide.
Signed-off-by: Wei Huang <wei.huang2@amd.com>
Signed-off-by: Joerg Roedel <joerg.roedel@amd.com>
Signed-off-by: Christoph Egger <christoph.egger@amd.com>
xen-unstable changeset: 21408:f40acba36be8
xen-unstable date: Tue May 18 11:21:25 2010 +0100
|
|
|
|
|
|
|
|
|
|
|
|
| |
This patch is to fix S3 resume failure with Intel TXT/tboot launched,
brought by c/s 21108. Don't printk anything between two
tboot_gen_xenheap_integrity() calls for release build or debug build.
Or else xen heap will be changed, which causes that memory integrity
will be lost on S3 resume.
Signed-off-by: Shane Wang <shane.wang@intel.com>
xen-unstable changeset: 21403:102dca3f485b
xen-unstable date: Mon May 17 11:05:21 2010 +0100
|
|
|
|
|
|
| |
Signed-off-by: Keir Fraser <keir.fraser@citrix.com>
xen-unstable changeset: 21402:8d274f678da6
xen-unstable date: Mon May 17 10:56:36 2010 +0100
|
|
|
|
|
|
| |
Signed-off-by: Keir Fraser <keir.fraser@citrix.com>
xen-unstable changeset: 21394:4dc64aa43692
xen-unstable date: Sat May 15 08:31:42 2010 +0100
|
|
|
|
|
|
| |
Signed-off-by: Mark Langsdorf <mark.langsdorf@amd.com>
xen-unstable changeset: 21393:3dfc577c8b9e
xen-unstable date: Sat May 15 08:29:59 2010 +0100
|
|
|
|
|
|
| |
Signed-off-by: Christoph Egger <Christoph.Egger@amd.com>
xen-unstable changeset: 21392:4b4c01defbdd
xen-unstable date: Sat May 15 08:29:21 2010 +0100
|
|
|
|
|
|
| |
Signed-off-by: Keir Fraser <keir.fraser@citrix.com>
xen-unstable changeset: 21374:9d53864d7be6
xen-unstable date: Thu May 13 12:21:16 2010 +0100
|
|
|
|
|
|
|
|
|
|
| |
Ensure the rangesets are always initialised. Certain (privileged)
invocations of hypercalls such as mmu_update can end up interrogating
these special domains for possible I/O capabilities.
Signed-off-by: Keir Fraser <keir.fraser@citrix.com>
xen-unstable changeset: 21373:1ec412805622
xen-unstable date: Thu May 13 10:09:02 2010 +0100
|
|
|
|
|
|
| |
Signed-off-by: Keir Fraser <keir.fraser@citrix.com>
xen-unstable changeset: 21372:6c22d2dfed48
xen-unstable date: Thu May 13 09:44:20 2010 +0100
|
|
|
|
|
|
|
|
| |
initialisation.
Signed-off-by: Keir Fraser <keir.fraser@citrix.com>
xen-unstable changeset: 21360:fa94385978e6
xen-unstable date: Wed May 12 09:09:40 2010 +0100
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Doing a pthread_cancel and join on the reader thread while holding all
the request/reply/watch mutexes can deadlock if the thread needs to
take any of those mutexes to exit. Kill off the reader thread before
taking any mutexes (which should be redundant if we're
single-threaded at that point).
Signed-off-by: Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com>
xen-unstable changeset: 21354:9de69d816b11
xen-unstable date: Wed May 12 08:49:13 2010 +0100
xs: make sure mutexes are cleaned up and memory freed if the read
thread is cancelled
If the read thread is terminated with pthread cancel, it must make
sure all memory is freed and mutexes are unlocked.
Signed-off-by: Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com>
xen-unstable changeset: 21353:2dd3141b3e3e
xen-unstable date: Wed May 12 08:48:14 2010 +0100
|
|
|
|
|
|
| |
Signed-off-by: Keir Fraser <keir.fraser@citrix.com>
xen-unstable changeset: 21350:e50afc6ecc48
xen-unstable date: Wed May 12 08:42:30 2010 +0100
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
direct use of gcc's built-in versions.
This dramatically simplifies our code while also avoiding compile
warnings with certain intermediate versions of gcc.
This patch is based on an initial version by Jan Beulich.
Signed-off-by: Keir Fraser <keir.fraser@citrix.com>
xen-unstable changeset: 21349:d77a88f938c6
xen-unstable date: Tue May 11 14:05:28 2010 +0100
|
|
|
|
|
|
|
|
|
|
|
|
| |
initializing on systems with huge amounts of memory
Process pending soft-IRQs every 4G worth of pages initialized for Dom0
to keep timekeeping happy and prevent the NMI watchdog (when enabled)
from kicking in.
Signed-off-by: Jan Beulich <jbeulich@novell.com>
xen-unstable changeset: 21340:220fa418eaae
xen-unstable date: Tue May 11 08:35:45 2010 +0100
|
|
|
|
|
|
|
| |
From: Jim Fehlig <jfehlig@novell.com>
Signed-off-by: Keir Fraser <Keir.Fraser@eu.citrix.com>
xen-unstable changeset: 21338:a915a11908e3
xen-unstable date: Tue May 11 08:31:16 2010 +0100
|
|
|
|
|
|
|
|
|
|
| |
t_info size should be in bytes, not pages. This fixes a bug
that crashes the hypervisor if the total number of all pages
is more than 1024 but less than 2048.
Signed-off-by: George Dunlap <george.dunlap@citrix.com>
xen-unstable changeset: 21333:93c5beba9d04
xen-unstable date: Mon May 10 09:22:52 2010 +0100
|
|
|
|
|
|
|
|
|
|
|
| |
It is invalid because we get vmexit via IRET interception in this
case. VINTR is unaware of NMI shadows and may vmexit early, leaving us
in an endless loop of VINTR injections and interceptions.
Signed-off-by: Wei Wang <wei.wang2@amd.com>
Signed-off-by: Keir Fraser <keir.fraser@citrix.com>
xen-unstable changeset: 21331:bbf009817ffb
xen-unstable date: Fri May 07 19:22:28 2010 +0100
|
|
|
|
|
|
| |
Signed-off-by: Xiao Guangrong <xiaoguangrong@cn.fujitsu.com>
xen-unstable changeset: 21325:535bf8e72dd2
xen-unstable date: Fri May 07 10:00:43 2010 +0100
|
|
|
|
|
|
|
|
|
|
|
| |
Using the CPU number to compare with an index into an array containing
only a subset of CPUs isn't valid. And indicator isn't necessary here
at all since the CPU number being dealt with gets printed right before
this line.
Signed-off-by: Jan Beulich <jbeulich@novell.com>
xen-unstable changeset: 21324:3b7228548a64
xen-unstable date: Fri May 07 09:50:17 2010 +0100
|
|
|
|
|
|
|
|
| |
Support tap2 device type in xend blkif utils parse method.
Signed-off-by: Jim Fehlig <jfehlig@novell.com>
xen-unstable changeset: 21317:5ac6e33fa3a7
xen-unstable date: Fri May 07 09:27:40 2010 +0100
|
|
|
|
|
|
|
|
|
| |
Also replaces the call to 'puts' with 'print' as the former is
undefined in python
Signed-off-by: Goncalo Gomes <Goncalo.Gomes@eu.Citrix.com>
xen-unstable changeset: 21296:460d156da874
xen-unstable date: Thu May 06 11:13:22 2010 +0100
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Fix booting through iSCSI protocol with Broadcom network cards.
These boards use the option ROM feature to implement the TCP/IP stack
protocol, and the iSCSI software initiator. The memory address
normally used by the PMM is 0x87000 which conflicts with the memory
allocation for Xen's trampoline routine, currently 0x88000.
Relocating down to 0x7c000 fixes the problem.
Signed-off-by: Fabio Guarneri <fabioguarneri@gmail.com>
xen-unstable changeset: 21276:fd44f1c0d3d6
xen-unstable date: Tue May 04 12:51:33 2010 +0100
|
|
|
|
|
|
|
|
|
|
| |
The location of the file in the build tree changed in recent Linux;
since there can be only one such file, using a wild card instead of
an explicit directory name seems the easiest solution.
Signed-off-by: Jan Beulich <jbeulich@novell.com>
xen-unstable changeset: 21273:d2373000996d
xen-unstable date: Tue May 04 12:42:56 2010 +0100
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Unfortunately the changes in c/s 21035 caused boot time to go up
significantly on certain large systems. To rectify this without going
back to the old behavior, introduce a new memory allocation flag so
that Dom0 allocations can exhaust non-DMA memory before starting to
consume DMA memory. For the latter, the behavior introduced in
aforementioned c/s gets retained, while for the former we can now even
try larger chunks first.
This builds on the fact that alloc_chunk() gets called with non-
increasing 'max_pages' arguments, end hence it can store locally the
allocation order last used (as larger order allocations can't succeed
during subsequent invocations if they failed once).
Signed-off-by: Jan Beulich <jbeulich@novell.com>
xen-unstable changeset: 21272:b07edd50661e
xen-unstable date: Tue May 04 12:42:21 2010 +0100
|
|
|
|
|
|
| |
Signed-off-by: Jan Beulich <jbeulich@novell.com>
xen-unstable changeset: 21270:bd52f2e040e5
xen-unstable date: Tue May 04 12:39:29 2010 +0100
|
|
|
|
|
|
|
|
|
|
|
|
| |
When I tried to use QCow image, I found that only each second boot is
successful. As I discovered, this is caused by wrong handling old qcow
tapdisk images. Extended header flag is not stored correctly so the
blktap tries to change endian fo L1 table on each startup.
From: Miroslav Rezanina <mrezanin@redhat.com>
Signed-off-by: Keir Fraser <keir.fraser@citrix.com>
xen-unstable changeset: 21269:d6cf080505cd
xen-unstable date: Tue May 04 12:38:19 2010 +0100
|
|
|
|
|
|
|
| |
Signed-off-by: Shane Wang <shane.wang@intel.com>
Signed-off-by: Keir Fraser <keir.fraser@citrix.com>
xen-unstable changeset: 21266:6d21da6feb59
xen-unstable date: Tue May 04 12:29:05 2010 +0100
|
|
|
|
|
|
|
|
|
| |
If you enable legacy tcp xmlrpc in xend's config but omit to enable
ssl then a backtrace is generated when starting xend.
Signed-off-by: Arnd Hannemann <hannemann@nets.rwth-aachen.de>
xen-unstable changeset: 21265:71cf9b12ac9e
xen-unstable date: Tue May 04 12:23:54 2010 +0100
|
|
|
|
|
|
| |
Signed-off-by: Yu Zhiguo <yuzg@cn.fujitsu.com>
xen-unstable changeset: 21258:31a6937e2359
xen-unstable date: Tue May 04 12:10:54 2010 +0100
|
|
|
|
|
|
|
|
|
|
|
| |
PAT caching was only propagated if has_arch_pdevs(),
causing the hvm_get_mem_pinned_cacheattr() to be ignored
in the non passthrough case.
l1_disallow_mask() needs to be relaxed.
Signed-off-by: Jean Guyader <jean.guyader@citrix.com>
xen-unstable changeset: 21236:9a1d7caa2024
xen-unstable date: Mon Apr 26 12:13:23 2010 +0100
|
|
|
|
|
|
|
|
|
|
|
| |
This patch allows guests that have directly mapped MMIO regions to set
the caching attributes for them, and only for them.
Currently we have just an on/off check for a directly assigned device
instead of looking for directly mapped MMIO regions.
Signed-off-by: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
xen-unstable changeset: 21119:5fdfbdd6ca41
xen-unstable date: Thu Apr 08 15:30:52 2010 +0100
|
|
|
|
|
|
|
|
|
| |
Otherwise, pass-through code may call memory allocation functions with
invalid node IDs, causing the allocations to fail.
Signed-off-by: Jan Beulich <jbeulich@novell.com>
xen-unstable changeset: 21234:d01ea51fc929
xen-unstable date: Mon Apr 26 12:11:30 2010 +0100
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The previous scheme --- freeing an area of BSS --- did not interact
nicely with device passthrough as IOMMU will not have any Xen BSS area
in guest device pagetables. Hence if the freed BSS space gets
allocated to a guest, DMAs to guest's own memory can fail.
The simple solution here is to always free the static buffer at end of
boot (initmem is specially handled for IOMMUs) and require a
dynamically-allocated buffer always to be created.
Signed-off-by: Keir Fraser <keir.fraser@citrix.com>
xen-unstable changeset: 21225:2b97855a629f
xen-unstable date: Thu Apr 22 17:43:56 2010 +0100
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
If domain creation in xend fails before devices are configured, e.g.
insufficient memory, device config is dropped from xend's managed
domain config.
Once xend is restarted, the domain's devices are lost.
This patch fixes a bug in XendConfig where only the device
controller was consulted for device configuration.
Signed-off-by: Jim Fehlig <jfehlig@novell.com>
xen-unstable changeset: 21223:5b72f9832cc2
xen-unstable date: Thu Apr 22 09:42:37 2010 +0100
|
|
|
|
|
|
| |
Signed-off-by: Dan Magenheimer <dan.magenheimer@oracle.com>
xen-unstable changeset: 21211:c7d7797656df
xen-unstable date: Wed Apr 21 08:31:31 2010 +0100
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Fixes the build error below:
gmake[5]: Entering directory `xen/arch/x86/boot'
gcc -O1 -fno-omit-frame-pointer -fno-optimize-sibling-calls -m32
-march=3Di686 -g -fno-strict-aliasing -std=3Dgnu99 -Wall
-Wstrict-prototypes
-Wno-unused-value -Wdeclaration-after-statement -fno-stack-protector
-Werror -fno-builtin -msoft-float -c reloc.c -o reloc.o
ld -melf_i386 -N -Ttext -o reloc.lnk reloc.o
ld: invalid hex number `-o'
BSD sed does not support the '+' in the basic re while gnu sed does.
BSD sed supports '+' in the extended re and uses the -E flag while
gnu sed uses -r.
The only difference with the original version is that the '+'
qualifier is replaced with '\{1\,\}' which should work with both BSD
sed and GNU sed.
Signed-off-by: Christoph Egger <Christoph.Egger@amd.com>
Acked-by: Ian Jackson <ian.jackson@eu.citrix.com>
xen-unstable changeset: 21210:b36467432eff
xen-unstable date: Wed Apr 21 08:30:45 2010 +0100
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
I noticed that 2 scripts in Xen 4.0.0 are calling "gawk". Normally, in
most distributions, gawk is considered a specific version of awk.
Calling "gawk" and not "awk" generally means that you need
specificities of the "g" version of awk, as opposed to "mawk" which is
another implementation of the same tool.
So, unless I misread the scripts, Xen doesn't need to use gawk but
just any implementation of awk, and the attached patch can safely be
applied.
If I am wrong (which I don't think I am at the first look) and that
there's a reason why gawk is used and not awk, then IMHO, the toplevel
README should mention it in the prerequisites.
From: Thomas Goirand <thomas@goirand.fr>
Signed-off-by: Keir Fraser <keir.fraser@citrix.com>
xen-unstable changeset: 21195:e5376ececd8b
xen-unstable date: Mon Apr 19 09:00:30 2010 +0100
|
|
|
|
|
|
|
|
|
|
| |
blktapctrl supports both 'tapdisk' and 'ioemu' subtypes in tap
protocol specification. Support the 'ioemu' subtype in xend
BlktapController as well.
Signed-off-by: Jim Fehlig <jfehlig@novell.com>
xen-unstable changeset: 21194:551a8406e840
xen-unstable date: Mon Apr 19 08:59:14 2010 +0100
|
|
|
|
|
|
|
|
|
| |
Perhaps this should even be further generalized (e.g. to remove any
"[!/]*:" pattern prefixes) to be more forward compatible?
Signed-off-by: Jan Beulich <jbeulich@novell.com>
xen-unstable changeset: 21193:ae1abcdd4a67
xen-unstable date: Mon Apr 19 08:58:43 2010 +0100
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
trailing-zero-elimination
Add "page deduplication" capability (with optional compression
and trailing-zero elimination) to Xen's tmem.
(Transparent to tmem-enabled guests.) Ephemeral pages
that have the exact same content are "combined" so that only
one page frame is needed. Since ephemeral pages are essentially
read-only, no C-O-W (and thus no equivalent of swapping) is
necessary. Deduplication can be combined with compression
or "trailing zero elimination" for even more space savings.
Signed-off-by: Dan Magenheimer <dan.magenheimer@oracle.com>
xen-unstable changeset: 21103:61372a4f4e76
xen-unstable date: Tue Apr 06 07:11:48 2010 +0100
|
|
|
|
|
|
|
|
|
|
| |
This approach is more straightforward, in that it simply works the
original e820 map. It's what the user expects, and reporting a smaller
value is never appreciated. ;-)
Signed-off-by: Keir Fraser <keir.fraser@citrix.com>
xen-unstable changeset: 21190:7ee8bb40200a
xen-unstable date: Thu Apr 15 19:11:16 2010 +0100
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
We recently found that FreeBSD 8.0 guest failed to install and boot on
Xen. The reason was that FreeBSD detected clflush feature and invoked
this instruction to flush MMIO space. This caused a page fault; but
x86_emulate.c failed to emulate this instruction (not supported). As a
result, a page fault was detected inside FreeBSD. A similar issue was
reported earlier.
http://lists.xensource.com/archives/html/xen-devel/2010-03/msg00362.html
From: Wei Huang <wei.huang2@amd.com>
Signed-off-by: Keir Fraser <keir.fraser@citrix.com>
xen-unstable changeset: 21189:d18e6a6c618a
xen-unstable date: Thu Apr 15 18:47:58 2010 +0100
|
|
|
|
|
|
|
|
|
|
| |
Due to changes in grub2, menu entry titles now have single quote
around them rather than double quotes, but the memtest entries still
are using double quotes, so we need to catch both.
Signed-off-by: David Markey <david.markey@citrix.com>
xen-unstable changeset: 21188:ffffddc4b1e0
xen-unstable date: Thu Apr 15 17:36:55 2010 +0100
|
|
|
|
|
|
|
|
| |
Describe the --reserve-disk-space option in the xentrace help.
Signed-off-by: George Dunlap <george.dunlap@eu.citrix.com>
xen-unstable changeset: 21164:c02cc832cb2d
xen-unstable date: Tue Apr 13 18:19:33 2010 +0100
|