From: "H. Peter Anvin" <hpa@zytor.com>
To: Andy Lutomirski <luto@mit.edu>
Cc: x86@kernel.org, Andi Kleen <andi@firstfloor.org>,
linux-kernel@vger.kernel.org, torvalds@linux-foundation.org,
lueckintel@yahoo.com, kimwooyoung@gmail.com,
Ingo Molnar <mingo@elte.hu>, Borislav Petkov <bp@alien8.de>,
Suresh Siddha <suresh.b.siddha@intel.com>
Subject: Re: [PATCH 1/4] x86-64: Allow emulated vsyscalls from user addresses
Date: Tue, 09 Aug 2011 13:59:20 -0500 [thread overview]
Message-ID: <4E418388.9050600@zytor.com> (raw)
In-Reply-To: <135b827ce7b4e6059f11de631ea4a455e2b433be.1312899174.git.luto@mit.edu>
On 08/09/2011 09:27 AM, Andy Lutomirski wrote:
> *
> * Vectors 0 ... 31 : system traps and exceptions - hardcoded events
> - * Vectors 32 ... 127 : device interrupts
> - * Vector 128 : legacy int80 syscall interface
> - * Vector 204 : legacy x86_64 vsyscall emulation
> - * Vectors 129 ... INVALIDATE_TLB_VECTOR_START-1 except 204 : device interrupts
> + * Vectors 32 ... INVALIDATE_TLB_VECTOR_START-1 : device interrupts, except:
> + * Vectors 64 ... 66 : legacy x86_64 vsyscall emulation
> + * Vector 128 : legacy int80 syscall interface
> * Vectors INVALIDATE_TLB_VECTOR_START ... 255 : special interrupts
> *
Hi Andy,
Was there a reason to not use the vectors in the 0x2X range?
-hpa
next prev parent reply other threads:[~2011-08-09 19:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-09 14:27 [PATCH 0/4] vsyscall tweaks Andy Lutomirski
2011-08-09 14:27 ` [PATCH 1/4] x86-64: Allow emulated vsyscalls from user addresses Andy Lutomirski
2011-08-09 18:59 ` H. Peter Anvin [this message]
2011-08-09 19:16 ` Andrew Lutomirski
2011-08-09 14:27 ` [PATCH 2/4] x86: Remove unnecessary compile flag tweaks for vsyscall code Andy Lutomirski
2011-08-09 14:27 ` [PATCH 3/4] x86-64: Wire up getcpu syscall Andy Lutomirski
2011-08-09 14:27 ` [PATCH 4/4] Add vsyscalls to feature-removal-schedule.txt Andy Lutomirski
2011-08-12 18:25 ` NACK! " Andi Kleen
2011-08-12 19:13 ` Andrew Lutomirski
2011-08-17 20:35 ` Ingo Molnar
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=4E418388.9050600@zytor.com \
--to=hpa@zytor.com \
--cc=andi@firstfloor.org \
--cc=bp@alien8.de \
--cc=kimwooyoung@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lueckintel@yahoo.com \
--cc=luto@mit.edu \
--cc=mingo@elte.hu \
--cc=suresh.b.siddha@intel.com \
--cc=torvalds@linux-foundation.org \
--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 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.