All of
 help / color / mirror / Atom feed
From: tip-bot for Cesar Eduardo Barros <>
Subject: [tip:x86/vdso] x86-64, doc: Remove int 0xcc from entry_64.S documentation
Date: Tue, 16 Aug 2011 06:22:34 GMT	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Commit-ID:  6cd2f4a4248891cb09954b7675c1c846c3c90dc0
Author:     Cesar Eduardo Barros <>
AuthorDate: Mon, 15 Aug 2011 19:26:50 -0300
Committer:  H. Peter Anvin <>
CommitDate: Mon, 15 Aug 2011 22:53:28 -0700

x86-64, doc: Remove int 0xcc from entry_64.S documentation

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.

Signed-off-by: Cesar Eduardo Barros <>
Acked-by: Andy Lutomirski <luto@MIT.EDU>
Signed-off-by: H. Peter Anvin <>
 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.

  parent reply	other threads:[~2011-08-16  6:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-15 22:26 [PATCH] x86-64: remove int 0xcc from entry_64.S documentation Cesar Eduardo Barros
2011-08-15 22:32 ` Andrew Lutomirski
2011-08-16  6:22 ` tip-bot for Cesar Eduardo Barros [this message]
2011-08-16 15:29 ` [tip:x86/vdso] x86-64, doc: Remove " 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \
    --cc=luto@MIT.EDU \ \ \

* 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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.