We should not panic the domain for an EINVAL return from the ioremap
hyerpcall. This was only meant for ENOSYS. Long term this is probably
not the best place for this kind of sanity checking.
Signed-off-by: Alex Williamson <alex.williamson@hp.com>
OK, this is the last one of patch sets, which enables xen/ia64 to work
on event channel mechanism fully. Now user may observe /proc/interrupts
of dom0 as:
CPU0
34: 12 Phys-irq ide0
39: 0 Phys-irq acpi
45: 322 Phys-irq serial
48: 115006 Phys-irq peth0
49: 16269 Phys-irq ioc0
50: 31 Phys-irq ioc1
51: 2 Phys-irq ehci_hcd:usb1
52: 0 Phys-irq uhci_hcd:usb2
53: 55 Phys-irq uhci_hcd:usb3
256: 0 Dynamic-irq RESCHED0
257: 0 Dynamic-irq IPI0
258: 44572 Dynamic-irq timer0
259: 2316 Dynamic-irq xenbus
260: 8304 Dynamic-irq blkif-backend
261: 25947 Dynamic-irq vif3.0
ERR: 0
Based on this patch, dom0's performance is not affected, while domU's
network output is seen with several percents increase. More important,
now xen/ia64 can progress a base step towards driver domain support!
Signed-off-by Kevin Tian <kevin.tian@intel.com>
Cleaner and allows use by architectures which aren't currently
using Xen's smpboot.c.
Based on an original patch by Tristan Gingold.
Signed-off-by: Keir Fraser <keir@xensource.com>
This patch adds a missing privop definition for ia64_trace_syscall
when CONFIG_XEN is unset. It also cleans up some inconsistent
spacing.
Signed-off-by: Aron Griffis <aron@hp.com>
initialising a Xen-specific driver or subsystem.
For ia64:
* Call xen_init in setup_arch.
* Remove xen_ksyms.c
Signed-off-by: Tristan Gingold <tristan.gingold@bull.net>
dom0 vp model: remove populate_physmap hypercall which becomes unnecesarry
because xenmem operation is fully supported by the previous patch.
Signed-off-by: Isaku Yamahata <yamahata@valinux.co.jp>
Add a new __xen_guest header field to distinguish between kernels with
the previous use of the paddr field and the new use.
Add a new __xen_guest header field to control the kernel entry point,
since the elf header entry field now points to a physical address.
This header field is also useful for supporting alternative entry
points in kernel images which run both on xen and native.
Also add a kernel config option to control whether the resulting kernel
should include compatibility code to run on Xen 3.0.2 or whether such
code such be left out, resulting in a kernel which will only run on
newer Xen versions. Default to having compatibility enabled.
Kernels built with the new use of the elf header fields would otherwise
not work on Xen versions prior to this changeset.
Signed-off-by: Christian Limpach <Christian.Limpach@cl.cam.ac.uk>
add trivial definitions, MULTI_UVMFLAGS_INDEX and MULTI_update_va_mapping()
to compile netback and netfront
Signed-off-by: Isaku Yamahata <yamahata@valinux.co.jp>
xen/ia64 XENMEM_increase_reservation, XENMEM_decrease_reservation,
XENMEM_populate_reservation are broken.
work around for it.
This patch should be removed after those hypercalls are fixed.
Signed-off-by: Isaku Yamahata <yamahata@valinux.co.jp>
add defeinitions of arch_free_page()
work around for PG_foreign. xen/ia64 uses PG_arch1.
This work around sould be removed once PG_foreign is taken.
Signed-off-by: Isaku Yamahata <yamahata@valinux.co.jp>
Current xen/ia64 grant table ignores some GNTMAP_xxx flags.
work around for that. This patch will be removed once the flags are supported.
Signed-off-by: Isaku Yamahata <yamahata@valinux.co.jp>
- moves the TPM frontend completely into the char/tpm directory where it
is a plug-in to the generic TPM driver
- removes a now obsolete include file
- adapts part of the documentation
- fixes some locking problems where copy_to/from_user was called with
IRQs blocked
Signed-off-by: Stefan Berger <stefanb@us.ibm.com>
interface (the legacy hypercalls would break if subcommands with large
argument structures were added, as it would grow the size of the
union of all argument structures).
Also, based on a patch from Kevin Tian, add a new physdev op to
signal EOI for a particular irq.
Signed-off-by: Keir Fraser <keir@xensource.com>
Add support to physdev ops, and thus give IOSAPIC RTEs
managed by Xen now. Dom0 now issues hypercall to r/w
RTE entry. Another change is the irq vector allocation
which is also owned by xen now.
After this change, the IOSAPIC is almost owned by xen
with only exception as IOSAPIC EOI which is still issued
by dom0 directly. But that's OK since currently dom0
owns all external physical devices. Later full event
channel mechanism will provide necessary support for
driver domain, and at that time, dom0 instead issues
physdev_op (PHYSDEVOP_IRQ_UNMASK_NOTIFY) naturally as
replace of IOSAPIC EOI.
Signed-off-by Kevin Tian <kevin.tian@intel.com>
