From: Eduardo Habkost <ehabkost@redhat.com>
To: Wanpeng Li <kernellwp@gmail.com>
Cc: qemu-devel@nongnu.org, kvm@vger.kernel.org,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Radim Krčmář" <rkrcmar@redhat.com>,
"Vitaly Kuznetsov" <vkuznets@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] target-i386: adds PV_SEND_IPI CPUID feature bit
Date: Mon, 2 Jul 2018 18:43:15 -0300 [thread overview]
Message-ID: <20180702214315.GH7451@localhost.localdomain> (raw)
In-Reply-To: <1530526971-1812-1-git-send-email-wanpengli@tencent.com>
On Mon, Jul 02, 2018 at 06:22:51PM +0800, Wanpeng Li wrote:
> From: Wanpeng Li <wanpengli@tencent.com>
>
> Adds PV_SEND_IPI CPUID feature bit.
>
Thanks!
Paolo, Radim: can I assume the bit is already reserved and queue
this patch, or should I wait until the KVM patch is merged into
kvm.git?
--
Eduardo
next prev parent reply other threads:[~2018-07-02 21:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-02 10:22 [Qemu-devel] [PATCH] target-i386: adds PV_SEND_IPI CPUID feature bit Wanpeng Li
2018-07-02 21:43 ` Eduardo Habkost [this message]
2018-07-23 10:58 ` Wanpeng Li
2018-08-07 7:45 ` Wanpeng Li
2018-08-07 10:07 ` Paolo Bonzini
2018-08-07 14:20 ` Eduardo Habkost
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=20180702214315.GH7451@localhost.localdomain \
--to=ehabkost@redhat.com \
--cc=kernellwp@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rkrcmar@redhat.com \
--cc=vkuznets@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).