From: Cesar Eduardo Barros <cesarb@cesarb.net>
To: linux-kernel@vger.kernel.org
Cc: linux-doc@vger.kernel.org, Randy Dunlap <rdunlap@xenotime.net>,
x86@kernel.org, Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
Cesar Eduardo Barros <cesarb@cesarb.net>,
Andy Lutomirski <luto@MIT.EDU>, Ingo Molnar <mingo@elte.hu>
Subject: [PATCH] x86-64: remove int 0xcc from entry_64.S documentation
Date: Mon, 15 Aug 2011 19:26:50 -0300 [thread overview]
Message-ID: <1313447210-9149-1-git-send-email-cesarb@cesarb.net> (raw)
Commit 3ae36655b97a03fa1decf72f04078ef945647c1a (x86-64: Rework vsyscall
emulation and add vsyscall= parameter) removed the special use of the
0xcc IDT vector.
Remove it from Documentation/x86/entry_64.txt also.
Cc: Andy Lutomirski <luto@MIT.EDU>
Cc: Ingo Molnar <mingo@elte.hu>
Signed-off-by: Cesar Eduardo Barros <cesarb@cesarb.net>
---
Documentation/x86/entry_64.txt | 3 ---
1 files changed, 0 insertions(+), 3 deletions(-)
diff --git a/Documentation/x86/entry_64.txt b/Documentation/x86/entry_64.txt
index 7869f14..bc7226e 100644
--- a/Documentation/x86/entry_64.txt
+++ b/Documentation/x86/entry_64.txt
@@ -27,9 +27,6 @@ Some of these entries are:
magically-generated functions that make their way to do_IRQ with
the interrupt number as a parameter.
- - emulate_vsyscall: int 0xcc, a special non-ABI entry used by
- vsyscall emulation.
-
- APIC interrupts: Various special-purpose interrupts for things
like TLB shootdown.
--
1.7.4.4
next reply other threads:[~2011-08-15 22:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-15 22:26 Cesar Eduardo Barros [this message]
2011-08-15 22:32 ` [PATCH] x86-64: remove int 0xcc from entry_64.S documentation Andrew Lutomirski
2011-08-16 6:22 ` [tip:x86/vdso] x86-64, doc: Remove " tip-bot for Cesar Eduardo Barros
2011-08-16 15:29 ` tip-bot for Cesar Eduardo Barros
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=1313447210-9149-1-git-send-email-cesarb@cesarb.net \
--to=cesarb@cesarb.net \
--cc=hpa@zytor.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@MIT.EDU \
--cc=mingo@elte.hu \
--cc=mingo@redhat.com \
--cc=rdunlap@xenotime.net \
--cc=tglx@linutronix.de \
--cc=x86@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).