All of lore.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: Andre Przywara <andre.przywara@amd.com>,
	Ricardo Martins <ricardo.martins.br@gmail.com>,
	"kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: Re: KVM Processor cache size
Date: Tue, 03 Aug 2010 08:41:35 +0300	[thread overview]
Message-ID: <4C57AC0F.3070909@redhat.com> (raw)
In-Reply-To: <4C575776.30106@codemonkey.ws>

  On 08/03/2010 02:40 AM, Anthony Liguori wrote:
>
> Yes, but virtualization is not supposed to expose the underlying 
> hardware.  The vendor_id bit is a harder problem that I'm willing to 
> ignore in this discussion.  I understand why we have to do this today.

Today and forever... unless one of the processor vendors starts 
supporting the other's fast system call instructions on all modes.

-- 
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.


  reply	other threads:[~2010-08-03  5:41 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-02 11:45 KVM Processor cache size Ricardo Martins
2010-08-02 12:51 ` Andre Przywara
2010-08-02 13:08   ` Avi Kivity
2010-08-02 22:22     ` Anthony Liguori
2010-08-02 22:35       ` Andre Przywara
2010-08-02 23:38         ` Anthony Liguori
2010-08-03  5:38           ` Avi Kivity
2010-08-03  5:33       ` Avi Kivity
2010-08-02 22:25     ` Anthony Liguori
2010-08-02 22:54       ` Andre Przywara
2010-08-02 23:40         ` Anthony Liguori
2010-08-03  5:41           ` Avi Kivity [this message]
2010-08-02 13:49   ` Ulrich Drepper
2010-08-02 18:38     ` Ricardo Martins
2010-08-02 22:24       ` Andre Przywara
2010-08-02 22:15     ` Andre Przywara
2010-08-02 22:23     ` Anthony Liguori
2010-08-02 22:42       ` Andre Przywara
2010-08-02 23:36         ` Anthony Liguori
2010-08-03  6:25           ` Dor Laor

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=4C57AC0F.3070909@redhat.com \
    --to=avi@redhat.com \
    --cc=andre.przywara@amd.com \
    --cc=anthony@codemonkey.ws \
    --cc=kvm@vger.kernel.org \
    --cc=ricardo.martins.br@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.