From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Andy Lutomirski <luto@amacapital.net>,
kvm list <kvm@vger.kernel.org>,
Rusty Russell <rusty@rustcorp.com.au>
Subject: Re: Stupid Xen vs KVM question
Date: Fri, 5 Dec 2014 11:09:08 -0500 [thread overview]
Message-ID: <20141205160908.GB472@laptop.dumpdata.com> (raw)
In-Reply-To: <54815EF2.4030808@redhat.com>
On Fri, Dec 05, 2014 at 08:29:54AM +0100, Paolo Bonzini wrote:
>
>
> On 05/12/2014 03:24, Konrad Rzeszutek Wilk wrote:
> > 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 :-)
>
> Wouldn't Xen HVM also want to be 2?
Oddly enough it was never set!
Looking at where the paravit_enabled() macro is used, on KVM it could
be just set to zero.
>
> Paolo
next prev parent reply other threads:[~2014-12-05 16:09 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
2014-12-05 7:29 ` Paolo Bonzini
2014-12-05 16:09 ` Konrad Rzeszutek Wilk [this message]
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=20141205160908.GB472@laptop.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=kvm@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=pbonzini@redhat.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox