[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] [PATCH 2/3] qemu-error: make use of {error, warn}_repor
From: |
Cornelia Huck |
Subject: |
Re: [Qemu-devel] [PATCH 2/3] qemu-error: make use of {error, warn}_report_once_cond |
Date: |
Wed, 29 Aug 2018 18:23:19 +0200 |
On Wed, 29 Aug 2018 18:12:32 +0200
Markus Armbruster <address@hidden> wrote:
> Cornelia Huck <address@hidden> writes:
>
> > {error,warn}_report_once() are a special case of the new functions
> > and can simply switch to them.
> >
> > Signed-off-by: Cornelia Huck <address@hidden>
> > ---
> > include/qemu/error-report.h | 10 ++--------
> > 1 file changed, 2 insertions(+), 8 deletions(-)
> >
> > diff --git a/include/qemu/error-report.h b/include/qemu/error-report.h
> > index d2a6515e68..4e4c0e757c 100644
> > --- a/include/qemu/error-report.h
> > +++ b/include/qemu/error-report.h
> > @@ -58,10 +58,7 @@ void warn_report_once_cond(bool *printed, const char
> > *fmt, ...)
> > static bool print_once_; \
> > bool ret_print_once_ = !print_once_; \
> > \
> > - if (!print_once_) { \
> > - print_once_ = true; \
> > - error_report(fmt, ##__VA_ARGS__); \
> > - } \
> > + error_report_once_cond(&print_once_, fmt, ##__VA_ARGS__); \
> > unlikely(ret_print_once_); \
> > })
> >
> > @@ -74,10 +71,7 @@ void warn_report_once_cond(bool *printed, const char
> > *fmt, ...)
> > static bool print_once_; \
> > bool ret_print_once_ = !print_once_; \
> > \
> > - if (!print_once_) { \
> > - print_once_ = true; \
> > - warn_report(fmt, ##__VA_ARGS__); \
> > - } \
> > + warn_report_once_cond(&print_once_, fmt, ##__VA_ARGS__); \
> > unlikely(ret_print_once_); \
> > })
>
> Hmm. The macros return a value, while the functions do not. Doesn't
> this contradict the commit message's claim the macros are รค special case
> of the new functions"?
>
> If you make the functions return the value, too, the macros become
> simpler. Moving complexity from macros to functions feels like a good
> deal, even when it's just a little bit of complexity like here.
Reducing macro complexity is a good idea, agreed.
Thanks for looking!
- [Qemu-devel] [PATCH 0/3] qemu-error: advanced report_once handling, Cornelia Huck, 2018/08/28
- [Qemu-devel] [PATCH 1/3] qemu-error: add {error, warn}_report_once_cond, Cornelia Huck, 2018/08/28
- [Qemu-devel] [PATCH 3/3] vfio-ccw: switch to warn_report_once_cond(), Cornelia Huck, 2018/08/28
- [Qemu-devel] [PATCH 2/3] qemu-error: make use of {error, warn}_report_once_cond, Cornelia Huck, 2018/08/28
- Re: [Qemu-devel] [PATCH 0/3] qemu-error: advanced report_once handling, Markus Armbruster, 2018/08/29