linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Joel Stanley <joel@jms.id.au>
To: Michael Neuling <mikey@neuling.org>
Cc: kvm@vger.kernel.org, Alexander Graf <agraf@suse.de>,
	kvm-ppc@vger.kernel.org, Paul Mackerras <paulus@samba.org>,
	"Srivatsa S. Bhat" <srivatsa.bhat@linux.vnet.ibm.com>,
	Mahesh Salgaonkar <mahesh@linux.vnet.ibm.com>,
	linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH 6/6] powerpc/powernv: Add support for POWER8 split core on powernv
Date: Thu, 24 Apr 2014 13:32:54 +0930	[thread overview]
Message-ID: <CACPK8Xc6RqXCSR0BvHT=jZbUcWEEYZ50n4r1vQkUyu=NPfpFew@mail.gmail.com> (raw)
In-Reply-To: <1398303165-6576-7-git-send-email-mikey@neuling.org>

Hi Mikey,

On Thu, Apr 24, 2014 at 11:02 AM, Michael Neuling <mikey@neuling.org> wrote:
> +static DEVICE_ATTR(subcores_per_core, 0600,
> +               show_subcores_per_core, store_subcores_per_core);

Can we make this 644, so users can query the state of the system
without being root? This is useful for tools like ppc64_cpu --info.

Cheers,

Joel

  reply	other threads:[~2014-04-24  4:03 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-24  1:32 [PATCH 0/6] Implement split core for POWER8 Michael Neuling
2014-04-24  1:32 ` [PATCH 1/6] KVM: PPC: Book3S HV: Rework the secondary inhibit code Michael Neuling
2014-04-24  1:32 ` [PATCH 2/6] powerpc/powernv: Make it possible to skip the IRQHAPPENED check in power7_nap() Michael Neuling
2014-04-24  1:32 ` [PATCH 3/6] powerpc: Add threads_per_subcore Michael Neuling
2014-04-24  1:32 ` [PATCH 4/6] powerpc: Check cpu_thread_in_subcore() in __cpu_up() Michael Neuling
2014-04-24  1:32 ` [PATCH 5/6] KVM: PPC: Book3S HV: Use threads_per_subcore in KVM Michael Neuling
2014-04-24  1:32 ` [PATCH 6/6] powerpc/powernv: Add support for POWER8 split core on powernv Michael Neuling
2014-04-24  4:02   ` Joel Stanley [this message]
2014-04-24  4:06     ` Michael Neuling
2014-04-30  5:09 ` [PATCH 0/6] Implement split core for POWER8 Michael Neuling
2014-04-30  9:52   ` Alexander Graf

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='CACPK8Xc6RqXCSR0BvHT=jZbUcWEEYZ50n4r1vQkUyu=NPfpFew@mail.gmail.com' \
    --to=joel@jms.id.au \
    --cc=agraf@suse.de \
    --cc=kvm-ppc@vger.kernel.org \
    --cc=kvm@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mahesh@linux.vnet.ibm.com \
    --cc=mikey@neuling.org \
    --cc=paulus@samba.org \
    --cc=srivatsa.bhat@linux.vnet.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).