From: "Petr Vandrovec" <VANDROVE@vc.cvut.cz>
To: Zwane Mwaikambo <zwane@linuxpower.ca>
Cc: linux-kernel@vger.kernel.org, rddunlap@osdl.org
Subject: Re: [PATCH][2.5] VMWare doesn't like sysenter
Date: Fri, 16 May 2003 18:28:07 +0200 [thread overview]
Message-ID: <1AF6C870AF5@vcnet.vc.cvut.cz> (raw)
On 15 May 03 at 11:15, Zwane Mwaikambo wrote:
> On Thu, 15 May 2003, Randy.Dunlap wrote:
>
> > On Thu, 15 May 2003 04:02:31 -0400 (EDT) Zwane Mwaikambo <zwane@linuxpower.ca> wrote:
> >
> > | I get a monitor error in VMWare4 with a sysenter syscall enabled kernel,
> > | this patch simply disables sysenter based syscalls but doesn't clear the
> > | SEP bit in the capabilities.
> >
> > | +static int __init do_nosysenter(char *s)
> > | +{
> > | + nosysenter = 1;
> > | + return 1;
> > | +}
> > | +__setup("nosysenter", do_nosysenter);
> >
> > Needs entry in Documentation/kernel-parameters.txt also
> > if/when accepted.
>
> Thanks for the heads up.
>
> Index: linux-2.5.69-mm5/Documentation/kernel-parameters.txt
> ===================================================================
> RCS file: /build/cvsroot/linux-2.5.69/Documentation/kernel-parameters.txt,v
> retrieving revision 1.1.1.1
> diff -u -p -B -r1.1.1.1 kernel-parameters.txt
> --- linux-2.5.69-mm5/Documentation/kernel-parameters.txt 6 May 2003 12:21:18 -0000 1.1.1.1
> +++ linux-2.5.69-mm5/Documentation/kernel-parameters.txt 15 May 2003 15:14:23 -0000
> @@ -1063,6 +1063,10 @@ running once the system is up.
>
> sym53c8xx= [HW,SCSI]
> See Documentation/scsi/ncr53c8xx.txt.
> +
> + nosysenter [IA-32]
> + Disable SYSENTER for syscalls, does not clear the SEP
> + capabilities bit.
RedHat's 9 backport of vsyscalls uses 'nosysinfo' name for
option which does simillar task (it just stops kernel from reporting
relevant AT_SYSINFO completely).
BTW, what's reason for this backport? They just always put int 0x80
into this page, so even on real CPU kernel booted with nosysinfo
is faster than one which uses this vsyscall entry point.
VMware's panic should be fixed in next update, but I'm afraid that
penalty from exectuing code in upper couple of MBs of address space
will not disappear. Moving SYSINFO page from FFFFE000 to FF7FF000
(PKMAP_BASE - PAGE_SIZE == VMALLOC_END + PAGE_SIZE) would fix both
problems.
Petr Vandrovec
vandrove@vc.cvut.cz
next reply other threads:[~2003-05-16 16:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-16 16:28 Petr Vandrovec [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-05-15 8:02 [PATCH][2.5] VMWare doesn't like sysenter Zwane Mwaikambo
2003-05-15 14:47 ` Randy.Dunlap
2003-05-15 15:15 ` Zwane Mwaikambo
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=1AF6C870AF5@vcnet.vc.cvut.cz \
--to=vandrove@vc.cvut.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=rddunlap@osdl.org \
--cc=zwane@linuxpower.ca \
/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