From: Paul Gortmaker <paul.gortmaker@windriver.com>
To: linux-rt-users@vger.kernel.org
Subject: Review comments/questions on preempt-irqs-i386.patch
Date: Tue, 19 Aug 2008 20:04:11 -0400 [thread overview]
Message-ID: <20080820000408.GA28774@windriver.com> (raw)
I'm looking at what is in "preempt-irqs-i386.patch" in the broken out
series for 2.6.26-rt1; and I've spotted something that I think might be
a merge/carry-forward error (not sure). Specifically this chunk:
- if (auto_eoi) /* master does Auto EOI */
- outb_pic(MASTER_ICW4_DEFAULT | PIC_ICW4_AEOI, PIC_MASTER_IMR);
- else /* master expects normal EOI */
- outb_pic(MASTER_ICW4_DEFAULT, PIC_MASTER_IMR);
+ if (!auto_eoi) /* master expects normal EOI */
+ outb_p(MASTER_ICW4_DEFAULT, PIC_MASTER_IMR);
+ else /* master does Auto EOI */
+ outb_p(MASTER_ICW4_DEFAULT | PIC_ICW4_AEOI, PIC_MASTER_IMR);
I'm wondering (a) is the replacement of outb_pic with the more generic
outb_p intentional, or a carry forward artefact, and (b) the outb aside,
I think this change looks like it essentially does:
- if (x)
- x-action();
- else
- not-x-action();
+ if (!x)
+ not-x-action();
+ else
+ x-action();
Is that a fair assesment, or am I missing something?
Thanks,
Paul.
reply other threads:[~2008-08-20 0:12 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20080820000408.GA28774@windriver.com \
--to=paul.gortmaker@windriver.com \
--cc=linux-rt-users@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).