similar to: Xen 4.3.1 / Linux 3.12 panic

Displaying 20 results from an estimated 1200 matches similar to: "Xen 4.3.1 / Linux 3.12 panic"

2014 Sep 19
3
sr-iov on Intel 82576 and rhel 7 - would not work
hi everybody a windows kvm guest would not start, process gets killed with: Out of memory: Kill process 21984 (qemu-kvm) score 44 or sacrifice child I really don't know where/what I might be missing, config seems fine, everything looks ok - I only am not sure, do I need to first stub a SR-IOV device like regular passthrough? I'm trying sr-iov, having one NIC left to the host and the
2012 Mar 06
4
Is: drivers/cpufreq/cpufreq-xen.c Was:Re: [PATCH 2 of 2] linux-xencommons: Load processor-passthru
.. snip.. >> Both of them (acpi-cpufreq.c and powernow-k8.c) have a symbol >> dependency on drivers/acpi/processor.c > > But them being ''m'' or ''y'' shouldn''t matter in the end. I thought you were saying it matters - as it should be done around the same time as cpufreq drivers were loaded? .. snip.. >> For a), this would mean some
2009 Aug 02
2
Can not modprobe acpi-cpufreq.ko in CentOS 5.2
Dear all, The cpufreq modules have been distributed in Centos. But recently, I met a problem when I tried to test the power-related applications. The module can not be modprobed in kernel notwithstanding releated with Centos distribution. The messgae thrown out is: ------------- dump of screen ------------ # modprobe p4-clockmod.ko FATAL: Module p4_clockmod.ko not found
2012 Feb 24
10
[PATCH 0 of 2] [RFC] Patches to work with processor-passthru driver (v1).
These two patches provide the neccessary infrastructure changes for the processor-passthru driver [www.spinics.net/lists/linux-acpi/msg34655.html] to properly function. The first one is quite easy - we just modprobe the processor-passthru driver. The second allows it to work under AMD machines by exposing the PM RDMSR to dom0. It has been tested with 2.6.32 kernel as well to make sure it does
2008 Jul 24
3
FW: cpufreq info propagation
it seems getting lost, and thus resend. Thanks, Kevin -----Original Message----- From: Tian, Kevin Sent: 2008年7月24日 8:39 To: ''Jan Beulich'' Cc: Liu, Jinsong; Keir Fraser; xen-devel@lists.xensource.com; mark.langsdorf@amd.com Subject: RE: [Xen-devel] cpufreq info propagation >From: Jan Beulich >Sent: 2008年7月23日 18:13 >> >>startup info is viable. But how
2008 Jul 23
3
cpufreq info propagation
Now that I finally got around to update our sources, I had a closer look at those changes, and apart from stylistic issues on the Linux side (part of which I may have asked for, but the result was somewhat overdone so the code is hardly legible now - I''ve got a patch queued to streamline this a little) I find it rather odd (fragile) that the who-is-in-charge information gets propagated
2009 Feb 26
5
[PATCH 4/4] ACPI: Enable THERM_CONTROL MSR write for dom0 even cpufreq=xen
Enable THERM_CONTROL MSR write for dom0 even cpufreq=xen Signed-off-by: Wei Gang <gang.wei@intel.com> diff -r bd683e0397b4 xen/arch/x86/traps.c --- a/xen/arch/x86/traps.c Tue Feb 17 22:29:38 2009 +0800 +++ b/xen/arch/x86/traps.c Wed Feb 25 11:23:01 2009 +0800 @@ -2187,10 +2187,17 @@ static int emulate_privileged_op(struct case MSR_IA32_MPERF: case MSR_IA32_APERF:
2007 Oct 17
8
cpufreq support status
Could anyone summarize what the support status of cpu frequency changes is at present. I don''t seem to recall generic changes to the hpyervisor in that respect, but the linux tree has fairly extensive changes to the powernow-k8 driver (which would make sense to me only if all other cpufreq drivers are fully supported now, too). Thanks, Jan
2007 Aug 26
4
HTB doesn''t give me the promised rate: cpufreq?
Hi all :) I''ve been using a tc setup for almost two years, but at some point (probably when I switched to kernel 2.6.x, but I''m not sure) it has started making something very weird. For a certain class, the rate is 125000bit and the ceil is 270000bit, but the fastest rate I get is about 75-80000bit, instead of the "promised" 125000, *with no other traffic in
2008 Oct 29
4
[PATCH] cpufreq.c: shut up compiler about cpufreq_dom
Some versions of GCC are too stupid to figure out that cpufreq_dom is only used if !!domexist and always set in that case, and complain that it may be used uninitialised. (In general it is IMO better to avoid these kind of flag variables; I would prefer structures like for (...) { cpufreq_dom = dom; if (...) goto cpufreq_dom_found; } cpufreq_dom = 0; cpufreq_dom_found: but on
2013 Sep 12
23
More Coverity-reported issues.
Another bundle of issues from Coverity triage. The first one is in x86/mm, and looks scarier than it is. The others are all in xen/drivers and AFAICT are pretty minor. Cheers, Tim.
2009 May 28
5
[PATCH] tools/stubdom: get rid of hardcoded pathes
Hi! Attached patch makes xen-tools and stubdom-dm going independent from hardcoded pathes. It is no possible to install into /usr/local or any other non-default directory and use it out-of-the box. This allows us to have different Xen versions in different directories, simplifies packaging for distributions. It also finds ''hvmloader'' and
2012 Dec 25
7
Using collectd: CPUFreq in dom0
Hello, I''ve tried to get the CPUFreq plugin of collectd running in dom0. But I mentioned that it isn''t so easy to get a file in sysfs on the rigth place. I know that the value has to come from hypervisor and I''ve seen the code in xenpm. The only value I need is "/sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq" which would create cpufreq.c. Can anyone
2013 Jun 20
3
[PATCH V2 1/2] cpufreq, xenpm: fix cpufreq and xenpm mismatch
Currently cpufreq and xenpm are out of sync. Fix cpufreq reporting of if turbo mode is enabled or not. Fix xenpm to not decode for tristate, but a boolean. Signed-off-by: Jacob Shin <jacob.shin@amd.com> --- tools/misc/xenpm.c | 14 +++----------- xen/drivers/cpufreq/utility.c | 2 +- 2 files changed, 4 insertions(+), 12 deletions(-) diff --git a/tools/misc/xenpm.c
2008 Oct 22
24
Problems with enabling hypervisor C and P-state control
Hi, Is there any documentation on enabling hypervisor support for both C and P-state control? On xen-unstable and linux-2.6.18-xen.hg, if I enable cpuidle=1 on the xen command line and then run xenpm, I will get output for C-states (shown below) but it complains that "Xen cpufreq is not enabled!" cpu id : 0 total C-states : 2 idle time(ms) : 73264 C0
2013 Jun 19
8
[PATCH 1/2] cpufreq, powernow: enable/disable core performance boost for all cpus in policy
Currently, enable/disable turbo mode on AMD is broken: $ xenpm enable-turbo-mode 0 <-- works and proper CPU MSR bit is set $ xenpm enable-turbo-mode 1 <-- silently broken, MSR bit not set Since ->turbo is per policy, when user requests to enable/disable turbo mode, we need to set the bit in all of the ->cpus that this policy affects. --- xen/arch/x86/acpi/cpufreq/powernow.c | 2
2009 Mar 28
6
cpu frequency scaling in xen 3.3.1
Hi, i read the xenpm wiki page, but i cannot use the "p-states". xenpm shows: xenpm cpu id : 0 total C-states : 2 idle time(ms) : 1776034 C0 : transition [00000000000000000000] residency [00000000000000000000 ms] C1 : transition [00000000000000260278] residency
2007 Aug 28
8
cpufreq affects rate in, at least, htb
Hi all :) I''ve tested this and having a cpufreq that slows down the CPU affects the rate of HTB. My ondemand cpufreq governor scales down the CPU frequency about 40% and this is more or less the slowdown the rate suffers, 40%. Any known way of dealing with this without having to disable cpufreq? Thanks in advance :) Ra?l N??ez de Arenas Coronado -- Linux Registered
2008 Sep 17
5
c/s 18470
This changeset reverts two previous corrections, for reasons that escape me. First, the domain map is again being confined to NR_CPUS, which I had submitted a patch to fix recently (yes, I realize the code has a TODO in there, but those really get forgotten about far too often). Second, the platform hypercall was reverted back to require all information to be passed to Xen in one chunk, whereas
2008 Sep 26
2
cpufreq and suspend
With my OQO, I get the following message when I try to suspend: cpufreq: suspend failed to assert current frequency is what timing core thinks it is. I see in /var/log/messages: kernel: acpi-cpufreq: CPU0 - ACPI performance management activated There are a number of apps and such dedicated to 'cpufreq' on the system. I have done a bit of searching and have not figured out what to do