From: Wanpeng Li <kernellwp@gmail.com> To: qemu-devel@nongnu.org, kvm@vger.kernel.org Cc: "Paolo Bonzini" <pbonzini@redhat.com>, "Radim Krčmář" <rkrcmar@redhat.com>, "Eduardo Habkost" <ehabkost@redhat.com> Subject: [PATCH] target-i386: adds PV_SCHED_YIELD CPUID feature bit Date: Wed, 10 Jul 2019 15:50:44 +0800 [thread overview] Message-ID: <1562745044-7838-1-git-send-email-wanpengli@tencent.com> (raw) From: Wanpeng Li <wanpengli@tencent.com> Adds PV_SCHED_YIELD CPUID feature bit. Cc: Eduardo Habkost <ehabkost@redhat.com> Cc: Paolo Bonzini <pbonzini@redhat.com> Cc: Radim Krčmář <rkrcmar@redhat.com> Signed-off-by: Wanpeng Li <wanpengli@tencent.com> --- Note: kvm part is merged v1 -> v2: * use bit 13 instead of bit 12 since bit 12 has user now target/i386/cpu.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/target/i386/cpu.c b/target/i386/cpu.c index 5f07d68..f4c4b6b 100644 --- a/target/i386/cpu.c +++ b/target/i386/cpu.c @@ -902,7 +902,7 @@ static FeatureWordInfo feature_word_info[FEATURE_WORDS] = { "kvmclock", "kvm-nopiodelay", "kvm-mmu", "kvmclock", "kvm-asyncpf", "kvm-steal-time", "kvm-pv-eoi", "kvm-pv-unhalt", NULL, "kvm-pv-tlb-flush", NULL, "kvm-pv-ipi", - NULL, NULL, NULL, NULL, + NULL, "kvm-pv-sched-yield', NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, "kvmclock-stable-bit", NULL, NULL, NULL, -- 2.7.4
WARNING: multiple messages have this Message-ID (diff)
From: Wanpeng Li <kernellwp@gmail.com> To: qemu-devel@nongnu.org, kvm@vger.kernel.org Cc: "Paolo Bonzini" <pbonzini@redhat.com>, "Eduardo Habkost" <ehabkost@redhat.com>, "Radim Krčmář" <rkrcmar@redhat.com> Subject: [Qemu-devel] [PATCH] target-i386: adds PV_SCHED_YIELD CPUID feature bit Date: Wed, 10 Jul 2019 15:50:44 +0800 [thread overview] Message-ID: <1562745044-7838-1-git-send-email-wanpengli@tencent.com> (raw) From: Wanpeng Li <wanpengli@tencent.com> Adds PV_SCHED_YIELD CPUID feature bit. Cc: Eduardo Habkost <ehabkost@redhat.com> Cc: Paolo Bonzini <pbonzini@redhat.com> Cc: Radim Krčmář <rkrcmar@redhat.com> Signed-off-by: Wanpeng Li <wanpengli@tencent.com> --- Note: kvm part is merged v1 -> v2: * use bit 13 instead of bit 12 since bit 12 has user now target/i386/cpu.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/target/i386/cpu.c b/target/i386/cpu.c index 5f07d68..f4c4b6b 100644 --- a/target/i386/cpu.c +++ b/target/i386/cpu.c @@ -902,7 +902,7 @@ static FeatureWordInfo feature_word_info[FEATURE_WORDS] = { "kvmclock", "kvm-nopiodelay", "kvm-mmu", "kvmclock", "kvm-asyncpf", "kvm-steal-time", "kvm-pv-eoi", "kvm-pv-unhalt", NULL, "kvm-pv-tlb-flush", NULL, "kvm-pv-ipi", - NULL, NULL, NULL, NULL, + NULL, "kvm-pv-sched-yield', NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, "kvmclock-stable-bit", NULL, NULL, NULL, -- 2.7.4
next reply other threads:[~2019-07-10 7:51 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-07-10 7:50 Wanpeng Li [this message] 2019-07-10 7:50 ` [Qemu-devel] [PATCH] target-i386: adds PV_SCHED_YIELD CPUID feature bit Wanpeng Li 2019-07-10 8:01 ` no-reply 2019-07-10 8:01 ` no-reply 2019-07-10 8:06 ` no-reply 2019-07-10 8:06 ` no-reply -- strict thread matches above, loose matches on Subject: below -- 2019-05-27 10:46 Wanpeng Li
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=1562745044-7838-1-git-send-email-wanpengli@tencent.com \ --to=kernellwp@gmail.com \ --cc=ehabkost@redhat.com \ --cc=kvm@vger.kernel.org \ --cc=pbonzini@redhat.com \ --cc=qemu-devel@nongnu.org \ --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: linkBe 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.