From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Andy Lutomirski <luto@amacapital.net>
Cc: kvm list <kvm@vger.kernel.org>, Rusty Russell <rusty@rustcorp.com.au>
Subject: Re: Stupid Xen vs KVM question
Date: Thu, 4 Dec 2014 21:24:20 -0500 [thread overview]
Message-ID: <20141205022420.GA27661@konrad-lan.dumpdata.com> (raw)
In-Reply-To: <CALCETrUQfzqtVzE8GV2yRkzyiWzVfzL-FL8FzTRXJQiFSXhk+w@mail.gmail.com>
On Thu, Dec 04, 2014 at 02:59:48PM -0800, Andy Lutomirski wrote:
> This code in arch/x86/kernel/entry_32.S is wrong:
>
> #ifdef CONFIG_PARAVIRT
> /*
> * The kernel can't run on a non-flat stack if paravirt mode
> * is active. Rather than try to fixup the high bits of
> * ESP, bypass this code entirely. This may break DOSemu
> * and/or Wine support in a paravirt VM, although the option
> * is still available to implement the setting of the high
> * 16-bits in the INTERRUPT_RETURN paravirt-op.
> */
> cmpl $0, pv_info+PARAVIRT_enabled
> jne restore_nocheck
> #endif
>
> On KVM guests, it notices that paravirt is enabled and bails. It
> should work fine on KVM -- the condition it should be checking is
> whether we have native segmentation.
>
> Do you know the right way to ask that?
We could do a simple thing - which is that the paravirt_enabled
could have the value 1 for Xen and 2 for KVM. The assembler logic
would be inverted and just check for 1. I am not going to attempt
to write the assembler code :-)
>
> Thanks,
> Andy
>
> --
> Andy Lutomirski
> AMA Capital Management, LLC
next prev parent reply other threads:[~2014-12-05 2:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-04 22:59 Stupid Xen vs KVM question Andy Lutomirski
2014-12-05 2:24 ` Konrad Rzeszutek Wilk [this message]
2014-12-05 7:29 ` Paolo Bonzini
2014-12-05 16:09 ` Konrad Rzeszutek Wilk
2014-12-05 17:52 ` Andy Lutomirski
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=20141205022420.GA27661@konrad-lan.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=kvm@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=rusty@rustcorp.com.au \
/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.