From: Keir Fraser <keir@xensource.com>
To: "Zhao, Yunfeng" <yunfeng.zhao@intel.com>, xen-devel@lists.xensource.com
Subject: Re: vmx status report against cset 14912 - 1 fixed issue, 4 old issues
Date: Wed, 25 Apr 2007 10:34:15 +0100 [thread overview]
Message-ID: <C254DF27.DCE2%keir@xensource.com> (raw)
In-Reply-To: <10EA09EFD8728347A513008B6B0DA77AA3EE2C@pdsmsx411.ccr.corp.intel.com>
On 25/4/07 10:27, "Zhao, Yunfeng" <yunfeng.zhao@intel.com> wrote:
>> To be clear: this is an unmodified RHEL4 release kernel, with *latest*
> PV
>> drivers from -unstable? Any idea if this issue is specific to the RHEL4
>> kernel, or can you reproduce with other kernels? Does it very
> definitely
>> seem to be specific to multiprocessor guests?
> [Yunfeng] The guest was booted with a 2.16.16 smp kernel which we built
> for PV test. It only happens on SMP HVM linux guest.I also saw the same
> issue on some SLES SMP HVM guests with SLES release kernel and PV
> drivers.
It would be interesting to see what happens if the platform-pci interrupt is
pinned strictly to vcpu0. So, what happens if you boot the guest with
'acpi=0'? Or, what about if you kill any irqbalance programs that are
running after boot, then 'cat /proc/interrupts' to find the xen-platform-pci
interrupt number (x) and then 'echo 1 >/proc/irq/<x>/smp_affinity'?
I couldn't repro just with SpecJBB but it's quite possible the kernel build
is really required to repro. Specjbb itself does very little I/O.
-- Keir
next prev parent reply other threads:[~2007-04-25 9:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <823A93EED437D048963A3697DB0E35DE2A1EEB@pdsmsx414.ccr.corp.intel.com>
2007-04-25 8:51 ` vmx status report against cset 14912 - 1 fixed issue, 4 old issues Zhao, Yunfeng
2007-04-25 8:56 ` Keir Fraser
2007-04-25 9:27 ` Zhao, Yunfeng
2007-04-25 9:34 ` Keir Fraser [this message]
2007-04-25 9:44 ` Zhao, Yunfeng
2007-04-25 11:09 ` vmx status report against cset 14912 - 1 fixedissue, " You, Yongkang
2007-04-25 11:27 ` Keir Fraser
2007-04-25 15:19 ` You, Yongkang
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=C254DF27.DCE2%keir@xensource.com \
--to=keir@xensource.com \
--cc=xen-devel@lists.xensource.com \
--cc=yunfeng.zhao@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.