From: Paolo Bonzini <pbonzini@redhat.com>
To: Alex Williamson <alex.williamson@redhat.com>,
Michael Tokarev <mjt@tls.msk.ru>
Cc: qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: Re: [RFC PATCH] kvm: Enable -cpu option to hide KVM
Date: Mon, 02 Jun 2014 17:55:12 +0200 [thread overview]
Message-ID: <538C9E60.4040501@redhat.com> (raw)
In-Reply-To: <1401715821.9207.20.camel@ul30vt.home>
Il 02/06/2014 15:30, Alex Williamson ha scritto:
> Then they'll be pissing off more users and driving them to AMD by doing
> so. In any case, having the ability to hide the hypervisor seems to
> stand on it's own. What if we want to test whether a guest behavior is
> the result of a paravirtual interface? What if a user wants to hide the
> hypervisor in order to further reduce the exposure surface to the VM?
> There are reasons beyond an arms race with Nvidia to want a feature like
> this. Thanks,
I totally agree with you.
This doesn't mean that nVidia doesn't deserve some bad press for
starting this kind of arms race, of course. :)
Paolo
WARNING: multiple messages have this Message-ID (diff)
From: Paolo Bonzini <pbonzini@redhat.com>
To: Alex Williamson <alex.williamson@redhat.com>,
Michael Tokarev <mjt@tls.msk.ru>
Cc: qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: Re: [Qemu-devel] [RFC PATCH] kvm: Enable -cpu option to hide KVM
Date: Mon, 02 Jun 2014 17:55:12 +0200 [thread overview]
Message-ID: <538C9E60.4040501@redhat.com> (raw)
In-Reply-To: <1401715821.9207.20.camel@ul30vt.home>
Il 02/06/2014 15:30, Alex Williamson ha scritto:
> Then they'll be pissing off more users and driving them to AMD by doing
> so. In any case, having the ability to hide the hypervisor seems to
> stand on it's own. What if we want to test whether a guest behavior is
> the result of a paravirtual interface? What if a user wants to hide the
> hypervisor in order to further reduce the exposure surface to the VM?
> There are reasons beyond an arms race with Nvidia to want a feature like
> this. Thanks,
I totally agree with you.
This doesn't mean that nVidia doesn't deserve some bad press for
starting this kind of arms race, of course. :)
Paolo
next prev parent reply other threads:[~2014-06-02 15:55 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-01 16:25 [RFC PATCH] kvm: Enable -cpu option to hide KVM Alex Williamson
2014-06-01 16:25 ` [Qemu-devel] " Alex Williamson
2014-06-01 18:29 ` Paolo Bonzini
2014-06-01 18:29 ` [Qemu-devel] " Paolo Bonzini
2014-06-01 21:11 ` Alex Williamson
2014-06-01 21:11 ` [Qemu-devel] " Alex Williamson
2014-06-02 7:09 ` Paolo Bonzini
2014-06-02 7:09 ` [Qemu-devel] " Paolo Bonzini
2014-06-02 14:42 ` Alex Williamson
2014-06-02 14:42 ` [Qemu-devel] " Alex Williamson
2014-06-02 15:55 ` Paolo Bonzini
2014-06-02 15:55 ` [Qemu-devel] " Paolo Bonzini
2014-06-02 10:32 ` Michael Tokarev
2014-06-02 10:32 ` [Qemu-devel] " Michael Tokarev
2014-06-02 13:30 ` Alex Williamson
2014-06-02 13:30 ` [Qemu-devel] " Alex Williamson
2014-06-02 15:55 ` Paolo Bonzini [this message]
2014-06-02 15:55 ` Paolo Bonzini
2014-06-02 18:01 ` Michael Tokarev
2014-06-02 18:01 ` [Qemu-devel] " Michael Tokarev
2014-06-02 18:37 ` Alex Williamson
2014-06-02 18:37 ` [Qemu-devel] " Alex Williamson
2014-06-02 19:03 ` Bandan Das
2014-06-02 19:03 ` [Qemu-devel] " Bandan Das
2014-06-02 19:18 ` Alex Williamson
2014-06-02 19:18 ` [Qemu-devel] " Alex Williamson
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=538C9E60.4040501@redhat.com \
--to=pbonzini@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=mjt@tls.msk.ru \
--cc=qemu-devel@nongnu.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.