From: Andrew Morton <akpm@osdl.org>
To: Doug Thompson <norsk5@yahoo.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/6] EDAC PCI device to DEVICE cleanup
Date: Tue, 27 Jun 2006 14:52:25 -0700 [thread overview]
Message-ID: <20060627145225.054b1e63.akpm@osdl.org> (raw)
In-Reply-To: <20060626221558.11917.qmail@web50115.mail.yahoo.com>
Doug Thompson <norsk5@yahoo.com> wrote:
>
> From: Doug Thompson <norsk5@xmission.com>
>
> Change MC drivers from using CVS revision strings for their version number,
> Now each driver has its own local string.
>
> Remove some PCI dependencies from the core EDAC module.
> Made the code 'struct device' centric instead of 'struct pci_dev'
> Most of the code changes here are from a patch by Dave Jiang.
> It may be best to eventually move the PCI-specific code into a separate source file.
>
> ...
>
> --- linux-2.6.17-rc6.orig/drivers/edac/edac_mc.h 2006-06-12 18:17:17.000000000 -0600
> +++ linux-2.6.17-rc6/drivers/edac/edac_mc.h 2006-06-12 18:17:29.000000000 -0600
> @@ -88,6 +88,12 @@
> #define PCI_VEND_DEV(vend, dev) PCI_VENDOR_ID_ ## vend, \
> PCI_DEVICE_ID_ ## vend ## _ ## dev
>
> +#if defined(CONFIG_X86) && defined(CONFIG_PCI)
> +#define dev_name(dev) pci_name(to_pci_dev(dev))
> +#else
> +#define dev_name(dev) to_platform_device(dev)->name
> +#endif
This looks fishy. pci_name() should work OK on non-x86?
> +static void do_pci_parity_check(void)
> +{
> + unsigned long flags;
> + int before_count;
> +
> + debugf3("%s()\n", __func__);
> +
> + if (!check_pci_parity)
> + return;
> +
> + before_count = atomic_read(&pci_parity_count);
> +
> + /* scan all PCI devices looking for a Parity Error on devices and
> + * bridges
> + */
> + local_irq_save(flags);
> + edac_pci_dev_parity_iterator(edac_pci_dev_parity_test);
> + local_irq_restore(flags);
> +
> + /* Only if operator has selected panic on PCI Error */
> + if (panic_on_pci_parity) {
> + /* If the count is different 'after' from 'before' */
> + if (before_count != atomic_read(&pci_parity_count))
> + panic("EDAC: PCI Parity Error");
> + }
> +}
What is the local_irq_save() attempting to do in there? It won't provide
any locking-style coverage on SMP..
next prev parent reply other threads:[~2006-06-27 21:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-26 22:15 Doug Thompson
2006-06-27 21:52 ` Andrew Morton [this message]
2006-06-28 18:02 ` Doug Thompson
-- strict thread matches above, loose matches on Subject: below --
2006-05-24 17:45 Doug Thompson
2006-05-24 23:31 ` Andrew Morton
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=20060627145225.054b1e63.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=norsk5@yahoo.com \
/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
all inboxes | Powered by JetHome®