All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Hildenbrand <david@redhat.com>
To: "Radim Krčmář" <rkrcmar@redhat.com>,
	linux-kernel@vger.kernel.org, kvm@vger.kernel.org
Cc: Paolo Bonzini <pbonzini@redhat.com>, Igor Mammedov <imammedo@redhat.com>
Subject: Re: [PATCH v3 2/4] KVM: x86: replace kvm_apic_id with kvm_{x,x2}apic_id
Date: Fri, 16 Dec 2016 16:41:49 +0100	[thread overview]
Message-ID: <751674f1-6085-575a-55d2-bf0b11a3ce0d@redhat.com> (raw)
In-Reply-To: <20161215170648.15714-3-rkrcmar@redhat.com>

Am 15.12.2016 um 18:06 schrieb Radim Krčmář:
> There were three calls sites:
>  - recalculate_apic_map and kvm_apic_match_physical_addr, where it would
>    only complicate implementation of x2APIC hotplug;
>  - in apic_debug, where it was still somewhat preserved, but keeping the
>    old function just for apic_debug was not worth it
>
> Signed-off-by: Radim Krčmář <rkrcmar@redhat.com>

Reviewed-by: David Hildenbrand <david@redhat.com>


-- 

David

  reply	other threads:[~2016-12-16 15:42 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-15 17:06 [PATCH v3 0/4] KVM: x86: allow hotplug of VCPU with APIC ID over 0xff Radim Krčmář
2016-12-15 17:06 ` [PATCH v3 1/4] KVM: x86: use delivery to self in hyperv synic Radim Krčmář
2016-12-15 17:06 ` [PATCH v3 2/4] KVM: x86: replace kvm_apic_id with kvm_{x,x2}apic_id Radim Krčmář
2016-12-16 15:41   ` David Hildenbrand [this message]
2016-12-15 17:06 ` [PATCH v3 3/4] KVM: x86: make interrupt delivery fast and slow path behave the same Radim Krčmář
2016-12-16 16:41   ` David Hildenbrand
2016-12-16 16:53     ` Paolo Bonzini
2016-12-16 17:07       ` [PATCH v4 " Radim Krčmář
2016-12-19 14:57         ` David Hildenbrand
2016-12-15 17:06 ` [PATCH v3 4/4] KVM: x86: allow hotplug of VCPU with APIC ID over 0xff Radim Krčmář
2016-12-16 16:48   ` David Hildenbrand

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=751674f1-6085-575a-55d2-bf0b11a3ce0d@redhat.com \
    --to=david@redhat.com \
    --cc=imammedo@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pbonzini@redhat.com \
    --cc=rkrcmar@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 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.