From: Thomas Gleixner <tglx@linutronix.de>
To: Ben Hutchings <bhutchings@solarflare.com>
Cc: Peter P Waskiewicz Jr <peter.p.waskiewicz.jr@intel.com>,
davem@davemloft.net, arjan@linux.jf.intel.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH linux-next v3 1/2] irq: Add CPU mask affinity hint
Date: Fri, 30 Apr 2010 23:17:25 +0200 (CEST) [thread overview]
Message-ID: <alpine.LFD.2.00.1004302311550.2951@localhost.localdomain> (raw)
In-Reply-To: <1272661345.2110.28.camel@achroite.uk.solarflarecom.com>
On Fri, 30 Apr 2010, Ben Hutchings wrote:
> On Fri, 2010-04-30 at 13:23 -0700, Peter P Waskiewicz Jr wrote:
> > +int irq_register_affinity_hint(unsigned int irq, const struct cpumask *m)
> > +{
> > + struct irq_desc *desc = irq_to_desc(irq);
> > + unsigned long flags;
> > +
> > + if (!desc)
> > + return -EINVAL;
>
> Is it possible for irq_to_desc(irq) to be NULL? This function already
> assumes that the caller 'owns' the IRQ.
Oh come on. Driver writers get everything wrong and not checking on an
invalid irq number is better than crashing :)
> > +static int irq_affinity_hint_proc_show(struct seq_file *m, void *v)
> > +{
> > + struct irq_desc *desc = irq_to_desc((long)m->private);
> > + unsigned long flags;
> > + cpumask_var_t mask;
> > + int ret = -EINVAL;
>
> I don't think this should be returning -EINVAL if the affinity hint is
> missing. That means 'invalid argument', but there is nothing invalid
> about trying to read() the corresponding file. The file should simply
> be empty if there is no hint. (Actually it might be better if it didn't
> appear at all, but that would be a pain to implement.)
I agree that -EINVAL is not really a good match.
How about just returning CPU_MASK_ALL if desc->affinity_hint is not
set ?
Thanks,
tglx
next prev parent reply other threads:[~2010-04-30 21:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-30 20:23 [PATCH linux-next v3 1/2] irq: Add CPU mask affinity hint Peter P Waskiewicz Jr
2010-04-30 20:24 ` Thomas Gleixner
2010-04-30 20:30 ` Peter P Waskiewicz Jr
2010-04-30 20:24 ` [PATCH linux-next v3 2/2] ixgbe: Example usage of the new IRQ affinity_hint callback Peter P Waskiewicz Jr
2010-04-30 21:02 ` [PATCH linux-next v3 1/2] irq: Add CPU mask affinity hint Ben Hutchings
2010-04-30 21:17 ` Thomas Gleixner [this message]
2010-04-30 21:18 ` Peter P Waskiewicz Jr
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=alpine.LFD.2.00.1004302311550.2951@localhost.localdomain \
--to=tglx@linutronix.de \
--cc=arjan@linux.jf.intel.com \
--cc=bhutchings@solarflare.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=peter.p.waskiewicz.jr@intel.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