linux-kernel - Re: [PATCH v5 00/11] drivers: cacheinfo support

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Fri, 7 Nov 2014 11:45:51 -0800
From:	Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To:	Sudeep Holla <sudeep.holla@....com>
Cc:	LKML <linux-kernel@...r.kernel.org>,
	Heiko Carstens <heiko.carstens@...ibm.com>,
	Lorenzo Pieralisi <Lorenzo.Pieralisi@....com>
Subject: Re: [PATCH v5 00/11] drivers: cacheinfo support

On Fri, Nov 07, 2014 at 07:40:51PM +0000, Sudeep Holla wrote:
> 
> 
> On 07/11/14 19:23, Greg Kroah-Hartman wrote:
> >On Tue, Oct 21, 2014 at 10:26:05AM +0100, Sudeep Holla wrote:
> >>Hi Greg,
> >>
> >>On 20/10/14 19:49, Greg Kroah-Hartman wrote:
> >>>On Mon, Oct 20, 2014 at 07:46:19PM +0100, Sudeep Holla wrote:
> >>>>Hi Greg,
> >>>>
> >>>>On 30/09/14 14:48, Sudeep Holla wrote:
> >>>>>This series adds a generic cacheinfo support similar to topology. The
> >>>>>implementation is based on x86 cacheinfo support. Currently x86, powerpc,
> >>>>>ia64 and s390 have their own implementations. While adding similar support
> >>>>>to ARM and ARM64, here is the attempt to make it generic quite similar to
> >>>>>topology info support. It also adds the missing ABI documentation for
> >>>>>the cacheinfo sysfs which is already being used.
> >>>>>
> >>>>>It moves all the existing different implementations on x86, ia64, powerpc
> >>>>>and s390 to use the generic cacheinfo infrastructure introduced here.
> >>>>>These changes on non-ARM platforms are only compile tested and tested on x86.
> >>>>>
> >>>>>This series also adds support for ARM and ARM64 architectures based on
> >>>>>the generic support.
> >>>>>
> >>>>>The code can be fetched from:
> >>>>>  git://linux-arm.org/linux-skn cacheinfo
> >>>>>
> >>>>
> >>>>I am hoping to target this for v3.19 if possible, it would be good if
> >>>>you can review and provide feedback.
> >>>
> >>>3.18-rc1 just came out a few _hours_ ago, and now we can start worrying
> >>>about what goes into 3.19.  I have 1257 emails in my "to-review" queue
> >>>for 3.19, please give me a chance to catch up in a few weeks to get to
> >>>this code.
> >>>
> >>
> >>I completely understand and I am sorry if that was a noise.
> >>I just wanted to ensure it's not lost, thanks for letting me know it's
> >>in your list.
> >
> >Do you want me to take this through my tree?  If so, I will, otherwise,
> >feel free to add:
> 
> I have not got it tested on AMD, IA64 and PPC. Probably they were
> waiting for the core driver to settle down. I have only tested on
> ARM{32,64} and x86. Heiko Carstens tested on s390 long back some
> previous version.
> 
> If it fine with you, I would like to break the first 4 patches and
> target it for v3.19, and take up the arch-specific patches (i.e.5-11)
> after that, so that I can get them tested on all architectures.
> 
> >
> >Acked-by: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
> >
> >to the series.
> 
> Thanks, I will rebase on v3.18-rc4 and repost first 4 patches  on Monday
> which you can take it through your tree *iff you agree with me* on above
> flow.

I've just taken the first 4 patches in my tree now, no need to repost
them.  Let's see what breaks with them :)

thanks,

greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/