From: Carsten Otte <cotte@de.ibm.com>
To: Christian Ehrhardt
<ehrhardt-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
kvm-ppc-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>,
Hollis Blanchard
<hollisb-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
Subject: Re: [kvm-ppc-devel] [kvm-devel] [PATCH 3 of 3] [POWERPC] Implement
Date: Tue, 05 Feb 2008 13:41:40 +0000 [thread overview]
Message-ID: <47A86794.4020408@de.ibm.com> (raw)
In-Reply-To: <47A85C09.5070609-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
Christian Ehrhardt wrote:
> This should work for other architectures too. While we need to specify
> cpu cores here others might specify something completely different with
> the same interface.
> So kvm_vcpu_create_type might be misleading while something like
> kvm_vcpu_create_info might be more generic.
> Just to get some background - do anyone else see the need to specify a
> detail on vcpu_create for their implementation in future ?
We do. For now, kvm_create_vcpu does create a cpu from a template.
However our hardware control block allows to enable/disable various
features. I would imagine that future userspace may want something
different than the stock default values, and therefore a parameter
would make sense for us too.
-------------------------------------------------------------------------
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: Carsten Otte <cotte-tA70FqPdS9bQT0dZR+AlfA@public.gmane.org>
To: Christian Ehrhardt
<ehrhardt-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
kvm-ppc-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>,
Hollis Blanchard
<hollisb-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
Subject: Re: [PATCH 3 of 3] [POWERPC] Implement an ioctl that creates a vcpu of a particular type
Date: Tue, 05 Feb 2008 14:41:40 +0100 [thread overview]
Message-ID: <47A86794.4020408@de.ibm.com> (raw)
In-Reply-To: <47A85C09.5070609-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
Christian Ehrhardt wrote:
> This should work for other architectures too. While we need to specify
> cpu cores here others might specify something completely different with
> the same interface.
> So kvm_vcpu_create_type might be misleading while something like
> kvm_vcpu_create_info might be more generic.
> Just to get some background - do anyone else see the need to specify a
> detail on vcpu_create for their implementation in future ?
We do. For now, kvm_create_vcpu does create a cpu from a template.
However our hardware control block allows to enable/disable various
features. I would imagine that future userspace may want something
different than the stock default values, and therefore a parameter
would make sense for us too.
-------------------------------------------------------------------------
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/
next prev parent reply other threads:[~2008-02-05 13:41 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 ` Carsten Otte [this message]
2008-02-05 13:41 ` 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 ` [kvm-ppc-devel] [kvm-devel] [PATCH 0 of 3] RFC: creating a Avi Kivity
2008-02-11 8:23 ` [PATCH 0 of 3] RFC: creating a particular vcpu type 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=47A86794.4020408@de.ibm.com \
--to=cotte@de.ibm.com \
--cc=avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org \
--cc=ehrhardt-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org \
--cc=hollisb-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=kvm-ppc-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 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.