MIME-Version: 1.0
In-Reply-To: <alpine.DEB.2.20.1703132008440.3712@nanos>
References: <1488908964-30261-1-git-send-email-vikas.shivappa@linux.intel.com>
 <alpine.DEB.2.20.1703072011080.4299@nanos> <3908561D78D1C84285E8C5FCA982C28F6120F0A9@ORSMSX113.amr.corp.intel.com>
 <CABPqkBQaOt3_0EN+6D8sJ4erA6dFW-P7ECCgdWu6UxFaaJ-eyg@mail.gmail.com>
 <alpine.DEB.2.20.1703080927260.3521@nanos> <CALcN6mgs=_wkav=reLsYOQW1N9Na=x9xKmM5GWvh4=0n_XD3Ng@mail.gmail.com>
 <alpine.DEB.2.20.1703091145070.3521@nanos> <CALcN6mjpuiy1mMn2KG33ororsf7e68AZYTmSjtpD9b-pitsY1g@mail.gmail.com>
 <alpine.DEB.2.20.1703101523230.3681@nanos> <CALcN6miebWcuLYcA19CN88bJ1pT8zRksFm-f3KFvQcemkqJa8Q@mail.gmail.com>
 <alpine.DEB.2.20.1703132008440.3712@nanos>
From: David Carrillo-Cisneros <davidcc@google.com>
Date: Mon, 13 Mar 2017 12:58:24 -0700
Message-ID: <CALcN6mi46MGiufWECbWCVkdPgxWr0MGKq0uoBWpfH-JZzf9=SA@mail.gmail.com>
Subject: Re: [PATCH 1/1] x86/cqm: Cqm requirements
To: Thomas Gleixner <tglx@linutronix.de>
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>
Content-Type: text/plain; charset=UTF-8
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 218
Lines: 7

>> 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.