kvm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Gleb Natapov <gleb@redhat.com>
Cc: kvm@vger.kernel.org
Subject: Re: [PATCHv2 0/4] decouple vcpu index from apic id
Date: Wed, 10 Jun 2009 18:41:39 +0300	[thread overview]
Message-ID: <4A2FD433.1000204@redhat.com> (raw)
In-Reply-To: <1244552189-17299-1-git-send-email-gleb@redhat.com>

Gleb Natapov wrote:
> Currently vcpu_id is used as an index into vcpus array and as apic id
> on x86.  This is incorrect since apic ids not have to be continuous
> (they can also encode cpu hierarchy information) and may have values
> bigger then vcpu array in case of x2apic. This series removes use of
> vcpu_id as vcpus array index. Each architecture may use it how it sees
> fit. x86 uses it as apic id.
>
> v2:
>   remove online_vcpus from ia64 in patch 3/4
>   introduce KVM_APIC_ARCHITECTURE config option
>
> Gleb Natapov (4):
>   Introduce kvm_vcpu_is_bsp() function.
>   Use pointer to vcpu instead of vcpu_id in timer code.
>   Break dependency between vcpu index in vcpus array and vcpu_id.
>   Use macro to iterate over vcpus.
>
>   

Applied, thanks.

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


      parent reply	other threads:[~2009-06-10 15:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-09 12:56 [PATCHv2 0/4] decouple vcpu index from apic id Gleb Natapov
2009-06-09 12:56 ` [PATCHv2 1/4] Introduce kvm_vcpu_is_bsp() function Gleb Natapov
2009-06-09 12:56 ` [PATCHv2 2/4] Use pointer to vcpu instead of vcpu_id in timer code Gleb Natapov
2009-06-09 12:56 ` [PATCHv2 3/4] Break dependency between vcpu index in vcpus array and vcpu_id Gleb Natapov
2009-06-09 12:56 ` [PATCHv2 4/4] Use macro to iterate over vcpus Gleb Natapov
2009-06-10 15:41 ` Avi Kivity [this message]

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=4A2FD433.1000204@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).