From: Paolo Bonzini <pbonzini@redhat.com>
To: Gerd Hoffmann <kraxel@redhat.com>, "Michael S. Tsirkin" <mst@redhat.com>
Cc: virtio-dev@lists.oasis-open.org,
open list <linux-kernel@vger.kernel.org>,
ABI/API <linux-api@vger.kernel.org>,
virtualization@lists.linux-foundation.org
Subject: Re: [virtio-dev] Re: [PATCH 1/1] Add virtio-input driver.
Date: Mon, 23 Mar 2015 12:52:36 +0100 [thread overview]
Message-ID: <550FFE84.4060001@redhat.com> (raw)
In-Reply-To: <1427097238.6365.27.camel@nilsson.home.kraxel.org>
On 23/03/2015 08:53, Gerd Hoffmann wrote:
>>>>> > > > > + if (cfg & (1 << (bit % 8)))
>>>>> > > > > + set_bit(bit, bits);
>>>> > > >
>>>> > > > what if not set? does something clear the mask?
>>> > >
>>> > > kzalloc?
>> >
>> > So you are really just reading in array of bytes?
>> > All this set bit trickery is just to convert things from LE?
> Trickery? Just checking each bit from virtio config space, then set it
> in the input layer bitmap. It's a simple stupid loop.
>
> Surely not the most efficient way, but hey, it's not in the hot path and
> I'm sure I'm setting the bits correctly because this uses the standard
> linux kernel bitops.
Use __set_bit though, because set_bit is an atomic operation.
Paolo
>> > At least, this needs a comment explaining what the function does,
>> > and maybe wrap it in a helper like virtio_input_bitmap_copy or
>> > virtio_bitmap_or.
> Can do that, sure.
next prev parent reply other threads:[~2015-03-23 11:52 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1426756391-26585-1-git-send-email-kraxel@redhat.com>
[not found] ` <1426756391-26585-1-git-send-email-kraxel-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2015-03-19 9:13 ` [PATCH 1/1] Add virtio-input driver Gerd Hoffmann
[not found] ` <1426756391-26585-2-git-send-email-kraxel-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2015-03-19 12:27 ` Michael S. Tsirkin
2015-03-20 10:28 ` Gerd Hoffmann
2015-03-21 22:22 ` Michael S. Tsirkin
2015-03-23 7:53 ` Gerd Hoffmann
2015-03-23 11:52 ` Paolo Bonzini [this message]
2015-03-23 13:44 ` Gerd Hoffmann
2015-03-23 13:51 ` Michael S. Tsirkin
2015-03-23 14:27 ` Gerd Hoffmann
[not found] ` <1427120855.27137.55.camel-3OfP5uLMi4C46o+2HkPkLj4oCIwMql/M@public.gmane.org>
2015-03-23 14:54 ` Michael S. Tsirkin
2015-03-23 15:05 ` Gerd Hoffmann
[not found] ` <1427123129.27137.62.camel-3OfP5uLMi4C46o+2HkPkLj4oCIwMql/M@public.gmane.org>
2015-03-23 16:17 ` Cornelia Huck
2015-03-23 18:20 ` Michael S. Tsirkin
2015-03-19 12:29 ` David Herrmann
[not found] ` <CANq1E4TDj4pq3J_BVc=Yuzo5dVR=QcNexVUqaqwjg7Qi5_xX4Q-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-03-19 16:27 ` Dmitry Torokhov
2015-03-19 17:16 ` David Herrmann
2015-03-20 9:54 ` Gerd Hoffmann
2015-03-20 9:48 ` Gerd Hoffmann
[not found] ` <1426844885.32097.36.camel-3OfP5uLMi4C46o+2HkPkLj4oCIwMql/M@public.gmane.org>
2015-03-20 9:55 ` David Herrmann
[not found] ` <CANq1E4QLPSK6NVeEx6yihYPdF-XPpXx4rKv0deHwX+s2RzFHCg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-03-20 10:36 ` Gerd Hoffmann
[not found] ` <1426847799.32097.66.camel-3OfP5uLMi4C46o+2HkPkLj4oCIwMql/M@public.gmane.org>
2015-03-20 10:43 ` David Herrmann
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=550FFE84.4060001@redhat.com \
--to=pbonzini@redhat.com \
--cc=kraxel@redhat.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=virtio-dev@lists.oasis-open.org \
--cc=virtualization@lists.linux-foundation.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 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).