All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chen Gang <gang.chen@asianux.com>
To: linux-s390@vger.kernel.org
Subject: Re: [PATCH] s390: kernel: remove redundency checking for sysinfo_show() in "sysinfo.c"
Date: Wed, 28 Aug 2013 08:19:20 +0000	[thread overview]
Message-ID: <521DB288.8010700@asianux.com> (raw)
In-Reply-To: <20130828060633.GA4353@osiris>

On 08/28/2013 02:06 PM, Heiko Carstens wrote:
> On Wed, Aug 28, 2013 at 09:55:00AM +0800, Chen Gang wrote:
>> So in my opnion, it will be better to let all level 1 related functions
>> within "if (level >= 1) {...}" code block, that will make code clearer
>> to readers (or some members may doubt about this code).
> 
> I'm not going to apply your patch, otherwise I would have done that already.
> 

OK, I can understand.

Hmm... better to provide some reasons, or I have to 'guess'. ;-)


>> BTW: could you provide more information about why need stsi_15_1_x() be
>> in "level 1" ?
> 
> That's what the architecture says.
> You can download it here: publibfi.boulder.ibm.com/epubs/pdf/dz9zr009.pdf
> 

Firstly, it is a valuable document (at least to me, it is), thanks.


After a quick reference of it, I find the answer below:

  for "level 15":

    "level 15" is "Current-configuration-level information".
    so it should print at any valid level: "level 1, 2, and 3".
    that is just equal to "level 1"

  and for "level 1,2,3"

    "Information about level 1 (the basic machine)"
    "Information about level 2 (a logical partition)"
    "Information about level 3 (a virtual machine)"

  and for "level 4--14"

    "None; codes are reserved"

  and for "level 0":

    "level 0" is for qureying ("Current-configuration-level number")
    so "level 1" also need check level number to support "level 0".


Is it correct ?


:-)

Thanks.
-- 
Chen Gang

           reply	other threads:[~2013-08-28  8:19 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20130828060633.GA4353@osiris>]

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=521DB288.8010700@asianux.com \
    --to=gang.chen@asianux.com \
    --cc=linux-s390@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.