From: Borislav Petkov <bp@amd64.org>
To: Markus Trippelsdorf <markus@trippelsdorf.de>
Cc: Borislav Petkov <bp@amd64.org>,
"rwhitton@iee.org" <rwhitton@iee.org>,
Clemens Ladisch <clemens@ladisch.de>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Background memory scrubbing
Date: Wed, 20 Apr 2011 19:36:27 +0200 [thread overview]
Message-ID: <20110420173627.GE2734@aftab> (raw)
In-Reply-To: <20110420165533.GA1624@x4.trippels.de>
On Wed, Apr 20, 2011 at 12:55:33PM -0400, Markus Trippelsdorf wrote:
> > > This is KERN_DEBUG since .38 (commit 24f9a7fe3f19f3fd310f556364d01a22911724b3)
> > > and it shouldn't appear on the console if you don't change your default log level.
> >
> > Yes. Sorry, but I was referring to dmesg and not the console.
> > What I mean is that maybe debugf1 or debugf2 is more appropriate than
> > amd64_debug?
>
> In other words:
Ok, that whole debugging output there is partly historical remains and
we don't really need them if we're smart about it. But you'll have to
change your patch and make a proper commit message :).
>
> diff --git a/drivers/edac/amd64_edac.c b/drivers/edac/amd64_edac.c
> index 31e71c4f..13b107e 100644
> --- a/drivers/edac/amd64_edac.c
> +++ b/drivers/edac/amd64_edac.c
> @@ -211,7 +211,7 @@ static int amd64_get_scrub_rate(struct mem_ctl_info *mci)
>
> scrubval = scrubval & 0x001F;
>
> - amd64_debug("pci-read, sdram scrub control value: %d\n", scrubval);
> + debugf1 ("pci-read, sdram scrub control value: %d\n", scrubval);
remove this one completely.
>
> for (i = 0; i < ARRAY_SIZE(scrubrates); i++) {
> if (scrubrates[i].scrubval == scrubval) {
> diff --git a/drivers/edac/edac_mc_sysfs.c b/drivers/edac/edac_mc_sysfs.c
> index 26343fd..8a34aea 100644
> --- a/drivers/edac/edac_mc_sysfs.c
> +++ b/drivers/edac/edac_mc_sysfs.c
> @@ -459,7 +459,7 @@ static ssize_t mci_sdram_scrub_rate_store(struct mem_ctl_info *mci,
>
> new_bw = mci->set_sdram_scrub_rate(mci, bandwidth);
> if (new_bw >= 0) {
> - edac_printk(KERN_DEBUG, EDAC_MC, "Scrub rate set to %d\n", new_bw);
> + debugf1 ("Scrub rate set to %d\n", new_bw);
> return count;
> }
Make here the success case implicit and issue a warning only if we fail
setting the scrub rate:
new_bw = mci->set_sdram_scrub_rate(mci, bandwidth);
if (new_bw < 0) {
edac_printk(KERN_WARNING, EDAC_MC,
"Error setting scrub rate to: %lu\n", bandwidth);
return -EINVAL;
}
and do the same thing with mci_sdram_scrub_rate_show() below.
>
> @@ -483,7 +483,7 @@ static ssize_t mci_sdram_scrub_rate_show(struct mem_ctl_info *mci, char *data)
> return bandwidth;
> }
>
> - edac_printk(KERN_DEBUG, EDAC_MC, "Read scrub rate: %d\n", bandwidth);
> + debugf1 ("Read scrub rate: %d\n", bandwidth);
This one can go too since the success-case is in sysfs anyway.
> return sprintf(data, "%d\n", bandwidth);
> }
Would you like to do that?
Thanks.
--
Regards/Gruss,
Boris.
Advanced Micro Devices GmbH
Einsteinring 24, 85609 Dornach
General Managers: Alberto Bozzo, Andrew Bowd
Registration: Dornach, Gemeinde Aschheim, Landkreis Muenchen
Registergericht Muenchen, HRB Nr. 43632
next prev parent reply other threads:[~2011-04-20 17:36 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-20 14:40 Background memory scrubbing Robert Whitton
2011-04-20 15:19 ` Clemens Ladisch
2011-04-20 15:35 ` Borislav Petkov
2011-04-20 15:46 ` Markus Trippelsdorf
2011-04-20 15:58 ` Borislav Petkov
2011-04-20 16:45 ` Markus Trippelsdorf
2011-04-20 16:55 ` Markus Trippelsdorf
2011-04-20 17:36 ` Borislav Petkov [this message]
2011-04-20 18:28 ` [PATCH] edac: Remove debugging output in scrub rate handling Markus Trippelsdorf
2011-04-21 11:55 ` Borislav Petkov
2011-04-20 19:23 ` Background memory scrubbing Bill Gatliff
-- strict thread matches above, loose matches on Subject: below --
2011-04-20 17:05 Robert Whitton
2011-04-20 17:53 ` Rik van Riel
2011-04-24 20:47 ` Pavel Machek
2011-04-20 15:46 Robert Whitton
2011-04-20 16:01 ` Borislav Petkov
2011-04-20 16:01 ` Borislav Petkov
2011-04-25 16:53 ` Chris Friesen
2011-04-25 16:53 ` Chris Friesen
2011-04-20 7:58 Robert Whitton
2011-04-20 13:30 ` Clemens Ladisch
2011-04-20 16:45 ` Rik van Riel
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=20110420173627.GE2734@aftab \
--to=bp@amd64.org \
--cc=clemens@ladisch.de \
--cc=linux-kernel@vger.kernel.org \
--cc=markus@trippelsdorf.de \
--cc=rwhitton@iee.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.