From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Keir Fraser <keir.fraser@eu.citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
"He, Qing" <qing.he@intel.com>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
Ian Jackson <Ian.Jackson@eu.citrix.com>,
"Cinco, Dante" <Dante.Cinco@lsi.com>,
"Zhang, Xiantao" <xiantao.zhang@intel.com>
Subject: Re: IRQ SMP affinity problems in domU with vcpus > 4 on HP ProLiant G6 with dual Xeon 5540 (Nehalem)
Date: Thu, 22 Oct 2009 14:11:34 -0700 [thread overview]
Message-ID: <4AE0CA86.8060601@goop.org> (raw)
In-Reply-To: <C705B951.18207%keir.fraser@eu.citrix.com>
On 10/21/09 23:25, Keir Fraser wrote:
> In general, having qemu make pci updates via the cf8/cfc method is clearly
> unsafe, and cannot be made safe. I would certainly be happy to see some of
> the low-level PCI management pushed into pciback (and/or pci-stub, depending
> on whether pciback is to be ported to pv_ops).
>
I've got Konrad's forward-port of pciback in xen/master at the moment.
J
next prev parent reply other threads:[~2009-10-22 21:11 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-16 1:38 IRQ SMP affinity problems in domU with vcpus > 4 on HP ProLiant G6 with dual Xeon 5540 (Nehalem) Cinco, Dante
2009-10-16 2:34 ` Qing He
2009-10-16 6:37 ` Keir Fraser
2009-10-16 7:32 ` Zhang, Xiantao
2009-10-16 8:24 ` Qing He
2009-10-16 8:22 ` Zhang, Xiantao
2009-10-16 8:34 ` Qing He
2009-10-16 8:35 ` Zhang, Xiantao
2009-10-16 9:01 ` Qing He
2009-10-16 9:42 ` Qing He
2009-10-16 9:49 ` Zhang, Xiantao
2009-10-16 14:54 ` Zhang, Xiantao
2009-10-16 18:24 ` Cinco, Dante
2009-10-17 0:59 ` Zhang, Xiantao
2009-10-20 0:19 ` Cinco, Dante
2009-10-20 5:46 ` Zhang, Xiantao
2009-10-20 7:51 ` Zhang, Xiantao
2009-10-20 17:26 ` Cinco, Dante
2009-10-21 1:10 ` Zhang, Xiantao
2009-10-22 1:00 ` Cinco, Dante
2009-10-22 1:58 ` Zhang, Xiantao
2009-10-22 2:42 ` Zhang, Xiantao
2009-10-22 6:25 ` Keir Fraser
2009-10-22 21:11 ` Jeremy Fitzhardinge [this message]
2009-10-22 5:10 ` Qing He
2009-10-23 0:10 ` Cinco, Dante
2009-10-22 6:46 ` Jan Beulich
2009-10-22 7:11 ` Zhang, Xiantao
2009-10-22 7:31 ` Jan Beulich
2009-10-22 8:41 ` Zhang, Xiantao
2009-10-22 9:42 ` Keir Fraser
2009-10-22 16:32 ` Zhang, Xiantao
2009-10-22 16:33 ` Cinco, Dante
2009-10-23 1:06 ` Zhang, Xiantao
2009-10-26 13:02 ` Zhang, Xiantao
2009-10-26 13:34 ` Keir Fraser
2009-10-16 9:41 ` Keir Fraser
2009-10-16 9:57 ` Qing He
2009-10-16 9:58 ` Zhang, Xiantao
2009-10-16 10:21 ` Jan Beulich
-- strict thread matches above, loose matches on Subject: below --
2009-10-08 0:08 Cinco, Dante
2009-10-08 16:07 ` Bruce Edge
2009-10-08 18:05 ` Keir Fraser
2009-10-08 18:11 ` Cinco, Dante
2009-10-08 21:35 ` Keir Fraser
2009-10-09 9:07 ` Qing He
2009-10-09 15:59 ` Cinco, Dante
2009-10-09 23:39 ` Cinco, Dante
2009-10-10 9:43 ` Qing He
2009-10-10 10:10 ` Keir Fraser
2009-10-12 5:25 ` Cinco, Dante
2009-10-12 5:54 ` Qing He
2009-10-14 19:54 ` Cinco, Dante
2009-10-16 0:09 ` Konrad Rzeszutek Wilk
2009-10-16 1:40 ` Konrad Rzeszutek Wilk
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=4AE0CA86.8060601@goop.org \
--to=jeremy@goop.org \
--cc=Dante.Cinco@lsi.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=keir.fraser@eu.citrix.com \
--cc=konrad.wilk@oracle.com \
--cc=qing.he@intel.com \
--cc=xen-devel@lists.xensource.com \
--cc=xiantao.zhang@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.