public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Russ Anderson <rja@sgi.com>
To: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
Cc: linux-kernel@vger.kernel.org, linux-ia64@vger.kernel.org,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Tony Luck <tony.luck@intel.com>,
	Christoph Lameter <clameter@sgi.com>
Subject: Re: [PATCH 3/3] ia64: Call migration code on correctable errors v6
Date: Wed, 25 Jun 2008 17:25:53 -0500	[thread overview]
Message-ID: <20080625222553.GA29402@sgi.com> (raw)
In-Reply-To: <20080623121721.37CA.KOSAKI.MOTOHIRO@jp.fujitsu.com>

On Mon, Jun 23, 2008 at 12:25:40PM +0900, KOSAKI Motohiro wrote:
> Hi
> 
> > +static ssize_t
> > +badpage_show(struct kobject *kobj,
> > +	     struct kobj_attribute *attr, char *buf)
> > +
> > +{
> > +	struct page *page, *page2;
> > +	int i = 0, cnt = 0;
> > +	char *bufend = buf + PAGE_SIZE;
> > +
> > +	cnt = snprintf(buf, bufend - (buf + cnt),
> > +			"Bad RAM: %d kB, %d pages marked bad\n"
> > +			"List of bad physical pages\n",
> > +			total_badpages << (PAGE_SHIFT - 10), total_badpages);
> > +
> > +	list_for_each_entry_safe(page, page2, &badpagelist, lru) {
> > +		if (bufend - (buf + cnt) < 20)
> > +			break;		/* Avoid overflowing the buffer */
> > +		cnt += snprintf(buf + cnt, bufend - (buf + cnt),
> > +				" 0x%011lx", page_to_phys(page));
> > +		if (!(++i % 5))
> > +			cnt += snprintf(buf + cnt, bufend - (buf + cnt), "\n");
> > +	}
> > +	cnt += snprintf(buf + cnt, bufend - (buf + cnt), "\n");
> > +
> > +	return cnt;
> > +}
> 
> it seems /proc/meminfo is better.
> because badpage is architecture independent concept.
> 
> nonsense?

The original patch used /proc/ (/proc/meminfo had badpage summary info
and /proc/badram had detailed info.  It was suggested that /sys was
a better place.

FWIW, I'm more than happy to put it anywhere deemed "best" by
the community.  It is currently /sys/kernel/badram.

Thanks,
-- 
Russ Anderson, OS RAS/Partitioning Project Lead  
SGI - Silicon Graphics Inc          rja@sgi.com

      reply	other threads:[~2008-06-25 22:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-09 16:20 [PATCH 3/3] ia64: Call migration code on correctable errors v6 Russ Anderson
2008-06-23  3:25 ` KOSAKI Motohiro
2008-06-25 22:25   ` Russ Anderson [this message]

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=20080625222553.GA29402@sgi.com \
    --to=rja@sgi.com \
    --cc=akpm@linux-foundation.org \
    --cc=clameter@sgi.com \
    --cc=kosaki.motohiro@jp.fujitsu.com \
    --cc=linux-ia64@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tony.luck@intel.com \
    --cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox