[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] Re: [RFC][PATCH v5 01/21] Move code related to fd handl
From: |
Jes Sorensen |
Subject: |
Re: [Qemu-devel] Re: [RFC][PATCH v5 01/21] Move code related to fd handlers into utility functions |
Date: |
Tue, 07 Dec 2010 16:02:03 +0100 |
User-agent: |
Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.12) Gecko/20101103 Fedora/1.0-0.33.b2pre.fc14 Lightning/1.0b3pre Thunderbird/3.1.6 |
On 12/07/10 15:48, Michael Roth wrote:
> On 12/07/2010 07:31 AM, Jes Sorensen wrote:
>> On 12/03/10 19:03, Michael Roth wrote:
>>> This allows us to implement an i/o loop outside of vl.c that can
>>> interact with objects that use qemu_set_fd_handler()
>>>
>>> Signed-off-by: Michael Roth<address@hidden>
>>
>> This commit message really tells us nothing. Please be more specific
>> about what is in the commit.
>>
>
> Currently, in qemu, the virtagent client/server functionality is driven
> by vl.c:main_loop_wait(), which implements a select() loop that kicks
> off handlers registered for various FDs/events via qemu_set_fd_handler().
>
> To share the code with the agent, qemu-va.c, I re-implemented this i/o
> loop to do same thing, along with vl.c:qemu_set_fd_handler*() and
> friends. It was big nasty copy/paste job and I think most of the
> reviewers agreed that the i/o loop code should be shared.
>
> This commit moves the shared code into back-end utility functions that
> get called by vl.c:qemu_set_fd_handler()/qemu_process_fd_handlers() and
> friends for qemu, and by
> qemu-tools.c:qemu_set_fd_handler()/qemu_process_fd_handlers() for tools.
>
> So now to interact with code that uses qemu_set_fd_handler() you can
> built a select() loop around these utility functions.
Please put some of this in the commit message.
>> I am not happy with this addition of numbers to these functions, it
>> doesn't tell us why we have a 3 and how it differs from 2. If 3 is
>> really the backend for implementing 2, maybe it would be better to name
>> it __qemu_set_fd_handler2() and then have macros/wrappers calling into
>> it.
>
> That was the initial plan, but qemu_set_fd_handler2() is a back-end of
> sorts for qemu_set_fd_handler(), so I was just trying to be consistent
> with the naming. Personally I don't have any objections one way or the
> other.
Anything to avoid qemu_set_fd_handler17() at some point. I think using
__qemu_set_fd_handler() encourages people to modify that code rather
than copy it.
Cheers,
Jes
- [Qemu-devel] [RFC][PATCH v5 00/21] virtagent: host/guest RPC communication agent, Michael Roth, 2010/12/03
- [Qemu-devel] [RFC][PATCH v5 01/21] Move code related to fd handlers into utility functions, Michael Roth, 2010/12/03
- [Qemu-devel] Re: [RFC][PATCH v5 01/21] Move code related to fd handlers into utility functions, Jes Sorensen, 2010/12/07
- Re: [Qemu-devel] Re: [RFC][PATCH v5 01/21] Move code related to fd handlers into utility functions, Michael Roth, 2010/12/07
- Re: [Qemu-devel] Re: [RFC][PATCH v5 01/21] Move code related to fd handlers into utility functions,
Jes Sorensen <=
- Re: [Qemu-devel] Re: [RFC][PATCH v5 01/21] Move code related to fd handlers into utility functions, Stefan Hajnoczi, 2010/12/08
- Re: [Qemu-devel] Re: [RFC][PATCH v5 01/21] Move code related to fd handlers into utility functions, Jes Sorensen, 2010/12/08
- Re: [Qemu-devel] Re: [RFC][PATCH v5 01/21] Move code related to fd handlers into utility functions, Stefan Hajnoczi, 2010/12/08
- Re: [Qemu-devel] Re: [RFC][PATCH v5 01/21] Move code related to fd handlers into utility functions, Jes Sorensen, 2010/12/08
- Re: [Qemu-devel] Re: [RFC][PATCH v5 01/21] Move code related to fd handlers into utility functions, Anthony Liguori, 2010/12/08
[Qemu-devel] [RFC][PATCH v5 04/21] virtagent: transport definitions and job callbacks, Michael Roth, 2010/12/03