Date: Thu, 3 Dec 2015 22:58:39 +0100
From: Pavel Machek <pavel@ucw.cz>
To: Marcelo Tosatti <mtosatti@redhat.com>
Cc: Luiz Capitulino <lcapitulino@redhat.com>,
        Peter Zijlstra <peterz@infradead.org>,
        Thomas Gleixner <tglx@linutronix.de>,
        Vikas Shivappa <vikas.shivappa@intel.com>, Tejun Heo <tj@kernel.org>,
        Yu Fenghua <fenghua.yu@intel.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH RFC] ioctl based CAT interface
Message-ID: <20151203215839.GD14427@amd>
References: <20151113163933.GA10222@amt.cnet>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20151113163933.GA10222@amt.cnet>
User-Agent: Mutt/1.5.23 (2014-03-12)
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1309
Lines: 37

Hi!
> 
> Attached is an early version of the ioctl based CAT interface we
> have been working on.
> 
> NOTE: it does not compile, there is no locking, but should 
> be sufficient for interested people to comment.
> 
> 
> diff --git a/arch/x86/Kconfig b/arch/x86/Kconfig
> index db3622f..293726b 100644
> --- a/arch/x86/Kconfig
> +++ b/arch/x86/Kconfig
> @@ -757,6 +757,14 @@ config HPET_EMULATE_RTC
>  	def_bool y
>  	depends on HPET_TIMER && (RTC=y || RTC=m || RTC_DRV_CMOS=m || RTC_DRV_CMOS=y)
>  
> +config CACHE_RESERVATION
> +	tristate "Cache Reservation Support"
> +	default n
> +	---help---
> +	  This feature makes use of Intel's Cache Allocation Technology to allow the
> +	  reservation of portions of the L3 cache to specific tasks. Please, see
> +	  Documentation/x86/cache-reservation.txt for more

Including the Documentation/x86/cache-reservation.txt file in the
patch would be nice ;-).
									Pavel
									
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/