1. 11 12月, 2019 1 次提交
  2. 22 11月, 2019 1 次提交
    • D
      util: consolidate on one free callback for hash data · bc7e7291
      Daniel P. Berrangé 提交于
      This previous commit introduced a simpler free callback for
      hash data with only 1 arg, the value to free:
      
        commit 49288fac
        Author: Peter Krempa <pkrempa@redhat.com>
        Date:   Wed Oct 9 15:26:37 2019 +0200
      
          util: hash: Add possibility to use simpler data free function in virHash
      
      It missed two functions in the hash table code which need
      to call the alternate data free function, virHashRemoveEntry
      and virHashRemoveSet.
      
      After the previous patch though, there is no code that
      makes functional use of the 2nd key arg in the data
      free function. There is merely one log message that can
      be dropped.
      
      We can thus purge the current virHashDataFree callback
      entirely, and rename virHashDataFreeSimple to replace
      it.
      Reviewed-by: NMichal Privoznik <mprivozn@redhat.com>
      Signed-off-by: NDaniel P. Berrangé <berrange@redhat.com>
      bc7e7291
  3. 13 11月, 2019 1 次提交
    • J
      locking: fix build with older sanlock · 54dd0938
      Ján Tomko 提交于
      ../../src/locking/lock_driver_sanlock.c:106:17: error: incompatible pointer types
      assigning to 'char **' from 'char *' [-Werror,-Wincompatible-pointer-types]
              message = g_strdup_printf(_("sanlock error %d"), err);
                      ^ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
      
      Fixes: b1d58418Signed-off-by: NJán Tomko <jtomko@redhat.com>
      54dd0938
  4. 12 11月, 2019 1 次提交
  5. 11 11月, 2019 1 次提交
  6. 09 11月, 2019 3 次提交
  7. 25 10月, 2019 1 次提交
  8. 23 10月, 2019 1 次提交
  9. 21 10月, 2019 2 次提交
  10. 18 10月, 2019 2 次提交
    • D
      util: drop support for stack traces with logging · 9b80e0c1
      Daniel P. Berrangé 提交于
      The log filters have supported the use of a "+" before the source match
      string to request that a stack trace be emitted for every log message:
      
        commit 54856395
        Author: Daniel P. Berrange <berrange@redhat.com>
        Date:   Wed May 9 15:18:56 2012 +0100
      
          Allow stack traces to be included with log messages
      
          Sometimes it is useful to see the callpath for log messages.
          This change enhances the log filter syntax so that stack traces
          can be show by setting '1:+NAME' instead of '1:NAME'.
      
      With the huge & ever increasing number of logging statements per file,
      this will be incredibly verbose and have a major performance penalty.
      This makes the feature impractical to use widely and as such it is not
      worth the code maint cost.
      
      Removing this seldom used feature allows us to drop the 'execinfo'
      module in gnulib which provides the backtrace() function which doesn't
      exist on non-Linux.
      
      Users who want to get stack traces of parts of libvirt can use GDB,
      or systemtap for live tracing with minimal perf impact.
      Reviewed-by: NJán Tomko <jtomko@redhat.com>
      Signed-off-by: NDaniel P. Berrangé <berrange@redhat.com>
      9b80e0c1
    • D
      build: fix use of $(AUG_GENTEST) as a dependency · b36b20a1
      Daniel P. Berrangé 提交于
      The use of $(AUG_GENTEST) as a dependency in the makefiles is
      a problem because this was assumed to be the filename of the
      script, but is in fact a full shell command line.
      
      Split it into two variables, so it can be correctly used for
      dependencies.
      Reviewed-by: NJán Tomko <jtomko@redhat.com>
      Signed-off-by: NDaniel P. Berrangé <berrange@redhat.com>
      b36b20a1
  11. 16 10月, 2019 2 次提交
  12. 15 10月, 2019 2 次提交
  13. 14 10月, 2019 2 次提交
    • D
      build: remove use of usleep gnulib module in favour of g_usleep · 27cb4c1a
      Daniel P. Berrangé 提交于
      The usleep function was missing on older mingw versions, but we can rely
      on it existing everywhere these days. It may only support times upto 1
      second in duration though, so we'll prefer to use g_usleep instead.
      
      The commandhelper program is not changed since that can't link to glib.
      Fortunately it doesn't need to build on Windows platforms either.
      Reviewed-by: NJán Tomko <jtomko@redhat.com>
      Signed-off-by: NDaniel P. Berrangé <berrange@redhat.com>
      27cb4c1a
    • D
      build: link to glib library · cfbe9f12
      Daniel P. Berrangé 提交于
      Add the main glib.h to internal.h so that all common code can use it.
      
      Historically glib allowed applications to register an alternative
      memory allocator, so mixing g_malloc/g_free with malloc/free was not
      safe.
      
      This was feature was dropped in 2.46.0 with:
      
            commit 3be6ed60aa58095691bd697344765e715a327fc1
            Author: Alexander Larsson <alexl@redhat.com>
            Date:   Sat Jun 27 18:38:42 2015 +0200
      
              Deprecate and drop support for memory vtables
      
      Applications are still encourged to match g_malloc/g_free, but it is no
      longer a mandatory requirement for correctness, just stylistic. This is
      explicitly clarified in
      
          commit 1f24b36607bf708f037396014b2cdbc08d67b275
          Author: Daniel P. Berrangé <berrange@redhat.com>
          Date:   Thu Sep 5 14:37:54 2019 +0100
      
              gmem: clarify that g_malloc always uses the system allocator
      
      Applications can still use custom allocators in general, but they must
      do this by linking to a library that replaces the core malloc/free
      implemenentation entirely, instead of via a glib specific call.
      
      This means that libvirt does not need to be concerned about use of
      g_malloc/g_free causing an ABI change in the public libary, and can
      avoid memory copying when talking to external libraries.
      
      This patch probes for glib, which provides the foundation layer with
      a collection of data structures, helper APIs, and platform portability
      logic.
      
      Later patches will introduce linkage to gobject which provides the
      object type system, built on glib, and gio which providing objects
      for various interesting tasks, most notably including DBus client
      and server support and portable sockets APIs, but much more too.
      Signed-off-by: NDaniel P. Berrangé <berrange@redhat.com>
      cfbe9f12
  14. 19 9月, 2019 1 次提交
  15. 10 9月, 2019 2 次提交
  16. 27 8月, 2019 4 次提交
  17. 09 8月, 2019 8 次提交
  18. 19 7月, 2019 1 次提交
  19. 12 7月, 2019 3 次提交
  20. 11 7月, 2019 1 次提交