From: Sheng Yang <sheng@linux.intel.com>
To: Marcelo Tosatti <mtosatti@redhat.com>
Cc: Gleb Natapov <gleb@redhat.com>, avi@redhat.com, kvm@vger.kernel.org
Subject: Re: [PATCH] use bitmap ops on a bitmap instead of bit ops
Date: Tue, 3 Mar 2009 09:28:00 +0800 [thread overview]
Message-ID: <200903030928.00971.sheng@linux.intel.com> (raw)
In-Reply-To: <200903021512.01051.sheng@linux.intel.com>
On Monday 02 March 2009 15:12:00 Sheng Yang wrote:
> On Friday 27 February 2009 21:26:58 Gleb Natapov wrote:
> > On Fri, Feb 27, 2009 at 11:19:09AM +0800, Sheng Yang wrote:
> > > > - *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.)
> >
> > Ok. I'll leave it although all callers of the function zeroes bitmask
> > anyway.
> >
> > > 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)?
> >
> > Oh. Here is updated patch:
>
> Thanks. :)
>
> Acked-by: Sheng Yang <sheng@linux.intel.com>
Just a reminder that I have merge this patch into the patch title"[PATCH] KVM:
Merge kvm_ioapic_get_delivery_bitmask into kvm_get_intr_delivery_bitmask" with
Gleb's agreement.
Thanks. :)
--
regards
Yang, Sheng
prev parent reply other threads:[~2009-03-03 1:28 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
2009-02-27 13:26 ` Gleb Natapov
2009-03-02 7:12 ` Sheng Yang
2009-03-03 1:28 ` Sheng Yang [this message]
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=200903030928.00971.sheng@linux.intel.com \
--to=sheng@linux.intel.com \
--cc=avi@redhat.com \
--cc=gleb@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@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