From: Wei Liu <wei.liu2@citrix.com>
To: "Hao, Xudong" <xudong.hao@intel.com>
Cc: Xen-devel <xen-devel@lists.xenproject.org>,
Wei Liu <wei.liu2@citrix.com>,
"Zhang, PengtaoX" <pengtaox.zhang@intel.com>,
"Zhang, Haozhong" <haozhong.zhang@intel.com>
Subject: Re: [BUG] xen's LLC, UCNA and MEM testing show error messge"Failed to inject MSR"
Date: Fri, 27 May 2016 11:32:45 +0100 [thread overview]
Message-ID: <20160527103245.GF22076@citrix.com> (raw)
In-Reply-To: <B8376D2DEA074F45BA033984477C453E034A3D4E@shsmsx102.ccr.corp.intel.com>
Hello
Please post patch v2 and see if the patch can be acked and then we might
be able to take it for 4.7.0.
I don't consider this issue a blocker at this point: it's not design
issue, it's not regression. The patch can be backported easily if it
misses 4.7.0.
Wei.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
prev parent reply other threads:[~2016-05-27 10:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-27 5:07 [BUG] xen's LLC, UCNA and MEM testing show error messge"Failed to inject MSR" Zhang, PengtaoX
2016-05-27 5:37 ` Zhang, Haozhong
2016-05-27 5:49 ` Hao, Xudong
2016-05-27 10:32 ` Wei Liu [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=20160527103245.GF22076@citrix.com \
--to=wei.liu2@citrix.com \
--cc=haozhong.zhang@intel.com \
--cc=pengtaox.zhang@intel.com \
--cc=xen-devel@lists.xenproject.org \
--cc=xudong.hao@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 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).