From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: George@acsinet12.oracle.com, Keir Fraser <keir@xen.org>,
Dunlap <George.Dunlap@eu.citrix.com>,
Wei Huang2 <Wei.Huang2@amd.com>, Jacob Shin <Jacob.Shin@amd.com>,
Wei Wang2 <wei.wang2@amd.com>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: Backport per-device vector map patches to xen 4.1.3
Date: Thu, 17 Nov 2011 12:05:14 -0500 [thread overview]
Message-ID: <20111117170514.GA3017@phenom.dumpdata.com> (raw)
In-Reply-To: <4EC549280200007800061AC5@nat28.tlf.novell.com>
On Thu, Nov 17, 2011 at 04:49:28PM +0000, Jan Beulich wrote:
> >>> On 17.11.11 at 17:02, Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> wrote:
> > On Thu, Oct 27, 2011 at 04:07:51PM +0200, Wei Wang2 wrote:
> >> Recently we found an issue in xen 4.1. Under heavy I/O stress such as
> > running
> >> bonnie++, Dom0 would lost its hard disk with lots of I/O errors. We found
> >> that some PCI-E devices was using the same vector as SMBus on AMD platforms
> >> and George' patch set that enables per-device vector map can fix this
> >> problem.
> >>
> >> Following patches have been back ported and tested by Jacob and Wei H.
> >> Please apply them to Xen 4.1.3
> >
> > Can they be applied please? I've been running these without hiccups for
> > well,
> > since they were posted. On both AMD and Intel boxes.
> >
> > So, Tested-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
>
> Thanks to Keir, they're already in - c/s 23177:9a38e30e5459.
Oh, they are. Hmm, somehow when I looked at xenbits.xen.org I couldn't find them.
Now I see them :-)
prev parent reply other threads:[~2011-11-17 17:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-27 14:07 Backport per-device vector map patches to xen 4.1.3 Wei Wang2
2011-11-17 16:02 ` Konrad Rzeszutek Wilk
2011-11-17 16:49 ` Jan Beulich
2011-11-17 17:05 ` Konrad Rzeszutek Wilk [this message]
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=20111117170514.GA3017@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=George@acsinet12.oracle.com \
--cc=JBeulich@suse.com \
--cc=Jacob.Shin@amd.com \
--cc=Wei.Huang2@amd.com \
--cc=keir@xen.org \
--cc=wei.wang2@amd.com \
--cc=xen-devel@lists.xensource.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).