1. 11 12月, 2019 1 次提交
  2. 12 11月, 2019 1 次提交
  3. 11 11月, 2019 1 次提交
  4. 09 11月, 2019 3 次提交
  5. 23 10月, 2019 1 次提交
  6. 21 10月, 2019 1 次提交
  7. 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
  8. 16 10月, 2019 1 次提交
  9. 15 10月, 2019 2 次提交
  10. 14 10月, 2019 1 次提交
    • 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
  11. 19 9月, 2019 1 次提交
  12. 10 9月, 2019 2 次提交
  13. 27 8月, 2019 3 次提交
  14. 09 8月, 2019 7 次提交
  15. 19 7月, 2019 1 次提交
  16. 12 7月, 2019 4 次提交
  17. 11 7月, 2019 1 次提交
  18. 21 6月, 2019 1 次提交
    • D
      remote: delete the avahi mDNS support · 5a148ce8
      Daniel P. Berrangé 提交于
      Libvirtd has long had integration with avahi for advertising libvirtd
      using mDNS when TCP/TLS listening is enabled. For a long time the
      virt-manager application had support for auto-detecting libvirtds
      on the local network using mDNS, but this was removed last year
      
        commit fc8f8d5d7e3ba80a0771df19cf20e84a05ed2422
        Author: Cole Robinson <crobinso@redhat.com>
        Date:   Sat Oct 6 20:55:31 2018 -0400
      
          connect: Drop avahi support
      
          Libvirtd can advertise itself over avahi. The feature is disabled by
          default though and in practice I hear of no one actually using it
          and frankly I don't think it's all that useful
      
          The 'Open Connection' wizard has a disproportionate amount of code
          devoted to this feature, but I don't think it's useful or worth
          maintaining, so let's drop it
      
      I've never heard of any other applications having support for using
      mDNS to detect libvirtd instances. Though it is theoretically possible
      something exists out there, it is clearly going to be a niche use case
      in the virt ecosystem as a whole.
      
      By removing avahi integration we can cut down the dependency chain for
      the basic libvirtd install and reduce our code maint burden.
      Reviewed-by: NJán Tomko <jtomko@redhat.com>
      Signed-off-by: NDaniel P. Berrangé <berrange@redhat.com>
      5a148ce8
  19. 13 6月, 2019 1 次提交
  20. 21 5月, 2019 1 次提交
  21. 17 5月, 2019 1 次提交
    • D
      src: don't statically link code that's already in libvirt.so · e5df4ede
      Daniel P. Berrangé 提交于
      Various binaries are statically linking to libvirt_util.la and
      other intermediate libraries we build. These intermediate libs
      all get built into the main libvirt.so shared library eventually,
      so we can dynamically link to that instead and reduce the on disk
      footprint.
      
      In libvirt-daemon RPM:
      
                  virtlockd: 1.6 MB -> 153 KB
                   virtlogd: 1.6 MB -> 157 KB
           libvirt_iohelper: 937 KB -> 23 KB
      
      In libvirt-daemon-driver-network RPM:
      
       libvirt_leaseshelper: 940 KB -> 26 KB
      
      In libvirt-daemon-driver-storage-core RPM:
      
         libvirt_parthelper: 926 KB -> 21 KB
      
      IOW, about 5.6 MB total space saving in a build done on Fedora 30
      x86_64 architecture.
      Reviewed-by: NJán Tomko <jtomko@redhat.com>
      Signed-off-by: NDaniel P. Berrangé <berrange@redhat.com>
      e5df4ede
  22. 12 4月, 2019 3 次提交