Clean up timer upcalls to guest kernel. Only send an upcall when
timestamp info actually changes.
Signed-off-by: Keir Fraser <keir.fraser@cl.cam.ac.uk>
This patch enables argument passing to plan 9 domains, so that users can
now have parameters for things like Venti etc.
Signed-off-by: ron minnich <rminnich@lanl.gov>
Signed-off-by: ian.pratt@cl.cam.ac.uk
From: Jari Ruusu via Pasi Kärkkäinen [pasik@iki.fi]
Small fix to 2.4 blkfront such that the capacity is reported correctly.
Does 2.6 need a similar fix?
Signed-off-by: ian@xensource.com
Clean up task-switch path. Now differs more from native code, but
it is a critical path. Also fixed a comment and FPU TS setting.
Signed-off-by: Keir Fraser <keir@xensource.com>
Build AGP and DRM modules into linux 2.6-xen0 default kernel.
WARNING: Not all of these drivers have been tested, and its possible that
previously working X setups will now cause the machine to spontaneously
reboot when X starts! If so, please report these problems, and disable
the AGP/DRM module that is being used.
Signed-off-by: ian.pratt@cl.cam.ac.uk
Rename check_pagetable() function to _check_pagetable to make it easier
to selectively enable it during debugging. There's still the same
check_pagetable macro, but now it's used both when SHADOW_DEBUG is
enabled and disabled.
Bug fix for shadow code.
When update_va_mapping() updates a entry, the corresponding shadow
entry may not be reachable via the shadow_linear_pg_table, even though
it is currently shadowed, as the corresponding spde has not necessarily
been faulted into place yet.
Fixes to make the vnet module compile under 2.6.10.
Thanks to Brian Bruce for spotting the problem and
suggesting fixes.
Signed-off-by: Mike Wray <mike.wray@hp.com>
Subject: [Xen-devel] [PATCH] Fix initrd support for Linux 2.4/2.6
The following patch sets the default root device to be the null device.
This is the behavior Linux is launched with no root device specified in
the command line and without a device provided by the boot loader.
Previously, the default root device was set to be /dev/ram0. This broke
initrd support. This change was made in 2.6 to because of a bug
reported on September 14th with dynamic ipconfig. I've recreated his
problem and looked through the code and the source of the problem was
that his kernel command line was incorrect. He was missing the BOOTP
field in the config line requiring that there be an actual root device.
This worked with 2.4 but only because 2.4 was also broken. His patch
just introduced that bug into 2.6.
I've tested this against the 2.6 and 2.4 trees in a recent copy of
xen-unstable. I've tested initrd support and ipconfig support
(including dynamic ip support). They both now work as expected.
If anyone needs an initrd for testing let me know.
Regards,
--
Anthony Liguori
Linux Technology Center (LTC) - IBM Austin
E-mail: aliguori@us.ibm.com
Phone: (512) 838-1208
Signed-off-by: Anthony Liguori
Signed-off-by: ian@xensource.com
Some functions aren't static and could be (damn C language!).
I tried turning on -Wmissing-prototypes: unfortunately gives warnings
for functions used in asm, which means introducing gratuitous prototypes
for them. Not sure it's worth it.
1) keyhandler.c: keypress_softirq() and do_task_queues() can be static.
2) physdev.c: pcidev_dom0_hidden() can be static.
3) resource.c/resource.h: check_region is deprecated (racy): remove.
4) sched_bvt.c: lots of things can be static.
5) pci/compat.c: not required for Xen.
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> (authored)
Signed-off-by: ian.pratt@cl.cam.ac.uk
This very simple patch is really just cosmetic. It "fixes" xend so that
it doesn't report restart as: "WARNING (XendDomainInfo:1038) Unknown
config field restart" in the xend.log. I'm not sure who should sign off
on this, but the patch is attached.
From: "B.G. Bruce" <bgb@nt-nv.com>
Signed-off-by: ian@xensource.com
As pointed out on the xen-devel list, the vm86 call was not very robust in
Xen.
It turned out to be due to a missing check in the pagefault handler,
determining whether the pagefault came from userspace or from the kernel.
Now the syscall-crash tool doesn't cause any "Oops" on the vm86 calls anymore.
From: Stephan Diestelhorst <sd386@cam.ac.uk>
Signed-off-by: ian.pratt@cl.cam.ac.uk
