similar to: [Doc] writeup for error handling usage in XEN

ioemu-remote: The device model needs to write in the ACPI tables when it wakes up from S3 state. Signed-off-by: Jean Guyader <jean.guyader@eu.citrix.com> -- Jean Guyader _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

Following 7 patches are for PCIE AER (Advanced Error Reporting) support for XEN. --------------------------------------------------------------------------- Patches 1~4 back port from Linux Kernel which enables kernel support to AER. Those patches enable DOM0 PCIE error handling capability. When a device sends a PCIE error message to the root port, it will trigger an interrupt. The irq handler

Hi, All Following 4 patches are for enabling CMCI of Intel CPUs in XEN. --------------------------------------------------------------------------- Patch 1: remove_intel_mce_old.patch is to remove old p4/p6 files. The reason is that machine check architecture for Intel families including p4/p6/latest are similar. We need not keep duplicated codes. Patch 2: change_stop_machine_run.patch changes

Hi, Jeremy and all This small patch lets pv ops guest handle machine check trap. When non fatal mce error happens, xen will inject vMCE# to the impacted pv ops guest. This patch allows pv ops guest could receive machine check trap and enter its own machine check handler. Thanks & Regards, Criping >From 5efc12fe8214d55e2becc2c4b6ec4a30531d7b60 Mon Sep 17 00:00:00 2001 From: Liping Ke

[Patch 4/4]: Xend interface for HVM S3 - extend "xm resume <domid>" to be able to S3 resume HVM domain. - when user issue "xm resume" command for HVM domain, xend will use xc lib API to call HVMOP_s3_resume hypercall. Note: it may not appropriate use xm resume for HVM s3, since xm resume is originally designed for save/restor purpose. It will be fine that

The patch ''mem_event: use wait queue when ring is full'' I just sent out makes use of the waitqueue feature. There are two issues I get with the change applied: I think I got the logic right, and in my testing vcpu->pause_count drops to zero in p2m_mem_paging_resume(). But for some reason the vcpu does not make progress after the first wakeup. In my debugging there is one

Hi, On paravirt x86 (both 32- and 64-bit), since cset 13998: http://xenbits.xensource.com/xen-unstable.hg?rev/13998 we translate all ptes from being mfn-based to pfn-based when the hardware _PAGE_PRESENT bit is cleared. We do this for PROT_NONE pages, which appear to the HV to be non-present, but which are special-cased in the kernel to appear present (a different bit in the

I was trying to install Ubuntu 7.10 on an HVM domain, when when the install kept hanging at a particular point. xm dmesg shows the following : (XEN) realmode.c:132:d28 Failed to emulate insn. (XEN) realmode.c:174:d28 Real-mode emulation failed @ 0000:00007f34: 0f 2c 06 08 6b 04 (XEN) domain_crash called from realmode.c:175 (XEN) Domain 28 (vcpu#0) crashed on cpu#0: (XEN) ----[ Xen-3.4-unstable

Hi men, When installing Xen, it builds a linux guest kernel of 2.6.18 as dom0, which does not support my network card. While 2.6.27 supports my card. So what should I do now? Thanks, Wu _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

We saw these issues in recent ChangeSet: 1. Reboot fail in Guest OS: Reboot in guest will close current qemu windows but does not create a new qemu window to restart 32bit HV/xen0: 2. 4 LTP math cases(float_bessel, float_exp_log, float_power and float_trigo) sometime fail. (775) 3. Kernel build in VMX may meet kernel panic. It complains like: "<0> Kernel panic - not syncing:

lspci shows MSI enabled for PCI device. PCI passthrough works fine. However, as soon as the MSI driver for card is insmodded, kernel panics. This is on xen-unstable. Tried the same with xen-3.3.0 which is supposed to have MSI passthrough, but the same guest shows MSI as disabled. Any else seen this bug, or know of a workaround ? Trace is as follows : ------------[ cut here ]------------

Hi, all Some Latest Intel CPU models (CPUID.1.EAX >= 0x00010674) support cupid mask features. Cpuid feature mask is used to limit the feature flags reported by CPUID.1.EDX:ECX. This small patch adds CPUID feature mask support in XEN by adding boot options in Grub entry as below example: kernel /boot/xen.gz com1=115200,8n1 console=com1 cpuid_mask_ecx = 0xFFFF7FFF cpuid_mask_edx = 0xFFFFFFFC

While adding code to create the compatibility p2m table mappings it seemed to me that the creation of the native ones is restricted to memory below the 512G boundary - otherwise, additional L2 tables would need to be allocated (currently other memory following the one L2 page getting allocated would be blindly overwritten). While I realize that machines this big aren''t likely to be

Hello All, I''m contemplating ways to avoid the domain_crash() in mm.c line ~615 without requiring new OS hooks. This crash occurs when the operating system writes a zero to the PTE for a grant mapping without an explicit Xen call to unmap. In hacking around, it seems the problem is this: When the mapping PTE gets squashed, Xen''s cleanup_writable_pagetable() has no way to find

hi I try to understand the code of balloon ,and got confused about the following parts of code: static int decrease_reservation(unsigned long nr_pages) { .... if (!PageHighMem(page)) { v = phys_to_virt(pfn << PAGE_SHIFT); scrub_pages(v, 1); ret = HYPERVISOR_update_va_mapping( (unsigned long)v, __pte_ma(0), 0);

There is a BUG_ON() at xen/arch/x86/physdev.c:169 which appears to be dependent upon guest behavior (should close event channel before un-mapping pirq), rather than on internal hypervisor state. In 2.6.18, this likely goes unnoticed because pci_device_shutdown() only calls all the driver shutdown routines. In newer kernels, however, it also calls pci_msi_shutdown() and pci_msix_shutdown(), which

Better use of VMX execution controls MSR. Signed-off-by: Xin Li<xin.b.li@intel.com> _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

While working on a database scaling problem using a SAP database test suite we discovered that these enterprise level large shared memory databases are very heavy users of mprotect(), to the extent that the performance overhead in current Xenolinux impacts scaling beyond a few cpus quite badly. A single cpu run under Xen has a nominal impact, but scaling out to 8 cpus results in a performance of

Future AMD SVM supports a new feature called flush by ASID. The idea is to allow CPU to flush TLBs associated with the ASID assigned to guest VM. So hypervisor doesn''t have to reassign a new ASID in order to flush guest''s VCPU. Please review it. Thanks, Wei Signed-off-by: Wei Huang <wei.huang2@amd.com> Signed-off-by: Wei Wang <wei.wang2@amd.com> -- Advanced Micro

Signed-off-by: Wei Wang <wei.wang2@amd.com> -- AMD Saxony, Dresden, Germany Operating System Research Center Legal Information: AMD Saxony Limited Liability Company & Co. KG Sitz (Geschäftsanschrift): Wilschdorfer Landstr. 101, 01109 Dresden, Deutschland Registergericht Dresden: HRA 4896 vertretungsberechtigter Komplementär: AMD Saxony LLC (Sitz Wilmington, Delaware, USA)