public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Dor Laor <dor.laor-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Joerg Roedel <joerg.roedel-5C7GfCeVMHo@public.gmane.org>
Cc: kvm-devel
	<kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>,
	Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
Subject: Re: question on #UD emulation
Date: Sun, 16 Dec 2007 14:49:31 +0200	[thread overview]
Message-ID: <47651EDB.2010601@qumranet.com> (raw)
In-Reply-To: <20071216123318.GB31298-5C7GfCeVMHo@public.gmane.org>


[-- Attachment #1.1: Type: text/plain, Size: 2677 bytes --]

Joerg Roedel wrote:
>
> On Sun, Dec 16, 2007 at 01:32:40PM +0200, Avi Kivity wrote:
> > Dong, Eddie wrote:
> >
> > > BTW, do we need to support live migrating an AMD VM to Intel 
> platform or
> > > vice versa
> >
> > Yes, it allows users to buy the machines with the best cost/performance
> > ratio, rather than continue to buy machines from the same vendor all the
> > time.
>
> I don't agree with this. A user can still buy machines from both vendors
> and migrate offline it he wants to. In general I think that allowing
> live migration between Intel and AMD hosts is not a good idea because
> you limit the guest to the subset of the CPU features available on both
> platforms. This disallows many optimizations and costs performance for
> the guest.
>
Having the option to live migrate between various hosts is a powerful 
feature.
Of course it costs some performance penalty but it might not be relevant 
for the user
work load.
By having cmd line parameters to control the cpuid and cpu type one can 
dynamically calculate
the lowest common denominator and to run his virtual machines using it.
One can always pass -cpu=host to have maximum performance.
For users who like to live migrate between Amd-Intel we'll use one of 
cpu types
for both.
Regards,
Dor
>
> Take the problem Dor mentioned this week about the performance impact of
> the gettimeofday() syscall causing many cpuid guest exits. If we had
> not to support migration between AMD and Intel we could simply propagate
> FEATURE_RDTSCP to an guest on AMD an SYNC_RDTSC on Intel platforms. The
> Linux get_cycles_sync() function would then no longer execute CPUID.
> This is only one example, I found some more during my work on KVM.
>
> Joerg
>
> --
>            |           AMD Saxony Limited Liability Company & Co. KG
>  Operating |         Wilschdorfer Landstr. 101, 01109 Dresden, Germany
>  System    |                  Register Court Dresden: HRA 4896
>  Research  |              General Partner authorized to represent:
>  Center    |             AMD Saxony LLC (Wilmington, Delaware, US)
>            | General Manager of AMD Saxony LLC: Dr. Hans-R. Deppe, 
> Thomas McCoy
>
>
>
> -------------------------------------------------------------------------
> SF.Net email is sponsored by:
> Check out the new SourceForge.net Marketplace.
> It's the best place to buy or sell services
> for just about anything Open Source.
> http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
> _______________________________________________
> kvm-devel mailing list
> kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
> https://lists.sourceforge.net/lists/listinfo/kvm-devel
>


[-- Attachment #1.2: Type: text/html, Size: 4358 bytes --]

[-- Attachment #2: Type: text/plain, Size: 308 bytes --]

-------------------------------------------------------------------------
SF.Net email is sponsored by:
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services
for just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace

[-- Attachment #3: Type: text/plain, Size: 186 bytes --]

_______________________________________________
kvm-devel mailing list
kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
https://lists.sourceforge.net/lists/listinfo/kvm-devel

  parent reply	other threads:[~2007-12-16 12:49 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-16 10:01 question on #UD emulation Dong, Eddie
     [not found] ` <10EA09EFD8728347A513008B6B0DA77A02858E27-wq7ZOvIWXbNpB2pF5aRoyrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2007-12-16 11:32   ` Avi Kivity
     [not found]     ` <47650CD8.5060401-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-12-16 12:33       ` Joerg Roedel
     [not found]         ` <20071216123318.GB31298-5C7GfCeVMHo@public.gmane.org>
2007-12-16 12:49           ` Dor Laor [this message]
     [not found]             ` <47651EDB.2010601-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-12-16 14:42               ` Dong, Eddie
     [not found]                 ` <10EA09EFD8728347A513008B6B0DA77A02858E8C-wq7ZOvIWXbNpB2pF5aRoyrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2007-12-16 15:04                   ` Avi Kivity
2007-12-16 14:44       ` Dong, Eddie
     [not found]         ` <10EA09EFD8728347A513008B6B0DA77A02858E8E-wq7ZOvIWXbNpB2pF5aRoyrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2007-12-16 15:07           ` Avi Kivity

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=47651EDB.2010601@qumranet.com \
    --to=dor.laor-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org \
    --cc=dor.laor-atKUWr5tajBWk0Htik3J/w@public.gmane.org \
    --cc=joerg.roedel-5C7GfCeVMHo@public.gmane.org \
    --cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox