From: Pavel Machek <pavel@suse.cz>
To: Mark Langsdorf <mark.langsdorf@amd.com>, gregkh@ucw.cz
Cc: tglx@linutronix.de, mingo@redhat.com, hpa@zytor.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 01/01] x86: L3 cache index disable for 2.6.26
Date: Sat, 9 Aug 2008 00:00:11 +0200 [thread overview]
Message-ID: <20080808220011.GA12156@ucw.cz> (raw)
In-Reply-To: <200807181603.52332.mark.langsdorf@amd.com>
Hi!
> New versions of AMD processors have support to disable parts
> of their L3 caches if too many MCEs are generated by the
> L3 cache.
>
> This patch provides a /sysfs interface under the cache
> hierarchy to display which caches indices are disabled
> (if any) and to monitoring applications to disable a
> cache index.
...
> +static ssize_t show_cache_disable(struct _cpuid4_info *this_leaf, char *buf)
> +{
> + struct pci_dev *dev;
> + if (this_leaf->can_disable) {
> + int i;
> + ssize_t ret = 0;
> + int node = cpu_to_node(first_cpu(this_leaf->shared_cpu_map));
> + dev = k8_northbridges[node];
> +
> + for (i = 0; i < 2; i++) {
> + unsigned int reg;
> + pci_read_config_dword(dev, 0x1BC + i * 4, ®);
> + ret += sprintf(buf, "%sEntry: %d\n", buf, i);
> + ret += sprintf(buf, "%sReads: %s\tNew Entries: %s\n",
> + buf,
> + reg & 0x80000000 ? "Disabled" : "Allowed",
> + reg & 0x40000000 ? "Disabled" : "Allowed");
> + ret += sprintf(buf, "%sSubCache: %x\tIndex: %x\n", buf,
> + (reg & 0x30000) >> 16, reg & 0xfff);
> +
> + }
> + return ret;
> + }
> + return sprintf(buf, "Feature not enabled\n");
> +}
I think there's one-value-per-file rule in sysfs...
I guess it is better to return -EOPNOTSUP (or something) instead of
english text explaining that...
No, really, what you created is impossible to parse -- /proc like
nightmare.
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2008-08-08 22:13 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-18 21:03 [PATCH 01/01] x86: L3 cache index disable for 2.6.26 Mark Langsdorf
2008-07-21 11:37 ` Ingo Molnar
2008-07-21 12:48 ` Ingo Molnar
2008-07-22 18:06 ` Mark Langsdorf
2008-07-28 14:22 ` Ingo Molnar
2008-07-28 14:49 ` Ingo Molnar
2008-07-28 14:54 ` Langsdorf, Mark
2008-08-08 22:00 ` Pavel Machek [this message]
2008-08-12 16:04 ` [PATCH 01/01][retry 1] " Mark Langsdorf
2008-08-12 21:56 ` Pavel Machek
2008-08-12 22:01 ` Langsdorf, Mark
2008-08-12 22:07 ` Pavel Machek
2008-08-12 22:53 ` Greg KH
2008-08-12 22:12 ` Greg KH
2008-08-13 20:02 ` [PATCH 01/01][retry 2] " Mark Langsdorf
2008-08-13 20:38 ` Pavel Machek
2008-08-13 23:45 ` Greg KH
2008-08-14 13:43 ` [PATCH 01/01][retry 3] " Mark Langsdorf
2008-08-14 13:44 ` Pavel Machek
2008-08-14 14:02 ` Langsdorf, Mark
2008-08-14 15:46 ` Pavel Machek
2008-08-14 16:41 ` Langsdorf, Mark
2008-08-14 14:04 ` Greg KH
2008-08-14 14:23 ` [PATCH 01/01][retry 4] " Mark Langsdorf
2008-08-14 16:48 ` [PATCH 01/01][retry 5] " Mark Langsdorf
2008-08-14 17:10 ` Greg KH
2008-08-14 18:32 ` Mark Langsdorf
2008-08-15 16:42 ` Ingo Molnar
2008-08-15 19:21 ` Langsdorf, Mark
2008-08-15 19:57 ` Ingo Molnar
2008-08-15 20:02 ` Langsdorf, Mark
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=20080808220011.GA12156@ucw.cz \
--to=pavel@suse.cz \
--cc=gregkh@ucw.cz \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.langsdorf@amd.com \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
/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