linux-kernel.vger.kernel.org archive mirror
 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 1/4] KVM: x86: use delivery to self in hyperv synic
Date: Mon, 5 Dec 2016 15:41:54 +0100	[thread overview]
Message-ID: <bf2c0b2e-7d55-4c6f-a183-646d1f1301b2@redhat.com> (raw)
In-Reply-To: <20161202194401.10038-2-rkrcmar@redhat.com>

Am 02.12.2016 um 20:43 schrieb Radim Krčmář:
> Interrupt to self can sent without knowing the APIC ID.

can _be_ sent?

Looks sane to me.

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

-- 

David

  reply	other threads:[~2016-12-05 14:42 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-02 19:43 [PATCH 0/4] KVM: x86: allow hotplug of VCPU with APIC ID over 0xff Radim Krčmář
2016-12-02 19:43 ` [PATCH 1/4] KVM: x86: use delivery to self in hyperv synic Radim Krčmář
2016-12-05 14:41   ` David Hildenbrand [this message]
2016-12-05 16:03     ` Radim Krčmář
2016-12-02 19:43 ` [PATCH 2/4] KVM: x86: replace kvm_apic_id with kvm_{x,x2}apic_id Radim Krčmář
2016-12-02 19:44 ` [PATCH 3/4] KVM: x86: make interrupt delivery fast and slow path behave the same Radim Krčmář
2016-12-02 19:44 ` [PATCH 4/4] KVM: x86: allow hotplug of VCPU with APIC ID over 0xff Radim Krčmář
2016-12-05 14:37   ` David Hildenbrand
2016-12-05 16:02     ` Radim Krčmář
2016-12-05 18:00       ` David Hildenbrand
2016-12-05 20:57         ` Radim Krčmář
2016-12-06  9:37           ` David Hildenbrand
2016-12-06 12:52             ` Radim Krčmář
2016-12-07 12:03   ` Paolo Bonzini
2016-12-07 15:47     ` 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=bf2c0b2e-7d55-4c6f-a183-646d1f1301b2@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 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).