All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Andrew Lutomirski <luto@mit.edu>
Cc: Keir Fraser <keir.xen@gmail.com>,
	xen-devel@lists.xensource.com,
	Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Subject: Re: [semi-urgent Xen CS question] Re: git commit 9fd67b4ed0714ab718f1f9bd14c344af336a6df7 (x86-64: Give vvars their own page) breaks Xen PV guests (64-bit).
Date: Fri, 29 Jul 2011 08:31:35 -0700	[thread overview]
Message-ID: <4E32D257.6090606@goop.org> (raw)
In-Reply-To: <CAObL_7G4Au=4wBaS4jJgaLCF7CrwO18tkOnQ3sCP6jaNY8-xaA@mail.gmail.com>

On 07/29/2011 05:51 AM, Andrew Lutomirski wrote:
> VCGF_in_syscall: gettimeofday() (the syscall version) takes 593 ns.
> Without VCGF_in_syscall, it's 712 ns.
>
> I'd argue for using my original approach of adding a user_64bit_mode
> function -- I think it's a legitimate cleanup and Xen, for better or
> worse, really does have two long mode CPL 3 selectors.  If we removed
> selector 6 from the GDT, that would be a different story, but that
> would probably be a more intrusive change.

Sigh.  Yeah, let's see what happens.

    J

  reply	other threads:[~2011-07-29 15:31 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-25 15:54 git commit 9fd67b4ed0714ab718f1f9bd14c344af336a6df7 (x86-64: Give vvars their own page) breaks Xen PV guests (64-bit) Konrad Rzeszutek Wilk
2011-07-25 15:54 ` Konrad Rzeszutek Wilk
2011-07-25 16:10 ` Konrad Rzeszutek Wilk
2011-07-25 16:10   ` Konrad Rzeszutek Wilk
2011-07-25 18:10   ` Andrew Lutomirski
2011-07-26  7:18     ` Jan Beulich
2011-07-26  7:18       ` Jan Beulich
2011-07-26 16:18     ` Konrad Rzeszutek Wilk
2011-07-26 16:46       ` Ian Campbell
2011-07-26 19:01       ` Andrew Lutomirski
2011-07-26 20:51         ` Konrad Rzeszutek Wilk
2011-07-26 20:51           ` Konrad Rzeszutek Wilk
2011-07-26 20:55           ` Andrew Lutomirski
2011-07-26 20:55             ` Andrew Lutomirski
2011-07-26 21:06             ` Konrad Rzeszutek Wilk
2011-07-26 21:06               ` Konrad Rzeszutek Wilk
     [not found] ` <CAObL_7GpX=f3+tXA4ga6cBB_9VWBe6yVFvon=TzECQs5kcb-ag@mail.gmail.com>
     [not found]   ` <20110726153220.GA15110@dumpdata.com>
2011-07-26 19:08     ` [semi-urgent Xen CS question] " Andrew Lutomirski
2011-07-26 20:48       ` Keir Fraser
2011-07-26 21:10         ` Andrew Lutomirski
2011-07-26 21:40           ` Andrew Lutomirski
2011-07-26 22:20             ` Keir Fraser
2011-07-26 23:37             ` j.fitz.inge@gmail.com
2011-07-27  2:17               ` Andrew Lutomirski
2011-07-27 15:40                 ` Jeremy Fitzhardinge
2011-07-27 16:02                   ` Andrew Lutomirski
2011-07-27 17:19                     ` Jeremy Fitzhardinge
2011-07-28  4:33                       ` Andrew Lutomirski
2011-07-28  6:07                         ` Jeremy Fitzhardinge
2011-07-29 12:51                           ` Andrew Lutomirski
2011-07-29 15:31                             ` Jeremy Fitzhardinge [this message]
2011-07-31 18:56                               ` Konrad Rzeszutek Wilk
2011-07-31 19:14                                 ` Andrew Lutomirski
2011-08-02 14:10                                   ` Konrad Rzeszutek Wilk
2011-07-27 12:57           ` Konrad Rzeszutek Wilk

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=4E32D257.6090606@goop.org \
    --to=jeremy@goop.org \
    --cc=keir.xen@gmail.com \
    --cc=konrad.wilk@oracle.com \
    --cc=luto@mit.edu \
    --cc=xen-devel@lists.xensource.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 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.