From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: Ingo Molnar <mingo-X9Un+BFzKDI@public.gmane.org>
Cc: kvm-devel <kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: %fs PDA & KVM
Date: Sun, 11 Mar 2007 14:38:53 +0200 [thread overview]
Message-ID: <45F3F85D.7000509@qumranet.com> (raw)
In-Reply-To: <20070311122441.GA10774-X9Un+BFzKDI@public.gmane.org>
Ingo Molnar wrote:
> hm, i just noticed that in vmx_vcpu_run() KVM restores %fs quite late.
>
> This is a bit awkward under v2.6.21 x86 because there we use %fs for the
> KERNEL_PDA area. Things like 'current' rely on it. So maybe we should
> just do this unconditionally in assembly:
>
> movl $(__KERNEL_PDA), %edx;
> movl %edx, %fs
>
Sure, but with %dx instead of %edx, please.
> it's also a problem with -rt too, which has that whole codepath up to
> the load_fs() call preemptible.
>
> i'm also wondering about this bit:
>
> kvm_run->exit_type = 0;
> if (fail) {
> kvm_run->exit_type = KVM_EXIT_TYPE_FAIL_ENTRY;
> kvm_run->exit_reason = vmcs_read32(VM_INSTRUCTION_ERROR);
> kvm_cr3_cache_sync(vcpu);
> r = 0;
> } else {
> if (fs_gs_ldt_reload_needed) {
> load_ldt(ldt_sel);
> load_fs(fs_sel);
>
> are you sure we dont need an FS reload in the 'fail' case?
>
The manual is not explicit about it, but I think that an entry failure
during loading of guest state _can_ cause fs to be loaded, so yes, that
path is missing the segment reloads.
Non -rt kvm cannot preempt there even with CONFIG_PREEMPT=y. Can
interrupts reference current? If so, that fix is needed badly for .21.
--
error compiling committee.c: too many arguments to function
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
next prev parent reply other threads:[~2007-03-11 12:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-11 12:24 %fs PDA & KVM Ingo Molnar
[not found] ` <20070311122441.GA10774-X9Un+BFzKDI@public.gmane.org>
2007-03-11 12:38 ` Avi Kivity [this message]
[not found] ` <45F3F85D.7000509-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-03-11 12:41 ` Ingo Molnar
2007-03-11 12:52 ` [patch] KVM: always reload segment selectors Ingo Molnar
2007-03-11 12:52 ` Ingo Molnar
2007-03-11 13:04 ` Avi Kivity
2007-03-11 13:04 ` Avi Kivity
2007-03-11 22:19 ` %fs PDA & KVM Rusty Russell
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=45F3F85D.7000509@qumranet.com \
--to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=mingo-X9Un+BFzKDI@public.gmane.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.