From: Avi Kivity <avi@redhat.com>
To: Gleb Natapov <gleb@redhat.com>
Cc: kvm@vger.kernel.org
Subject: Re: [PATCH 3/4] Break dependency between vcpu index in vcpus array and vcpu_id.
Date: Mon, 08 Jun 2009 14:23:13 +0300 [thread overview]
Message-ID: <4A2CF4A1.2030603@redhat.com> (raw)
In-Reply-To: <1244453578-29857-4-git-send-email-gleb@redhat.com>
Gleb Natapov wrote:
> Archs are free to use vcpu_id as they see fit. For x86 it is used as
> vcpu's apic id. New ioctl is added to configure boot vcpu id that was
> assumed to be 0 till now.
>
> @@ -2284,6 +2291,7 @@ static long kvm_dev_ioctl_check_extension_generic(long arg)
> case KVM_CAP_USER_MEMORY:
> case KVM_CAP_DESTROY_MEMORY_REGION_WORKS:
> case KVM_CAP_JOIN_MEMORY_REGIONS_WORKS:
> + case KVM_CAP_SET_BOOT_CPU_ID:
> return 1;
> #ifdef CONFIG_HAVE_KVM_IRQCHIP
> case KVM_CAP_IRQ_ROUTING:
>
Predicate on HAVE_KVM_IRQCHIP (or a new symbol if it turns out it's more
appropriate).
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2009-06-08 11:23 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-08 9:32 [PATCH 0/4] decouple vcpu index from apic id Gleb Natapov
2009-06-08 9:32 ` [PATCH 1/4] Introduce kvm_vcpu_is_bsp() function Gleb Natapov
2009-06-08 11:20 ` Avi Kivity
2009-06-08 16:53 ` Hollis Blanchard
2009-06-08 16:57 ` Avi Kivity
2009-06-09 1:00 ` Zhang, Xiantao
2009-06-09 3:35 ` Avi Kivity
2009-06-08 9:32 ` [PATCH 2/4] Use pointer to vcpu instead of vcpu_id in timer code Gleb Natapov
2009-06-08 9:32 ` [PATCH 3/4] Break dependency between vcpu index in vcpus array and vcpu_id Gleb Natapov
2009-06-08 11:23 ` Avi Kivity [this message]
2009-06-08 9:32 ` [PATCH 4/4] Use macro to iterate over vcpus Gleb Natapov
2009-06-08 11:25 ` [PATCH 0/4] decouple vcpu index from apic id Avi Kivity
-- strict thread matches above, loose matches on Subject: below --
2009-06-09 2:30 Zhang, Xiantao
2009-06-09 2:30 ` Zhang, Xiantao
2009-06-09 5:26 ` Gleb Natapov
2009-06-09 5:26 ` Gleb Natapov
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=4A2CF4A1.2030603@redhat.com \
--to=avi@redhat.com \
--cc=gleb@redhat.com \
--cc=kvm@vger.kernel.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.