All of lore.kernel.org
 help / color / mirror / Atom feed
From: chris hyser <chris.hyser@oracle.com>
To: sparclinux@vger.kernel.org
Subject: Re: [PATCH v3] sparc64: Setup sysfs to mark LDOM sockets, cores and threads correctly
Date: Fri, 10 Apr 2015 19:55:44 +0000	[thread overview]
Message-ID: <55282AC0.8050802@oracle.com> (raw)
In-Reply-To: <5526cf9b.DFcVpFfcq8CBXHg7%chris.hyser@oracle.com>

On 4/10/2015 3:25 PM, David Miller wrote:
> From: chris hyser <chris.hyser@oracle.com>
> Date: Fri, 10 Apr 2015 11:27:23 -0400
>
>> On 4/9/2015 7:06 PM, David Miller wrote:
>>> How will this work on T3, T2, and T1 which all neither have the
>>> "socket" mdesc nodes nor level 3 caches?
>>
>> The patch only works for sun4v and is only called in that path.
>
> T1, T2, and T3 are sun4v systems.
>
> I can't believe I'm having this conversation with an Oracle engineer.

Your mileage will vary. So you want a generic solution that works on platforms that do not have the key element required 
for this patch? Absent useful machine provided info, I'm guessing it will require some sort of hardcoded table.

-chrish


  parent reply	other threads:[~2015-04-10 19:55 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-09 19:14 [PATCH v3] sparc64: Setup sysfs to mark LDOM sockets, cores and threads correctly chris.hyser
2015-04-09 23:06 ` David Miller
2015-04-10 15:27 ` chris hyser
2015-04-10 19:25 ` David Miller
2015-04-10 19:55 ` chris hyser [this message]
2015-04-11 21:57 ` David Miller
2015-04-16 19:41 ` David Miller
2015-04-16 20:31 ` chris hyser
2015-04-21 18:25 ` chris hyser
2015-04-21 18:33 ` David Miller
2015-04-21 18:39 ` chris hyser
2015-04-21 18:41 ` chris hyser

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=55282AC0.8050802@oracle.com \
    --to=chris.hyser@oracle.com \
    --cc=sparclinux@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.