similar to: x86/dom0: limit dom0_max_vcpus value

Hi experts, Q1:What''s the different for "dom0_max_vcpus=4 dom0_vcpus_pin" and "dom0_max_vcpus=4" ? which will get better performance Q2: dom0_max_vcpus=4 means "core0-3 will be just used by dom0" or means "4 cores(not dedicate cores) will be used by dom0, eg: core2-5 or core3-6? Q3.what does mean "nosmp" , xen, dom0,domU, will just use one

Hi experts, Q1:What''s the different for "dom0_max_vcpus=4 dom0_vcpus_pin" and "dom0_max_vcpus=4" ? which will get better performance Q2: dom0_max_vcpus=4 means "core0-3 will be just used by dom0" or means "4 cores(not dedicate cores) will be used by dom0, eg: core2-5 or core3-6? Q3.what does mean "nosmp" , xen, dom0,domU, will just use one

Hello, I''m unable to boot a dom0 3.4.x kernel on top of xen4.1.x Xen seems to boot fine but the dom0 is crashing without any error: (XEN) Xen trace buffers: disabled (XEN) Std. Loglevel: All (XEN) Guest Loglevel: All (XEN) *** Serial input -> DOM0 (type ''CTRL-a'' three times to switch input to Xen) (XEN) Freed 232kB init memory. mapping kernel into physical memory

This issue came up when debugging pcpu linked list corruption (patches for that issue to follow). -- Andrew Cooper - Dom0 Kernel Engineer, Citrix XenServer T: +44 (0)1223 225 900, http://www.citrix.com _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel

XSA-36 changed the default vector map mode from global to per-device. This is because a global vector map does not prevent one PCI device from impersonating another and launching a DoS on the system. However, the per-device vector map logic is broken for devices with multiple MSI-X vectors, which can either result in a failed ASSERT() or misprogramming of a guests interrupt remapping tables.

We have tested latest xen on VT platform with Intel 915/E8500 chipset.Here is the test summary. Issues: - IA-32 VMX guest will hang when booting on IA-32PAE host with acpi=1 and apic=1.(Bug 594) - Failed to created VMX after tens of VMXs have been created & destroyed on IA-32e.(Bug593) IA-32: Build&Boot SMP xen0 without problem Can bootup unmodified IA-32 2.4/2.6 linux in VMX

Hi all, I need a periodic timer running at ideally at 125 microseconds and at least 500 microseconds. I''ve just found the VCPUOP_set_periodic_timer, however there is a comment saying "periods less than one millisecond may not be supported". I will be running on an x64 machine. Is this supported? If not, is there any alternate means of generating a fast interrupt? Regards.

This series consists of improvements to Xen''s ability to print traces of its own stack, and specifically for the stack overflow case to be able to use frame pointers in a debug build. I have dev tested the series in debug and non-debug cases, with and without memory guards, and I believe that all the stack traces look correct. However, I would greatly appreciate a second opinion on the

Coverity IDs 1054956, 1054957 Coverity pointed out that we applying array operations based on an expression which yielded singleton pointers. The problem is actually that the externs were typed incorrectly. Correct the extern declaration to prevent straying into undefined behaviour, and relying on the lenience of GCC to work. Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com> CC:

I'm trying to install ocfs using RHAS 2.1 uniprocessor kernel on a vmware gsx server 3.0 virtual machine and I'm getting the unresolved symbols error when I try to start ocfs. I'm using the following packages: ocfs-tools-1.0.10-1.i386.rpm ocfs-support-1.0.10-1.i386.rpm ocfs-2.4.9-e-1.0.11-1.i686.rpm My kernel is 2.4.9-e.38 uniprocessor (compiled by me). Questions: 1) Am I using the

Hi All, I have a windows 7 as my domU and some windows based drivers are not fully functional (like: touchpad-driver etc ) because they are SMBus based. I was looking at a way to passthrough the SMBus at 00:1f.03 on south bridge ( 00:1f.0), I was debugging at pt-graphics.c and understand that it is detecting the south bridge and passing it through but the other functions for the same dev-id are

On 15/07/2019 19:17, Nadav Amit wrote: >> On Jul 15, 2019, at 8:16 AM, Andrew Cooper <andrew.cooper3 at citrix.com> wrote: >> >> There is a lot of infrastructure for functionality which is used >> exclusively in __{save,restore}_processor_state() on the suspend/resume >> path. >> >> cr8 is an alias of APIC_TASKPRI, and APIC_TASKPRI is saved/restored

On 15/07/2019 19:17, Nadav Amit wrote: >> On Jul 15, 2019, at 8:16 AM, Andrew Cooper <andrew.cooper3 at citrix.com> wrote: >> >> There is a lot of infrastructure for functionality which is used >> exclusively in __{save,restore}_processor_state() on the suspend/resume >> path. >> >> cr8 is an alias of APIC_TASKPRI, and APIC_TASKPRI is saved/restored

The DMI checks that force the use of the bigsmp APIC driver are for systems that are no longer supported by Xen (32-bit x86). Signed-off-by: Matt Wilson <msw@amazon.com> Cc: Keir Fraser <keir@xen.org> Cc: Jan Beulich <jbeulich@suse.com> Cc: Andrew Cooper <andrew.cooper3@citrix.com> --- xen/arch/x86/genapic/bigsmp.c | 30 +----------------------------- 1 files changed, 1

This patch is based on one which has been in XenServer for a very long. To keep the trend of documentation going, it also corrects the new command line document. -- Andrew Cooper - Dom0 Kernel Engineer, Citrix XenServer T: +44 (0)1223 225 900, http://www.citrix.com _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel

The self_nmi() code cause''s an NMI to be triggered by sending an APIC message to the local processor. However, NMIs are blocked by the VMEXIT, until the next iret or VMENTER. Volume 3 Chapter 27 Section 1 of the Intel SDM states: An NMI causes subsequent NMIs to be blocked, but only after the VM exit completes. As a result, as soon as the VMENTER happens, an immediate VMEXIT happens

With GPLPV under 2.6.30, GPLPV gets the following from the ring: ring slot n (first buffer): status (length) = 54 bytes offset = 0 flags = NETRXF_extra_info (possibly csum too but not relevant) ring slot n + 1 (extra info) gso.size (mss) = 1460 Because NETRXF_extra_info is not set, that''s all I get for that packet. In the IP header though, the total length is 1544 (which in itself

With GPLPV under 2.6.30, GPLPV gets the following from the ring: ring slot n (first buffer): status (length) = 54 bytes offset = 0 flags = NETRXF_extra_info (possibly csum too but not relevant) ring slot n + 1 (extra info) gso.size (mss) = 1460 Because NETRXF_extra_info is not set, that''s all I get for that packet. In the IP header though, the total length is 1544 (which in itself

Hi all, My Ct's box is RH 3.0 SMP kernel EM64T. They are asking if OCFS for SMP (EM64T) is available or not. In following site, we can not see OCFS for SMP (EM64T). http://oss.oracle.com/projects/ocfs/files/RedHat/RHEL3/x86_64/1.0.14-1/ ---------- ocfs-2.4.21-EL-1.0.14-1.ia32e.rpm OCFS driver for kernel version 2.4.21-27.EL and higher (EM64T) ocfs-2.4.21-EL-1.0.14-1.src.rpm OCFS driver

Do you have anything detailing what the goal of each phase in Xenrt is? Phases 4 and 5 seem to be pretty much identical. Thanks, Paul Larson _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel