From: Olaf Hering <olaf@aepfle.de>
To: Wei Liu <wei.liu2@citrix.com>
Cc: keir@xen.org, ian.campbell@citrix.com,
He Chen <he.chen@linux.intel.com>,
andrew.cooper3@citrix.com, stefano.stabellini@eu.citrix.com,
ian.jackson@eu.citrix.com, jbeulich@suse.com,
xen-devel@lists.xenproject.org, chao.p.peng@linux.intel.com
Subject: Re: [PATCH v7 2/3] x86: add domctl cmd to set/get CDP code/data CBM
Date: Fri, 16 Oct 2015 11:10:55 +0200 [thread overview]
Message-ID: <20151016091055.GA19291@aepfle.de> (raw)
In-Reply-To: <20151015152647.GF32638@zion.uk.xensource.com>
On Thu, Oct 15, Wei Liu wrote:
> No, because 1) staging is not using GCC5, 2) staging has debug=y.
Are there enough resources to address #2?
Build once with debug=y and once without?
Olaf
next prev parent reply other threads:[~2015-10-16 9:11 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-13 8:53 [PATCH v7 0/3] detect and initialize CDP (Code/Data Prioritization) feature He Chen
2015-10-13 8:53 ` [PATCH v7 1/3] x86: Support enable CDP by boot parameter and add get CDP status He Chen
2015-10-14 2:02 ` Chao Peng
2015-10-13 8:53 ` [PATCH v7 2/3] x86: add domctl cmd to set/get CDP code/data CBM He Chen
2015-10-13 15:38 ` Jan Beulich
2015-10-14 2:07 ` Chao Peng
2015-10-15 14:57 ` Olaf Hering
2015-10-15 15:10 ` Wei Liu
2015-10-15 15:22 ` Olaf Hering
2015-10-15 15:26 ` Wei Liu
2015-10-15 15:30 ` Wei Liu
2015-10-16 9:10 ` Olaf Hering [this message]
2015-10-15 15:47 ` Jan Beulich
2015-10-16 8:24 ` He Chen
2015-10-16 8:32 ` Jan Beulich
2015-10-13 8:53 ` [PATCH v7 3/3] tools & docs: add tools and docs support for Intel CDP He Chen
2015-10-13 16:23 ` Ian Campbell
2015-10-14 2:38 ` Chao Peng
2015-10-14 8:52 ` Ian Campbell
2015-10-14 9:08 ` Dario Faggioli
2015-10-14 9:20 ` Ian Campbell
2015-10-14 10:52 ` Jan Beulich
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=20151016091055.GA19291@aepfle.de \
--to=olaf@aepfle.de \
--cc=andrew.cooper3@citrix.com \
--cc=chao.p.peng@linux.intel.com \
--cc=he.chen@linux.intel.com \
--cc=ian.campbell@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=jbeulich@suse.com \
--cc=keir@xen.org \
--cc=stefano.stabellini@eu.citrix.com \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xenproject.org \
/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.