not to let the guest disable interrupts in the real EFLAGS.
Signed-off-by: Ian Campbell <ian.campbell@citrix.com
xen-unstable changeset: 21700:fae04060a4f4
xen-unstable date: Wed Jun 30 18:12:43 2010 +0100
Use gfn_to_mfn_query() rather then gfn_to_mfn() when changing
P2M types since we do not really want to force a PoD allocation
as a side effect.
Signed-off-by: Paul Durrant <Paul.Durrant@citrix.com>
xen-unstable changeset: 21699:7cda3ad44c6d
xen-unstable date: Wed Jun 30 18:11:42 2010 +0100
There's no need to share writably the t_info pages (Dom0 only wants
[and needs] to read it)
Signed-off-by: Jan Beulich <jbeulich@novell.com>
Acked-by: George Dunlap <george.dunlap@eu.citrix.com>
xen-unstable changeset: 21695:c5f3fe17374c
xen-unstable date: Tue Jun 29 18:18:42 2010 +0100
Set the types in the public memory_event header file to use
fixed-sized and self-aligned fields rather than "unsigned long". AIUI
this feature only works with 64-bit hypervisors but I think this
change will be necessary to use 32-on-64 dom0 tools.
This breaks compatibility with older builds of the tools, but I can't
see any way to avoid it short of __attribute__((__packed__)).
Signed-off-by: Tim Deegan <Tim.Deegan@citrix.com>
Acked-by: Patrick Colp <pjcolp@cs.ubc.ca>
xen-unstable changeset: 21694:2a3a5979e3f1
xen-unstable date: Tue Jun 29 18:17:44 2010 +0100
32-bit Xen doesn't have enough p2m types to support them.
Signed-off-by: Tim Deegan <Tim.Deegan@citrix.com>
xen-unstable changeset: 21693:6b5a5bfaf357
xen-unstable date: Tue Jun 29 18:16:41 2010 +0100
Since they're being passed to Dom0 using an array of uint32_t, they
must be representable as 32-bit quantities, and hence the buffer
allocation must specify an upper address boundary.
Signed-off-by: Jan Beulich <jbeulich@novell.com>
Acked-by: George Dunlap <george.dunlap@eu.citrix.com>
xen-unstable changeset: 21682:7e46fdbe8a11
xen-unstable date: Mon Jun 28 16:27:56 2010 +0100
IMQ does not work with ebtables on 2.6.31, and IFB is not a
third-party patch.
Signed-off-by: Brendan Cully <brendan@cs.ubc.ca>
xen-unstable changeset: 21244:0f403a63ef6b
xen-unstable date: Tue May 04 09:36:05 2010 +0100
Fix deprecation warning in Qdisc class under python 2.6.
Fix rtattr length and padding (rta_len is unaligned).
Null-terminate qdisc name in rtnl messages.
Signed-off-by: Brendan Cully <brendan@cs.ubc.ca>
xen-unstable changeset: 21238:99a85cb72c9f
xen-unstable date: Tue May 04 09:30:53 2010 +0100
must still be tmem-enabled to use this functionality (e.g.
won't work for Windows), but upstream Linux tmem (aka
cleancache and frontswap) patches apply cleanly on top
of PV on HVM patches.
Also, fix up some ASSERTS and code used only when bad guest
mfns are passed to tmem. Previous code could crash Xen
if a buggy/malicious guest passes bad gmfns.
Signed-off-by: Dan Magenheimer <dan.magenheimer@oracle.com>
xen-unstable changeset: 21648:72c6228b5f0f
xen-unstable date: Mon Jun 21 19:19:25 2010 +0100
This is a minor fix to the calculation of bit-width of fixed function
perfmon counters in Intel processors. Bits 5-12 of edx register
should be calculated as (edx & 0x1fe0) >>5 instead of using 0x1f70.
From: "John, Jaiber J" <jaiber.j.john@intel.com>
Signed-off-by: Keir Fraser <keir.fraser@citrix.com>
xen-unstable changeset: 21643:31708477f0a9
xen-unstable date: Mon Jun 21 09:59:10 2010 +0100
That value can, for forcibly unbound PIRQs, validly be negative, and
for the respective check to catch those cases (and prevent using these
negative values as array index), the respective variables must be of
signed type.
Signed-off-by: Jan Beulich <jbeulich@novell.com>
xen-unstable changeset: 21620:b0f7f710f512
xen-unstable date: Tue Jun 15 13:21:03 2010 +0100
Escalate to use a wider context invalidation if the requested context
invalidation is not supported.
Signed-off-by: Xin Li <xin.li@intel.com>
xen-unstable changeset: 21598:a822156d9fbb
xen-unstable date: Fri Jun 11 09:34:58 2010 +0100
Escalate to use all context invalidation if single context
invalidation is not supported.
Signed-off-by: Xin Li <xin.li@intel.com>
xen-unstable changeset: 21592:9db8fc1ca2ef
xen-unstable date: Thu Jun 10 17:30:23 2010 +0100
Also use a macro to get EPT walk length.
Signed-off-by: Xin Li <xin.li@intel.com>
xen-unstable changeset: 21591:def12332b19c
xen-unstable date: Thu Jun 10 11:18:02 2010 +0100
Make erratum 383 use msr safe variants to work on top of KVM.
Signed-off-by: Christoph Egger <Christoph.Egger@amd.com>
xen-unstable changeset: 21602:f086edac7f92
xen-unstable date: Fri Jun 11 13:57:52 2010 +0100
Obtaining a domain reference count is neither necessary nor
sufficient. Instead we simply check whether a domain is already dying
when it first becomes a client of tmem. If it is not then we will
correctly clean up later via tmem_destroy() called from domain_kill().
Signed-off-by: Keir Fraser <keir.fraser@citrix.com>
xen-unstable changeset: 21596:04e81a65d27e
xen-unstable date: Thu Jun 10 22:39:52 2010 +0100
which claims a ref once when the tmem client is first associated
with the domain, and puts it once when the tmem client is
destroyed.
Signed-off-by: Dan Magenheimer <dan.magenheimer@oracle.com>
xen-unstable changeset: 21595:39657b168068
xen-unstable date: Thu Jun 10 22:12:36 2010 +0100
This disables superpage restore support, but should gain us acceptable
performance when restoring a domain using a pv_ops dom0 kernel. This
is because single-page allocations will be batched rather than issued
singly.
Signed-off-by: Keir Fraser <keir.fraser@citrix.com>
xen-unstable changeset: 21588:6c3d8aec202d
xen-unstable date: Thu Jun 10 09:35:16 2010 +0100
Various function we may call assert this fact. We just want to restart
the system.
Signed-off-by: Keir Fraser <keir.fraser@citrix.com>
xen-unstable changeset: 21550:cb75117829a6
xen-unstable date: Mon Jun 07 16:41:19 2010 +0100
1. Bug fix for error: "Error: Device /dev/xvdp (51952, tap2) is
already connected." (xenstore does not clean after DomU stoped)
2. Bug fix for error: "File 'vhd:/path/.../disk.img' doesn't exist."
(not correct parsing)
3. Bug fix for error: "Error: Device 51952 not connected" (in config
file for DomU we should be use prefix "tap2:tapdisk:xxx" for devices
from (aio, ram, qcow, vhd, remus) or "tap:tapdisk:xxx" for devices
from (sync, vmdk, qcow2, ioemu))
4. Bug fix for error: "Disk is not accessible" (if use 'tap2'-device
type, then '/dev/xpvd' may not be accessible immediately after its
creation)
Signed-off-by: eXeC001er <execooler@gmail.com>
xen-unstable changeset: 21541:7ff0e885b5c3
xen-unstable date: Mon Jun 07 07:19:43 2010 +0100
If xen's time leaps forward by a large amount, the RTC will try to
model a tick for every second that it thinks has passed. This can
livelock a CPU with a series of timer requests each of which fires
immediately and requests the next one.
This patch treats a delay of more than a day between ticks as a
special case, abandoning the attempt to catch up. That should be good
enough to avoid livelock but doesn't fix the underlying time problem.
Signed-off-by: Tim Deegan <Tim.Deegan@citrix.com>
xen-unstable changeset: 21515:1b6c9732436b
xen-unstable date: Fri Jun 04 10:05:42 2010 +0100
RHEL4 guests take a fair number of spurious pagefaults on Nehalem; no
need to report each one of them at XENLOG_WARNING.
Signed-off-by: Tim Deegan <Tim.Deegan@citrix.com>
xen-unstable changeset: 21514:88932ba626fe
xen-unstable date: Fri Jun 04 10:04:30 2010 +0100
Keir Fraser