From: Sheng Yang <sheng@linux.intel.com>
To: Gleb Natapov <gleb@redhat.com>
Cc: avi@redhat.com, kvm@vger.kernel.org
Subject: Re: [PATCH] use bitmap ops on a bitmap instead of bit ops
Date: Fri, 27 Feb 2009 11:19:09 +0800 [thread overview]
Message-ID: <200902271119.12359.sheng@linux.intel.com> (raw)
In-Reply-To: <20090226130339.GG8810@redhat.com>
On Thursday 26 February 2009 21:03:39 Gleb Natapov wrote:
> And don't zero bitmap twice. Assume that caller zeros it.
>
> Signed-off-by: Gleb Natapov <gleb@redhat.com>
> diff --git a/virt/kvm/ioapic.c b/virt/kvm/ioapic.c
> index 7c2cb2b..21627b9 100644
> --- a/virt/kvm/ioapic.c
> +++ b/virt/kvm/ioapic.c
> @@ -170,12 +170,11 @@ void kvm_ioapic_get_delivery_bitmask(struct
> kvm_ioapic *ioapic, u8 dest,
>
> ioapic_debug("dest %d dest_mode %d\n", dest, dest_mode);
>
Hi Gleb
> - *mask = 0;
I think the caller should not assume anything about the output, so let
function itself do the clean is better. (however, not in this way for "mask"
should be KVM_MAX_VCPUS long.)
And, I found some other things are not proper after looking back code, I would
send a patch to fix it (deliver_bitmask in kvm_get_intr_delivery_bitmask).
> if (dest_mode == 0) { /* Physical mode. */
> if (dest == 0xFF) { /* Broadcast. */
> for (i = 0; i < KVM_MAX_VCPUS; ++i)
> if (kvm->vcpus[i] && kvm->vcpus[i]->arch.apic)
> - *mask |= 1 << i;
> + __set_bit(i, *mask);
Should be __set_bit(i, mask)?
--
regards
Yang, Sheng
> return;
> }
> for (i = 0; i < KVM_MAX_VCPUS; ++i) {
> @@ -184,7 +183,7 @@ void kvm_ioapic_get_delivery_bitmask(struct kvm_ioapic
> *ioapic, u8 dest, continue;
> if (kvm_apic_match_physical_addr(vcpu->arch.apic, dest)) {
> if (vcpu->arch.apic)
> - *mask = 1 << i;
> + __set_bit(i, *mask);
> break;
> }
> }
> @@ -195,7 +194,7 @@ void kvm_ioapic_get_delivery_bitmask(struct kvm_ioapic
> *ioapic, u8 dest, continue;
> if (vcpu->arch.apic &&
> kvm_apic_match_logical_addr(vcpu->arch.apic, dest))
> - *mask |= 1 << vcpu->vcpu_id;
> + __set_bit(i, *mask);
> }
> ioapic_debug("mask %x\n", *mask);
> }
> --
> Gleb.
next prev parent reply other threads:[~2009-02-27 3:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-26 13:03 [PATCH] use bitmap ops on a bitmap instead of bit ops Gleb Natapov
2009-02-27 3:19 ` Sheng Yang [this message]
2009-02-27 13:26 ` Gleb Natapov
2009-03-02 7:12 ` Sheng Yang
2009-03-03 1:28 ` Sheng Yang
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=200902271119.12359.sheng@linux.intel.com \
--to=sheng@linux.intel.com \
--cc=avi@redhat.com \
--cc=gleb@redhat.com \
--cc=kvm@vger.kernel.org \
/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.