From: Thomas Gleixner <tglx@linutronix.de>
To: David Carrillo-Cisneros <davidcc@google.com>
Cc: Stephane Eranian <eranian@google.com>,
"Luck, Tony" <tony.luck@intel.com>,
Vikas Shivappa <vikas.shivappa@linux.intel.com>,
"Shivappa, Vikas" <vikas.shivappa@intel.com>,
"x86@kernel.org" <x86@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"hpa@zytor.com" <hpa@zytor.com>,
"mingo@kernel.org" <mingo@kernel.org>,
"peterz@infradead.org" <peterz@infradead.org>,
"Shankar, Ravi V" <ravi.v.shankar@intel.com>,
"Yu, Fenghua" <fenghua.yu@intel.com>,
"Kleen, Andi" <andi.kleen@intel.com>
Subject: Re: [PATCH 1/1] x86/cqm: Cqm requirements
Date: Mon, 13 Mar 2017 21:21:19 +0100 (CET) [thread overview]
Message-ID: <alpine.DEB.2.20.1703132121080.3712@nanos> (raw)
In-Reply-To: <CALcN6mi46MGiufWECbWCVkdPgxWr0MGKq0uoBWpfH-JZzf9=SA@mail.gmail.com>
On Mon, 13 Mar 2017, David Carrillo-Cisneros wrote:
> >> I am ok removing the perf-like CPU filtering from the requirements.
> >
> > So if I'm not missing something then ALL remaining requirements can be
> > solved with the RDT integrated monitoring mechanics, right?
> >
>
> Right.
Excellent.
prev parent reply other threads:[~2017-03-13 20:21 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-07 17:49 Vikas Shivappa
2017-03-07 19:31 ` Thomas Gleixner
2017-03-07 20:04 ` Luck, Tony
2017-03-07 20:22 ` Thomas Gleixner
2017-03-07 23:29 ` Stephane Eranian
2017-03-07 23:31 ` Shivappa Vikas
2017-03-08 8:30 ` Thomas Gleixner
2017-03-08 17:58 ` David Carrillo-Cisneros
2017-03-09 11:01 ` Thomas Gleixner
2017-03-09 18:05 ` David Carrillo-Cisneros
2017-03-10 14:53 ` Thomas Gleixner
2017-03-11 1:53 ` David Carrillo-Cisneros
2017-03-13 19:10 ` Thomas Gleixner
2017-03-13 19:58 ` David Carrillo-Cisneros
2017-03-13 20:21 ` Thomas Gleixner [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=alpine.DEB.2.20.1703132121080.3712@nanos \
--to=tglx@linutronix.de \
--cc=andi.kleen@intel.com \
--cc=davidcc@google.com \
--cc=eranian@google.com \
--cc=fenghua.yu@intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=ravi.v.shankar@intel.com \
--cc=tony.luck@intel.com \
--cc=vikas.shivappa@intel.com \
--cc=vikas.shivappa@linux.intel.com \
--cc=x86@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®