kvm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: "Radim Krčmář" <rkrcmar@redhat.com>,
	"Suravee Suthikulpanit" <Suravee.Suthikulpanit@amd.com>
Cc: joro@8bytes.org, bp@alien8.de, gleb@kernel.org,
	alex.williamson@redhat.com, kvm@vger.kernel.org,
	linux-kernel@vger.kernel.org, wei@redhat.com,
	sherry.hurwitz@amd.com
Subject: Re: [PART1 RFC v4 08/11] svm: Add VMEXIT handlers for AVIC
Date: Wed, 13 Apr 2016 00:29:08 +0200	[thread overview]
Message-ID: <570D76B4.1030703@redhat.com> (raw)
In-Reply-To: <20160412162245.GD6762@potion.brq.redhat.com>



On 12/04/2016 18:22, Radim Krčmář wrote:
>> > +
>> > +		if (apic_id > 4 || cluster_id >= 0xf)
>> > +			return NULL;
>> > +		index = (cluster_id << 2) + apic_id;
> ffs(apic_id), because 'apic_id' must be compacted into 2 bits.
> 

ffs(apic_id)-1 actually.

Thanks for the review, Radim.

Paolo

  reply	other threads:[~2016-04-12 22:29 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-07  8:20 [PART1 RFC v4 00/11] KVM: x86: Introduce SVM AVIC support Suravee Suthikulpanit
2016-04-07  8:20 ` [PART1 RFC v4 01/11] KVM: x86: Misc LAPIC changes to expose helper functions Suravee Suthikulpanit
2016-04-11 20:34   ` Radim Krčmář
2016-04-18 19:57     ` Suravee Suthikulpanit
2016-04-18 20:29       ` Suravee Suthikulpanit
2016-04-07  8:20 ` [PART1 RFC v4 02/11] KVM: x86: Introducing kvm_x86_ops VM init/uninit hooks Suravee Suthikulpanit
2016-04-11 20:49   ` Radim Krčmář
2016-04-12 21:55     ` Paolo Bonzini
2016-04-18 22:01       ` Suravee Suthikulpanit
2016-04-18 20:40     ` Suravee Suthikulpanit
2016-04-07  8:20 ` [PART1 RFC v4 03/11] KVM: x86: Introducing kvm_x86_ops VCPU blocking/unblocking hooks Suravee Suthikulpanit
2016-04-07  8:20 ` [PART1 RFC v4 04/11] KVM: split kvm_vcpu_wake_up from kvm_vcpu_kick Suravee Suthikulpanit
2016-04-07  8:20 ` [PART1 RFC v4 05/11] svm: Introduce new AVIC VMCB registers Suravee Suthikulpanit
2016-04-07  8:20 ` [PART1 RFC v4 06/11] KVM: x86: Detect and Initialize AVIC support Suravee Suthikulpanit
2016-04-11 20:48   ` Radim Krčmář
2016-04-12 21:54     ` Paolo Bonzini
2016-04-07  8:20 ` [PART1 RFC v4 07/11] svm: Add interrupt injection via AVIC Suravee Suthikulpanit
2016-04-11 20:52   ` Radim Krčmář
2016-04-07  8:20 ` [PART1 RFC v4 08/11] svm: Add VMEXIT handlers for AVIC Suravee Suthikulpanit
2016-04-12 16:22   ` Radim Krčmář
2016-04-12 22:29     ` Paolo Bonzini [this message]
2016-04-13 12:37       ` Radim Krčmář
2016-04-28 22:08     ` Suravee Suthikulanit
2016-04-29 14:56       ` Radim Krčmář
2016-04-07  8:20 ` [PART1 RFC v4 09/11] svm: Do not expose x2APIC when enable AVIC Suravee Suthikulpanit
2016-04-11 20:54   ` Radim Krčmář
2016-04-12 22:09     ` Paolo Bonzini
2016-04-07  8:20 ` [PART1 RFC v4 10/11] svm: Do not intercept CR8 " Suravee Suthikulpanit
2016-04-12 14:18   ` Radim Krčmář
2016-04-12 22:26     ` Paolo Bonzini
2016-04-07  8:20 ` [PART1 RFC v4 11/11] svm: Manage vcpu load/unload " Suravee Suthikulpanit
2016-04-12 14:34   ` Radim Krčmář

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=570D76B4.1030703@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=Suravee.Suthikulpanit@amd.com \
    --cc=alex.williamson@redhat.com \
    --cc=bp@alien8.de \
    --cc=gleb@kernel.org \
    --cc=joro@8bytes.org \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rkrcmar@redhat.com \
    --cc=sherry.hurwitz@amd.com \
    --cc=wei@redhat.com \
    /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).