From: Paolo Bonzini <pbonzini@redhat.com>
To: qemu-devel@nongnu.org
Cc: Stefan Weil <sw@weilnetz.de>, Paolo Bonzini <pbonzini@redhat.com>
Subject: [Qemu-devel] [PULL 01/15] target-i386: Remove unused data from local array
Date: Tue, 13 May 2014 14:57:10 +0200 [thread overview]
Message-ID: <1399985844-788-2-git-send-email-pbonzini@redhat.com> (raw)
In-Reply-To: <1399985844-788-1-git-send-email-pbonzini@redhat.com>
From: Stefan Weil <sw@weilnetz.de>
Signed-off-by: Stefan Weil <sw@weilnetz.de>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
---
target-i386/kvm.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/target-i386/kvm.c b/target-i386/kvm.c
index 4389959..d17eea3 100644
--- a/target-i386/kvm.c
+++ b/target-i386/kvm.c
@@ -130,14 +130,13 @@ static const struct kvm_para_features {
{ KVM_CAP_NOP_IO_DELAY, KVM_FEATURE_NOP_IO_DELAY },
{ KVM_CAP_PV_MMU, KVM_FEATURE_MMU_OP },
{ KVM_CAP_ASYNC_PF, KVM_FEATURE_ASYNC_PF },
- { -1, -1 }
};
static int get_para_features(KVMState *s)
{
int i, features = 0;
- for (i = 0; i < ARRAY_SIZE(para_features) - 1; i++) {
+ for (i = 0; i < ARRAY_SIZE(para_features); i++) {
if (kvm_check_extension(s, para_features[i].cap)) {
features |= (1 << para_features[i].feature);
}
--
1.8.3.1
next prev parent reply other threads:[~2014-05-13 12:57 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-13 12:57 [Qemu-devel] [PULL 00/15] KVM patches for 2014-05-13 Paolo Bonzini
2014-05-13 12:57 ` Paolo Bonzini [this message]
2014-05-13 12:57 ` [Qemu-devel] [PULL 02/15] kvm: make one_reg helpers available for everyone Paolo Bonzini
2014-05-13 12:57 ` [Qemu-devel] [PULL 03/15] pci-assign: Fix a bug when map MSI-X table memory failed Paolo Bonzini
2014-05-13 12:57 ` [Qemu-devel] [PULL 04/15] pci-assign: limit # of msix vectors Paolo Bonzini
2014-05-13 12:57 ` [Qemu-devel] [PULL 05/15] target-i386: set eflags prior to calling svm_load_seg_cache() in svm_helper.c Paolo Bonzini
2014-05-13 12:57 ` [Qemu-devel] [PULL 06/15] target-i386: set eflags and cr0 prior to calling cpu_x86_load_seg_cache() in smm_helper.c Paolo Bonzini
2014-05-13 12:57 ` [Qemu-devel] [PULL 07/15] target-i386: set eflags prior to calling cpu_x86_load_seg_cache() in seg_helper.c Paolo Bonzini
2014-05-13 12:57 ` [Qemu-devel] [PULL 08/15] target-i386: the x86 CPL is stored in CS.selector - auto update hflags accordingly Paolo Bonzini
2014-05-13 12:57 ` [Qemu-devel] [PULL 09/15] kvm: reset state from the CPU's reset method Paolo Bonzini
2014-05-13 12:57 ` [Qemu-devel] [PULL 10/15] kvm: forward INIT signals coming from the chipset Paolo Bonzini
2014-05-13 12:57 ` [Qemu-devel] [PULL 11/15] target-i386: fix set of registers zeroed on reset Paolo Bonzini
2014-05-13 12:57 ` [Qemu-devel] [PULL 12/15] target-i386: preserve FPU and MSR state on INIT Paolo Bonzini
2014-05-13 12:57 ` [Qemu-devel] [PULL 13/15] apic: do not accept SIPI on the bootstrap processor Paolo Bonzini
2014-05-13 12:57 ` [Qemu-devel] [PULL 14/15] cpu: make CPU_INTERRUPT_RESET available on all targets Paolo Bonzini
2014-05-13 12:57 ` [Qemu-devel] [PULL 15/15] pc: port 92 reset requires a low->high transition Paolo Bonzini
2014-05-15 15:27 ` [Qemu-devel] [PULL 00/15] KVM patches for 2014-05-13 Peter Maydell
2014-05-15 16:54 ` Andreas Färber
2014-05-15 17:08 ` Paolo Bonzini
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=1399985844-788-2-git-send-email-pbonzini@redhat.com \
--to=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=sw@weilnetz.de \
/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).