From: Don Zickus <dzickus@redhat.com>
To: Cyrill Gorcunov <gorcunov@openvz.org>
Cc: Ingo Molnar <mingo@elte.hu>, "Huang, Ying" <ying.huang@intel.com>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH -tip 1/2 resend] x86, nmi: Define a name for NMI control port
Date: Wed, 2 Mar 2011 14:35:33 -0500 [thread overview]
Message-ID: <20110302193533.GY11359@redhat.com> (raw)
In-Reply-To: <4D6E630E.1070107@openvz.org>
On Wed, Mar 02, 2011 at 06:32:30PM +0300, Cyrill Gorcunov wrote:
> Also add a comment anout why we need in-out operations.
>
> Signed-off-by: Cyrill Gorcunov <gorcunov@openvz.org>
> ---
>
> Ingo I hope this time I've resolved MUA space injection.
>
> arch/x86/include/asm/mach_traps.h | 18 +++++++++++++-----
> 1 file changed, 13 insertions(+), 5 deletions(-)
>
> Index: linux-2.6.git/arch/x86/include/asm/mach_traps.h
> =====================================================================
> --- linux-2.6.git.orig/arch/x86/include/asm/mach_traps.h
> +++ linux-2.6.git/arch/x86/include/asm/mach_traps.h
> @@ -8,6 +8,7 @@
> #include <asm/mc146818rtc.h>
>
> #define NMI_REASON_PORT 0x61
> +#define NMI_ENABLE_PORT 0x70 /* Real-Time Clock Address Register as well */
>
> #define NMI_REASON_SERR 0x80
> #define NMI_REASON_IOCHK 0x40
> @@ -30,12 +31,19 @@ static inline void reassert_nmi(void)
> old_reg = current_lock_cmos_reg();
> else
> lock_cmos(0); /* register doesn't matter here */
> - outb(0x8f, 0x70);
> - inb(0x71); /* dummy */
I was wondering if 0x71 should get a name change too. Then again I can't
find the Intel doc that tells me what 0x70 is either (I remember seeing it
somewhere).
Cheers,
Don
next prev parent reply other threads:[~2011-03-02 19:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-02 15:32 [PATCH -tip 1/2 resend] x86, nmi: Define a name for NMI control port Cyrill Gorcunov
2011-03-02 18:46 ` [tip:perf/core] " tip-bot for Cyrill Gorcunov
2011-03-02 19:35 ` Don Zickus [this message]
2011-03-02 19:49 ` [PATCH -tip 1/2 resend] " Cyrill Gorcunov
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=20110302193533.GY11359@redhat.com \
--to=dzickus@redhat.com \
--cc=gorcunov@openvz.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=ying.huang@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