All of lore.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi.kivity@gmail.com>
To: Jan Kiszka <jan.kiszka@siemens.com>, Joel Schopp <joel.schopp@amd.com>
Cc: Valentine Sinitsyn <valentine.sinitsyn@gmail.com>,
	kvm <kvm@vger.kernel.org>,
	Jailhouse <jailhouse-dev@googlegroups.com>
Subject: Re: SVM: vmload/vmsave-free VM exits?
Date: Mon, 13 Apr 2015 21:07:55 +0300	[thread overview]
Message-ID: <552C05FB.5060604@gmail.com> (raw)
In-Reply-To: <552C0376.30102@siemens.com>

On 04/13/2015 08:57 PM, Jan Kiszka wrote:
> On 2015-04-13 19:48, Avi Kivity wrote:
>> I think that Xen does (or did) something along the lines of disabling
>> IST usage (by playing with the descriptors in the IDT) and then
>> re-enabling them when exiting to userspace.
> So we would reuse that active stack for the current IST users until
> then.

Yes.

> But I bet there are subtle details that prevent a simple switch at
> IDT level. Hmm, no low-hanging fruit it seems...


For sure. It's not insurmountable, but fairly hard.

>>
>>> [17] http://thread.gmane.org/gmane.comp.emulators.kvm.devel/26712/
> That thread proposed the complete IST removal. But, given that we still
> have it 7 years later,

Well, it's not as if a crack team of kernel hackers was laboring night 
and day to remove it, but...

>   I suppose that was not very welcome in general.

Simply removing it is impossible, or an NMI happening immediately after 
SYSCALL will hit user-provided %rsp.

> Thanks,
> Jan
>
> PS: For the Jailhouse readers: we don't use IST.
>

You don't have userspace, yes?  Only guests?

-- 
You received this message because you are subscribed to the Google Groups "Jailhouse" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jailhouse-dev+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

  reply	other threads:[~2015-04-13 18:07 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-05  8:31 SVM: vmload/vmsave-free VM exits? Jan Kiszka
2015-04-05 17:12 ` Valentine Sinitsyn
2015-04-07  5:43   ` Jan Kiszka
2015-04-07  6:10     ` Valentine Sinitsyn
2015-04-07  6:13       ` Jan Kiszka
2015-04-07  6:19         ` Valentine Sinitsyn
2015-04-07  6:23           ` Jan Kiszka
2015-04-07  6:29             ` Valentine Sinitsyn
2015-04-07  6:35               ` Jan Kiszka
2015-04-13  7:01     ` Jan Kiszka
2015-04-13 17:29       ` Avi Kivity
2015-04-13 17:35         ` Jan Kiszka
2015-04-13 17:41           ` Avi Kivity
2015-04-13 17:48             ` Avi Kivity
2015-04-13 17:57               ` Jan Kiszka
2015-04-13 18:07                 ` Avi Kivity [this message]
2015-04-13 18:14                   ` Jan Kiszka
2015-04-14  6:39             ` Valentine Sinitsyn
2015-04-14  7:02               ` Jan Kiszka
2015-04-14  7:11                 ` Valentine Sinitsyn

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=552C05FB.5060604@gmail.com \
    --to=avi.kivity@gmail.com \
    --cc=jailhouse-dev@googlegroups.com \
    --cc=jan.kiszka@siemens.com \
    --cc=joel.schopp@amd.com \
    --cc=kvm@vger.kernel.org \
    --cc=valentine.sinitsyn@gmail.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.