search for: joserenato

Renato, When I tried running "opcontrol --start" (after previously running "opcontrol --start-daemon") in dom0, I get this error message: /usr/local/bin/opcontrol: line 1639: echo: write error: Operation not permitted and this message in the Xen console: (XEN) xenoprof: operation 9 failed for dom 0 (status : -1) It looks like opcontrol is trying to do this: echo 1 >

Renato, When I tried running "opcontrol --start" (after previously running "opcontrol --start-daemon") in dom0, I get this error message: /usr/local/bin/opcontrol: line 1639: echo: write error: Operation not permitted and this message in the Xen console: (XEN) xenoprof: operation 9 failed for dom 0 (status : -1) It looks like opcontrol is trying to do this: echo 1 >

my system configuration xen 3.4.2, oprofile 0.9.5( xenoprof patched ), dom0( jeremy''s pvops kernel 2.6.31.6 - patched dullor''s xenoprof patch ), domU( vanilla kernel 2.6.32 with paravirt enabled ), distribution( ubuntu 9.10 ) In passive mode, xenoprof seems to work well, opreport showed good information. but, in active mode, it seems not to be done correctly. my command is

Hi, Xenoprof buffers are mapped into the kernel using direct_kernel_remap_pfn_range(). I need to unmap the buffer when it is not needed anymore. However, I could not find any function that unmaps pages previously mapped with direct_kernel_remap_pfn_range(). Any suggestion on how to do this? Thanks Renato _______________________________________________ Xen-devel mailing list

Hi I am using oprofile 0.9.3 on xen cs 16540 on an Intel system. When I look at the top "hot" functions, I see p2m_change_type being one of the top function in xen-syms. This function is only in the svm (AMD) code and should not appear on an Intel system. I see that this function is not being clled at all when I am running my apps as I have put printk in the functions and they do

This is a repost of the RCU patch I have posted some time ago. The only change from the previous post, was to move it to a more recent version of xen-unstable (changeset 13386). I am planning to submit the following additional patches, after this one is accepted: 1) rename_find_domain.patch: Rename find_domain_by_id() to get_domain_by_id() 2) add_find_domain.patch: Add new

This is a repost of the RCU patch I have posted some time ago. The only change from the previous post, was to move it to a more recent version of xen-unstable (changeset 13386). I am planning to submit the following additional patches, after this one is accepted: 1) rename_find_domain.patch: Rename find_domain_by_id() to get_domain_by_id() 2) add_find_domain.patch: Add new

The correct kernel configuration for VMDq support is CONFIG_XEN_NETDEV2_VMQ, not CONFIG_XEN_NETDEV2_BACKEND. Signed-off-by: Mitch Williams <mitch.a.williams@intel.com> diff -urpN a/drivers/net/ixgbe/ixgbe.h b/drivers/net/ixgbe/ixgbe.h --- a/drivers/net/ixgbe/ixgbe.h 2009-02-06 09:03:44.000000000 -0800 +++ b/drivers/net/ixgbe/ixgbe.h 2009-02-10 14:32:57.000000000 -0800 @@ -35,7 +35,7 @@

Hi Renato, This patch is to add Xenoprof passive domain support in SMP environment. Basically: - It allocates per vcpu buffers for passive domain and maps them into primary domain''s space. - When primary domain gets sampled and triggers virq, its kernel module will handle passive domain'' samples besides its owns. There is potential buffer overflow if passive is very busy while

This patch adds experimental VMDq support (AKA Netchannel2 vmq) to the ixgbe driver. This applies to the Netchannel2 tree, and should NOT be applied to the "normal" development tree. To enable VMDq functionality, load the driver with the command-line parameter VMDQ=<num queues>, as in: $ modprobe ixgbe VMDQ=8 You can then set up PV domains to use the device by modifying your VM

These patches address issues in the kernel part of xenoprof: * Ill-advised use of on_each_cpu() can lead to sleep with interrupts disabled. * Race conditions in active_domains code. * Cleanup of active_domains code. Comments welcome. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

Hi , I am getting following error when i try to run xenoprof /usr/local/bin/opcontrol: line 1082: echo: write error: Invalid argument Using 2.6+ OProfile kernel interface. Reading module info. Using log file /var/lib/oprofile/oprofiled.log Daemon started. what is this write error ? Any help is really appreciated. -John _______________________________________________ Xen-users mailing list

Hi , I am getting following error when i try to run xenoprof /usr/local/bin/opcontrol: line 1082: echo: write error: Invalid argument Using 2.6+ OProfile kernel interface. Reading module info. Using log file /var/lib/oprofile/oprofiled.log Daemon started. what is this write error ? Any help is really appreciated. -John _______________________________________________ Xen-users mailing list

>> >> Is the nmi_sanity_check() needed? We shouldn''t lose NMIs: >> even if we take one while doing NMI processing, we sholuld >> retake the NMI as soon as the first one IRETs. >> The nmi_sanity_check() should not be needed if everything is working fine. However I suggest we should keep it for now until we are sure it is safe to remove it. I would

The attached patches add vmq (multi-queue) support for netchannel2. (also known as VMDq) These patches were based on a previous implementation written for netchannel1 by Kaushik Kumar Ram. These patches are based on the latest netchannel2 public trees. Patches 1 and 2 are for the Xen tree and patches 3 and 4 for the linux tree. This version provides the basic multi-queue functionality but does