All of lore.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@qumranet.com>
To: Anthony Liguori <aliguori@us.ibm.com>
Cc: kvm-devel@lists.sourceforge.net,
	kvm-ppc-devel@lists.sourceforge.net,
	Hollis Blanchard <hollisb@us.ibm.com>
Subject: Re: [kvm-ppc-devel] [kvm-devel] [PATCH 0 of 3] RFC: creating a
Date: Mon, 11 Feb 2008 08:23:06 +0000	[thread overview]
Message-ID: <47B005EA.5000108@qumranet.com> (raw)
In-Reply-To: <47A8B9C4.3010709@us.ibm.com>

Anthony Liguori wrote:
>
> So the new ioctl() has the extra data and the old ioctl() is just a 
> compat interface which calls the new ioctl with a NULL extra data.  I 
> think this is the better approach if you're going this route.
>
> However, I still don't think that supporting asymmetric cores is 
> really useful at the moment and that introducing a per-vm arch ioctl 
> would be the best approach.

Note that kvm/x86 supports slightly asymmetric cores, in that the cpuid 
results can be different for different vcpus.  I can't judge how 
important this feature is for ppc, though.

-- 
error compiling committee.c: too many arguments to function


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
kvm-ppc-devel mailing list
kvm-ppc-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kvm-ppc-devel

WARNING: multiple messages have this Message-ID (diff)
From: Avi Kivity <avi@qumranet.com>
To: Anthony Liguori <aliguori@us.ibm.com>
Cc: kvm-devel@lists.sourceforge.net,
	kvm-ppc-devel@lists.sourceforge.net,
	Hollis Blanchard <hollisb@us.ibm.com>
Subject: Re: [PATCH 0 of 3] RFC: creating a particular vcpu type
Date: Mon, 11 Feb 2008 10:23:06 +0200	[thread overview]
Message-ID: <47B005EA.5000108@qumranet.com> (raw)
In-Reply-To: <47A8B9C4.3010709@us.ibm.com>

Anthony Liguori wrote:
>
> So the new ioctl() has the extra data and the old ioctl() is just a 
> compat interface which calls the new ioctl with a NULL extra data.  I 
> think this is the better approach if you're going this route.
>
> However, I still don't think that supporting asymmetric cores is 
> really useful at the moment and that introducing a per-vm arch ioctl 
> would be the best approach.

Note that kvm/x86 supports slightly asymmetric cores, in that the cpuid 
results can be different for different vcpus.  I can't judge how 
important this feature is for ppc, though.

-- 
error compiling committee.c: too many arguments to function


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

  reply	other threads:[~2008-02-11  8:23 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-05  5:34 [kvm-ppc-devel] [PATCH 0 of 3] RFC: creating a particular vcpu type Hollis Blanchard
2008-02-05  5:34 ` Hollis Blanchard
2008-02-05  5:34 ` [kvm-ppc-devel] [PATCH 1 of 3] Pass an opaque parameter Hollis Blanchard
2008-02-05  5:34   ` [PATCH 1 of 3] Pass an opaque parameter through kvm_vm_ioctl_vcpu_create() to kvm_arch_vcpu_create() Hollis Blanchard
2008-02-05  5:34 ` [kvm-ppc-devel] [PATCH 2 of 3] Export kvm_vm_ioctl_create_vcpu() to Hollis Blanchard
2008-02-05  5:34   ` [PATCH 2 of 3] Export kvm_vm_ioctl_create_vcpu() to be called from architecture modules Hollis Blanchard
2008-02-05  5:34 ` [kvm-ppc-devel] [PATCH 3 of 3] [POWERPC] Implement an ioctl that Hollis Blanchard
2008-02-05  5:34   ` [PATCH 3 of 3] [POWERPC] Implement an ioctl that creates a vcpu of a particular type Hollis Blanchard
2008-02-05 12:52   ` [kvm-ppc-devel] [kvm-devel] [PATCH 3 of 3] [POWERPC] Implement Christian Ehrhardt
2008-02-05 12:52     ` [PATCH 3 of 3] [POWERPC] Implement an ioctl that creates a vcpu of a particular type Christian Ehrhardt
     [not found]     ` <47A85C09.5070609-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
2008-02-05 13:41       ` [kvm-ppc-devel] [kvm-devel] [PATCH 3 of 3] [POWERPC] Implement Carsten Otte
2008-02-05 13:41         ` [PATCH 3 of 3] [POWERPC] Implement an ioctl that creates a vcpu of a particular type Carsten Otte
     [not found]         ` <47A86794.4020408-tA70FqPdS9bQT0dZR+AlfA@public.gmane.org>
2008-02-05 14:03           ` [kvm-ppc-devel] [kvm-devel] [PATCH 3 of 3] [POWERPC] Implement Carsten Otte
2008-02-05 14:03             ` [PATCH 3 of 3] [POWERPC] Implement an ioctl that creates a vcpu of a particular type Carsten Otte
2008-02-05 15:13       ` [kvm-ppc-devel] [kvm-devel] [PATCH 3 of 3] [POWERPC] Implement Hollis Blanchard
2008-02-05 15:13         ` [PATCH 3 of 3] [POWERPC] Implement an ioctl that creates a vcpu of a particular type Hollis Blanchard
2008-02-05 16:44 ` [kvm-ppc-devel] [kvm-devel] [PATCH 0 of 3] RFC: creating a Anthony Liguori
2008-02-05 16:44   ` [PATCH 0 of 3] RFC: creating a particular vcpu type Anthony Liguori
     [not found]   ` <47A89285.40802-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2008-02-05 17:53     ` [kvm-ppc-devel] [kvm-devel] [PATCH 0 of 3] RFC: creating a Hollis Blanchard
2008-02-05 17:53       ` [PATCH 0 of 3] RFC: creating a particular vcpu type Hollis Blanchard
2008-02-05 18:05       ` [kvm-ppc-devel] [kvm-devel] [PATCH 0 of 3] RFC: creating a Anthony Liguori
2008-02-05 18:05         ` [PATCH 0 of 3] RFC: creating a particular vcpu type Anthony Liguori
     [not found]         ` <47A8A582.5060502-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2008-02-05 19:23           ` [kvm-ppc-devel] [kvm-devel] [PATCH 0 of 3] RFC: creating a Hollis Blanchard
2008-02-05 19:23             ` [PATCH 0 of 3] RFC: creating a particular vcpu type Hollis Blanchard
2008-02-05 19:32             ` [kvm-ppc-devel] [kvm-devel] [PATCH 0 of 3] RFC: creating a Anthony Liguori
2008-02-05 19:32               ` [PATCH 0 of 3] RFC: creating a particular vcpu type Anthony Liguori
2008-02-11  8:23               ` Avi Kivity [this message]
2008-02-11  8:23                 ` 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=47B005EA.5000108@qumranet.com \
    --to=avi@qumranet.com \
    --cc=aliguori@us.ibm.com \
    --cc=hollisb@us.ibm.com \
    --cc=kvm-devel@lists.sourceforge.net \
    --cc=kvm-ppc-devel@lists.sourceforge.net \
    /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.