From: Jon Masters <jonathan@jonmasters.org>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: IO-APIC discrepency between x86 subarches
Date: Wed, 05 Dec 2007 03:22:42 -0500 [thread overview]
Message-ID: <1196842962.25930.16.camel@perihelion> (raw)
Yo,
Can someone tell me what the current collective thinking is about
calling io_apic_sync during interrupt masking?
This has changed several times recently, and is different between x86
IA32 and x86_64. As Ingo noted a long while back, it should be fine, but
consistency is a nice thing. With that in mind, I'm thinking that the
shared io_apic files could do with a nice cleanup - one has inlines, the
other has DO_ACTION macros that are wrapped, etc.
Jon.
reply other threads:[~2007-12-05 8:23 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=1196842962.25930.16.camel@perihelion \
--to=jonathan@jonmasters.org \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®