From: Heiko Carstens <heiko.carstens@de.ibm.com>
To: Sudeep Holla <Sudeep.Holla@arm.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Martin Schwidefsky <schwidefsky@de.ibm.com>,
"linux390@de.ibm.com" <linux390@de.ibm.com>,
"linux-s390@vger.kernel.org" <linux-s390@vger.kernel.org>
Subject: Re: [PATCH RFC/RFT v2 3/8] s390: move cacheinfo sysfs to generic cacheinfo infrastructure
Date: Mon, 10 Feb 2014 12:59:23 +0100 [thread overview]
Message-ID: <20140210115923.GF19013@osiris> (raw)
In-Reply-To: <52F8B95F.5030401@arm.com>
On Mon, Feb 10, 2014 at 11:34:55AM +0000, Sudeep Holla wrote:
> On 10/02/14 09:50, Heiko Carstens wrote:
> > On Fri, Feb 07, 2014 at 04:49:18PM +0000, Sudeep Holla wrote:
> >> - show_cacheinfo(m);
> >> }
> >> get_online_cpus();
> >> if (cpu_online(n)) {
> >
> > You can't remove that. It's a user space visible change.
> >
> Correct, I wanted to add show_cacheinfo back as its user ABI already, missed it.
>
> Is it ok if I use cpu0 cacheinfo or to be safer as cpu0 can be offline, use
> the cacheinfo of the cpu executing this ?
Any online cpu would do, as the information is completely symmetrical.
next prev parent reply other threads:[~2014-02-10 11:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1391791763-28518-1-git-send-email-sudeep.holla@arm.com>
2014-02-07 16:49 ` [PATCH RFC/RFT v2 3/8] s390: move cacheinfo sysfs to generic cacheinfo infrastructure Sudeep Holla
2014-02-10 9:50 ` Heiko Carstens
2014-02-10 11:34 ` Sudeep Holla
2014-02-10 11:59 ` Heiko Carstens [this message]
2014-02-10 11:30 ` Heiko Carstens
2014-02-10 11:36 ` Sudeep Holla
2014-02-17 18:36 ` Sudeep Holla
2014-02-18 9:45 ` Heiko Carstens
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=20140210115923.GF19013@osiris \
--to=heiko.carstens@de.ibm.com \
--cc=Sudeep.Holla@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=linux390@de.ibm.com \
--cc=schwidefsky@de.ibm.com \
/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;
as well as URLs for NNTP newsgroup(s).