qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Igor Mammedov <imammedo@redhat.com>
To: Steven Sistare <steven.sistare@oracle.com>
Cc: "Jason Zeng" <jason.zeng@linux.intel.com>,
	"Juan Quintela" <quintela@redhat.com>,
	"Eric Blake" <eblake@redhat.com>,
	"Michael S. Tsirkin" <mst@redhat.com>,
	"David Hildenbrand" <david@redhat.com>,
	qemu-devel@nongnu.org,
	"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
	"Zheng Chuan" <zhengchuan@huawei.com>,
	"Alex Williamson" <alex.williamson@redhat.com>,
	"Paolo Bonzini" <pbonzini@redhat.com>,
	"Stefan Hajnoczi" <stefanha@redhat.com>,
	"Marc-André Lureau" <marcandre.lureau@redhat.com>,
	"Daniel P. Berrange" <berrange@redhat.com>,
	"Philippe Mathieu-Daudé" <philmd@redhat.com>,
	"Alex Bennée" <alex.bennee@linaro.org>,
	"Markus Armbruster" <armbru@redhat.com>
Subject: Re: [PATCH V7 10/29] machine: memfd-alloc option
Date: Thu, 10 Mar 2022 17:00:25 +0100	[thread overview]
Message-ID: <20220310170025.33b9f6f0@redhat.com> (raw)
In-Reply-To: <3e0803ef-392a-b863-3474-3f76dcd27ae1@oracle.com>

On Thu, 10 Mar 2022 10:36:08 -0500
Steven Sistare <steven.sistare@oracle.com> wrote:

> On 3/8/2022 2:20 AM, Igor Mammedov wrote:
> > On Tue, 8 Mar 2022 01:50:11 -0500
> > "Michael S. Tsirkin" <mst@redhat.com> wrote:
> >   
> >> On Mon, Mar 07, 2022 at 09:41:44AM -0500, Steven Sistare wrote:  
> >>> On 3/4/2022 5:41 AM, Igor Mammedov wrote:    
> >>>> On Thu, 3 Mar 2022 12:21:15 -0500
> >>>> "Michael S. Tsirkin" <mst@redhat.com> wrote:
> >>>>     
> >>>>> On Wed, Dec 22, 2021 at 11:05:15AM -0800, Steve Sistare wrote:    
> >>>>>> Allocate anonymous memory using memfd_create if the memfd-alloc machine
> >>>>>> option is set.
> >>>>>>
> >>>>>> Signed-off-by: Steve Sistare <steven.sistare@oracle.com>
> >>>>>> ---
> >>>>>>  hw/core/machine.c   | 19 +++++++++++++++++++
> >>>>>>  include/hw/boards.h |  1 +
> >>>>>>  qemu-options.hx     |  6 ++++++
> >>>>>>  softmmu/physmem.c   | 47 ++++++++++++++++++++++++++++++++++++++---------
> >>>>>>  softmmu/vl.c        |  1 +
> >>>>>>  trace-events        |  1 +
> >>>>>>  util/qemu-config.c  |  4 ++++
> >>>>>>  7 files changed, 70 insertions(+), 9 deletions(-)
> >>>>>>
> >>>>>> diff --git a/hw/core/machine.c b/hw/core/machine.c
> >>>>>> index 53a99ab..7739d88 100644
> >>>>>> --- a/hw/core/machine.c
> >>>>>> +++ b/hw/core/machine.c
> >>>>>> @@ -392,6 +392,20 @@ static void machine_set_mem_merge(Object *obj, bool value, Error **errp)
> >>>>>>      ms->mem_merge = value;
> >>>>>>  }
> >>>>>>  
> >>>>>> +static bool machine_get_memfd_alloc(Object *obj, Error **errp)
> >>>>>> +{
> >>>>>> +    MachineState *ms = MACHINE(obj);
> >>>>>> +
> >>>>>> +    return ms->memfd_alloc;
> >>>>>> +}
> >>>>>> +
> >>>>>> +static void machine_set_memfd_alloc(Object *obj, bool value, Error **errp)
> >>>>>> +{
> >>>>>> +    MachineState *ms = MACHINE(obj);
> >>>>>> +
> >>>>>> +    ms->memfd_alloc = value;
> >>>>>> +}
> >>>>>> +
> >>>>>>  static bool machine_get_usb(Object *obj, Error **errp)
> >>>>>>  {
> >>>>>>      MachineState *ms = MACHINE(obj);
> >>>>>> @@ -829,6 +843,11 @@ static void machine_class_init(ObjectClass *oc, void *data)
> >>>>>>      object_class_property_set_description(oc, "mem-merge",
> >>>>>>          "Enable/disable memory merge support");
> >>>>>>  
> >>>>>> +    object_class_property_add_bool(oc, "memfd-alloc",
> >>>>>> +        machine_get_memfd_alloc, machine_set_memfd_alloc);
> >>>>>> +    object_class_property_set_description(oc, "memfd-alloc",
> >>>>>> +        "Enable/disable allocating anonymous memory using memfd_create");
> >>>>>> +
> >>>>>>      object_class_property_add_bool(oc, "usb",
> >>>>>>          machine_get_usb, machine_set_usb);
> >>>>>>      object_class_property_set_description(oc, "usb",
> >>>>>> diff --git a/include/hw/boards.h b/include/hw/boards.h
> >>>>>> index 9c1c190..a57d7a0 100644
> >>>>>> --- a/include/hw/boards.h
> >>>>>> +++ b/include/hw/boards.h
> >>>>>> @@ -327,6 +327,7 @@ struct MachineState {
> >>>>>>      char *dt_compatible;
> >>>>>>      bool dump_guest_core;
> >>>>>>      bool mem_merge;
> >>>>>> +    bool memfd_alloc;
> >>>>>>      bool usb;
> >>>>>>      bool usb_disabled;
> >>>>>>      char *firmware;
> >>>>>> diff --git a/qemu-options.hx b/qemu-options.hx
> >>>>>> index 7d47510..33c8173 100644
> >>>>>> --- a/qemu-options.hx
> >>>>>> +++ b/qemu-options.hx
> >>>>>> @@ -30,6 +30,7 @@ DEF("machine", HAS_ARG, QEMU_OPTION_machine, \
> >>>>>>      "                vmport=on|off|auto controls emulation of vmport (default: auto)\n"
> >>>>>>      "                dump-guest-core=on|off include guest memory in a core dump (default=on)\n"
> >>>>>>      "                mem-merge=on|off controls memory merge support (default: on)\n"
> >>>>>> +    "                memfd-alloc=on|off controls allocating anonymous guest RAM using memfd_create (default: off)\n"      
> >>>>>
> >>>>> Question: are there any disadvantages associated with using
> >>>>> memfd_create? I guess we are using up an fd, but that seems minor.  Any
> >>>>> reason not to set to on by default? maybe with a fallback option to
> >>>>> disable that?    
> >>>
> >>> Old Linux host kernels, circa 4.1, do not support huge pages for shared memory.
> >>> Also, the tunable to enable huge pages for share memory is different than for
> >>> anon memory, so there could be performance loss if it is not set correctly.
> >>>     /sys/kernel/mm/transparent_hugepage/enabled
> >>>     vs
> >>>     /sys/kernel/mm/transparent_hugepage/shmem_enabled    
> >>
> >> I guess we can test this when launching the VM, and select
> >> a good default.
> >>  
> >>> It might make sense to use memfd_create by default for the secondary segments.    
> >>
> >> Well there's also KSM now you mention it.  
> > 
> > then another quest, is there downside to always using memfd_create
> > without any knobs being involved?  
> 
> Lower performance if small pages are used (but Michael suggests qemu could 
> automatically check the tunable and use anon memory instead)
> 
> KSM (same page merging) is not supported for shared memory, so ram_block_add ->
> memory_try_enable_merging will not enable it.
> 
> In both cases, I expect the degradation would be negligible if memfd_create is
> only automatically applied to the secondary segments, which are typically small.
> But, someone's secondary segment could be larger, and it is time consuming to
> prove innocence when someone claims your change caused their performance regression.

Adding David as memory subsystem maintainer, maybe he will a better
idea instead of introducing global knob that would also magically alter 
backends' behavior despite of its their configured settings.



> - Steve
> 
> >>>>> I am concerned that it's actually a kind of memory backend, this flag
> >>>>> seems to instead be closer to the deprecated mem-prealloc. E.g.
> >>>>> it does not work with a mem path, does it?    
> >>>
> >>> One can still define a memory backend with mempath to create the main ram segment,
> >>> though it must be some form of shared to work with live update.  Indeed, I would 
> >>> expect most users to specify an explicit memory backend for it.  The secondary
> >>> segments would still use memfd_create.
> >>>     
> >>>> (mem path and mem-prealloc are transparently aliased to used memory backend
> >>>> if I recall it right.)
> >>>>
> >>>> Steve,
> >>>>
> >>>> For allocating guest RAM, we switched exclusively to using memory-backends
> >>>> including initial guest RAM (-m size option) and we have hostmem-memfd
> >>>> that uses memfd_create() and I'd rather avoid adding random knobs to machine
> >>>> for tweaking how RAM should be allocated, we have memory backends for this,
> >>>> so this patch begs the question: why hostmem-memfd is not sufficient?
> >>>> (patch description is rather lacking on rationale behind the patch)    
> >>>
> >>> There is currently no way to specify memory backends for the secondary memory
> >>> segments (vram, roms, etc), and IMO it would be onerous to specify a backend for
> >>> each of them.  On x86_64, these include pc.bios, vga.vram, pc.rom, vga.rom,
> >>> /rom@etc/acpi/tables, /rom@etc/table-loader, /rom@etc/acpi/rsdp.

MemoryRegion is not the only place where state is stored.
If we only talk about fwcfg entries state, it can also reference
plain malloced memory allocated elsewhere or make a deep copy internally.
Similarly devices also may store state outside of RamBlock framework.

How are you dealing with that?

> >>>
> >>> - Steve
> >>>     
> >>>>>>      "                aes-key-wrap=on|off controls support for AES key wrapping (default=on)\n"
> >>>>>>      "                dea-key-wrap=on|off controls support for DEA key wrapping (default=on)\n"
> >>>>>>      "                suppress-vmdesc=on|off disables self-describing migration (default=off)\n"
> >>>>>> @@ -76,6 +77,11 @@ SRST
> >>>>>>          supported by the host, de-duplicates identical memory pages
> >>>>>>          among VMs instances (enabled by default).
> >>>>>>  
> >>>>>> +    ``memfd-alloc=on|off``
> >>>>>> +        Enables or disables allocation of anonymous guest RAM using
> >>>>>> +        memfd_create.  Any associated memory-backend objects are created with
> >>>>>> +        share=on.  The memfd-alloc default is off.
> >>>>>> +
> >>>>>>      ``aes-key-wrap=on|off``
> >>>>>>          Enables or disables AES key wrapping support on s390-ccw hosts.
> >>>>>>          This feature controls whether AES wrapping keys will be created
> >>>>>> diff --git a/softmmu/physmem.c b/softmmu/physmem.c
> >>>>>> index 3524c04..95e2b49 100644
> >>>>>> --- a/softmmu/physmem.c
> >>>>>> +++ b/softmmu/physmem.c
> >>>>>> @@ -41,6 +41,7 @@
> >>>>>>  #include "qemu/config-file.h"
> >>>>>>  #include "qemu/error-report.h"
> >>>>>>  #include "qemu/qemu-print.h"
> >>>>>> +#include "qemu/memfd.h"
> >>>>>>  #include "exec/memory.h"
> >>>>>>  #include "exec/ioport.h"
> >>>>>>  #include "sysemu/dma.h"
> >>>>>> @@ -1964,35 +1965,63 @@ static void ram_block_add(RAMBlock *new_block, Error **errp)
> >>>>>>      const bool shared = qemu_ram_is_shared(new_block);
> >>>>>>      RAMBlock *block;
> >>>>>>      RAMBlock *last_block = NULL;
> >>>>>> +    struct MemoryRegion *mr = new_block->mr;
> >>>>>>      ram_addr_t old_ram_size, new_ram_size;
> >>>>>>      Error *err = NULL;
> >>>>>> +    const char *name;
> >>>>>> +    void *addr = 0;
> >>>>>> +    size_t maxlen;
> >>>>>> +    MachineState *ms = MACHINE(qdev_get_machine());
> >>>>>>  
> >>>>>>      old_ram_size = last_ram_page();
> >>>>>>  
> >>>>>>      qemu_mutex_lock_ramlist();
> >>>>>> -    new_block->offset = find_ram_offset(new_block->max_length);
> >>>>>> +    maxlen = new_block->max_length;
> >>>>>> +    new_block->offset = find_ram_offset(maxlen);
> >>>>>>  
> >>>>>>      if (!new_block->host) {
> >>>>>>          if (xen_enabled()) {
> >>>>>> -            xen_ram_alloc(new_block->offset, new_block->max_length,
> >>>>>> -                          new_block->mr, &err);
> >>>>>> +            xen_ram_alloc(new_block->offset, maxlen, new_block->mr, &err);
> >>>>>>              if (err) {
> >>>>>>                  error_propagate(errp, err);
> >>>>>>                  qemu_mutex_unlock_ramlist();
> >>>>>>                  return;
> >>>>>>              }
> >>>>>>          } else {
> >>>>>> -            new_block->host = qemu_anon_ram_alloc(new_block->max_length,
> >>>>>> -                                                  &new_block->mr->align,
> >>>>>> -                                                  shared, noreserve);
> >>>>>> -            if (!new_block->host) {
> >>>>>> +            name = memory_region_name(mr);
> >>>>>> +            if (ms->memfd_alloc) {
> >>>>>> +                Object *parent = &mr->parent_obj;
> >>>>>> +                int mfd = -1;          /* placeholder until next patch */
> >>>>>> +                mr->align = QEMU_VMALLOC_ALIGN;
> >>>>>> +                if (mfd < 0) {
> >>>>>> +                    mfd = qemu_memfd_create(name, maxlen + mr->align,
> >>>>>> +                                            0, 0, 0, &err);
> >>>>>> +                    if (mfd < 0) {
> >>>>>> +                        return;
> >>>>>> +                    }
> >>>>>> +                }
> >>>>>> +                qemu_set_cloexec(mfd);
> >>>>>> +                /* The memory backend already set its desired flags. */
> >>>>>> +                if (!object_dynamic_cast(parent, TYPE_MEMORY_BACKEND)) {
> >>>>>> +                    new_block->flags |= RAM_SHARED;
> >>>>>> +                }
> >>>>>> +                addr = file_ram_alloc(new_block, maxlen, mfd,
> >>>>>> +                                      false, false, 0, errp);
> >>>>>> +                trace_anon_memfd_alloc(name, maxlen, addr, mfd);
> >>>>>> +            } else {
> >>>>>> +                addr = qemu_anon_ram_alloc(maxlen, &mr->align,
> >>>>>> +                                           shared, noreserve);
> >>>>>> +            }
> >>>>>> +
> >>>>>> +            if (!addr) {
> >>>>>>                  error_setg_errno(errp, errno,
> >>>>>>                                   "cannot set up guest memory '%s'",
> >>>>>> -                                 memory_region_name(new_block->mr));
> >>>>>> +                                 name);
> >>>>>>                  qemu_mutex_unlock_ramlist();
> >>>>>>                  return;
> >>>>>>              }
> >>>>>> -            memory_try_enable_merging(new_block->host, new_block->max_length);
> >>>>>> +            memory_try_enable_merging(addr, maxlen);
> >>>>>> +            new_block->host = addr;
> >>>>>>          }
> >>>>>>      }
> >>>>>>  
> >>>>>> diff --git a/softmmu/vl.c b/softmmu/vl.c
> >>>>>> index 620a1f1..ab3648a 100644
> >>>>>> --- a/softmmu/vl.c
> >>>>>> +++ b/softmmu/vl.c
> >>>>>> @@ -2440,6 +2440,7 @@ static void create_default_memdev(MachineState *ms, const char *path)
> >>>>>>          object_property_set_str(obj, "mem-path", path, &error_fatal);
> >>>>>>      }
> >>>>>>      object_property_set_int(obj, "size", ms->ram_size, &error_fatal);
> >>>>>> +    object_property_set_bool(obj, "share", ms->memfd_alloc, &error_fatal);
> >>>>>>      object_property_add_child(object_get_objects_root(), mc->default_ram_id,
> >>>>>>                                obj);
> >>>>>>      /* Ensure backend's memory region name is equal to mc->default_ram_id */
> >>>>>> diff --git a/trace-events b/trace-events
> >>>>>> index a637a61..770a9ac 100644
> >>>>>> --- a/trace-events
> >>>>>> +++ b/trace-events
> >>>>>> @@ -45,6 +45,7 @@ ram_block_discard_range(const char *rbname, void *hva, size_t length, bool need_
> >>>>>>  # accel/tcg/cputlb.c
> >>>>>>  memory_notdirty_write_access(uint64_t vaddr, uint64_t ram_addr, unsigned size) "0x%" PRIx64 " ram_addr 0x%" PRIx64 " size %u"
> >>>>>>  memory_notdirty_set_dirty(uint64_t vaddr) "0x%" PRIx64
> >>>>>> +anon_memfd_alloc(const char *name, size_t size, void *ptr, int fd) "%s size %zu ptr %p fd %d"
> >>>>>>  
> >>>>>>  # gdbstub.c
> >>>>>>  gdbstub_op_start(const char *device) "Starting gdbstub using device %s"
> >>>>>> diff --git a/util/qemu-config.c b/util/qemu-config.c
> >>>>>> index 436ab63..3606e5c 100644
> >>>>>> --- a/util/qemu-config.c
> >>>>>> +++ b/util/qemu-config.c
> >>>>>> @@ -207,6 +207,10 @@ static QemuOptsList machine_opts = {
> >>>>>>              .type = QEMU_OPT_BOOL,
> >>>>>>              .help = "enable/disable memory merge support",
> >>>>>>          },{
> >>>>>> +            .name = "memfd-alloc",
> >>>>>> +            .type = QEMU_OPT_BOOL,
> >>>>>> +            .help = "enable/disable memfd_create for anonymous memory",
> >>>>>> +        },{
> >>>>>>              .name = "usb",
> >>>>>>              .type = QEMU_OPT_BOOL,
> >>>>>>              .help = "Set on/off to enable/disable usb",
> >>>>>> -- 
> >>>>>> 1.8.3.1      
> >>>>>
> >>>>>    
> >>>>     
> >>  
> >   
> 



  reply	other threads:[~2022-03-10 16:02 UTC|newest]

Thread overview: 96+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-22 19:05 [PATCH V7 00/29] Live Update Steve Sistare
2021-12-22 19:05 ` [PATCH V7 01/29] memory: qemu_check_ram_volatile Steve Sistare
2022-02-24 18:28   ` Dr. David Alan Gilbert
2022-03-03 15:55     ` Steven Sistare
2022-03-04 12:47   ` Philippe Mathieu-Daudé
2021-12-22 19:05 ` [PATCH V7 02/29] migration: fix populate_vfio_info Steve Sistare
2022-02-24 18:42   ` Peter Maydell
2022-03-03 15:55     ` Steven Sistare
2022-03-03 16:21       ` Peter Maydell
2022-03-03 16:38         ` Steven Sistare
2021-12-22 19:05 ` [PATCH V7 03/29] migration: qemu file wrappers Steve Sistare
2022-02-24 18:21   ` Dr. David Alan Gilbert
2022-03-03 15:55     ` Steven Sistare
2021-12-22 19:05 ` [PATCH V7 04/29] migration: simplify savevm Steve Sistare
2022-02-24 18:25   ` Dr. David Alan Gilbert
2022-03-03 15:55     ` Steven Sistare
2021-12-22 19:05 ` [PATCH V7 05/29] vl: start on wakeup request Steve Sistare
2022-02-24 18:51   ` Dr. David Alan Gilbert
2022-03-03 15:56     ` Steven Sistare
2021-12-22 19:05 ` [PATCH V7 06/29] cpr: reboot mode Steve Sistare
2021-12-22 19:05 ` [PATCH V7 07/29] cpr: reboot HMP interfaces Steve Sistare
2021-12-22 19:05 ` [PATCH V7 08/29] memory: flat section iterator Steve Sistare
2022-03-04 12:48   ` Philippe Mathieu-Daudé
2022-03-07 14:42     ` Steven Sistare
2022-03-09 14:18   ` Marc-André Lureau
2021-12-22 19:05 ` [PATCH V7 09/29] oslib: qemu_clear_cloexec Steve Sistare
2021-12-22 19:05 ` [PATCH V7 10/29] machine: memfd-alloc option Steve Sistare
2022-02-18  8:05   ` Guoyi Tu
2022-03-03 15:55     ` Steven Sistare
2022-02-24 17:56   ` Dr. David Alan Gilbert
2022-03-03 15:56     ` Steven Sistare
2022-03-03 17:21   ` Michael S. Tsirkin
2022-03-04 10:41     ` Igor Mammedov
2022-03-07 14:41       ` Steven Sistare
2022-03-08  6:50         ` Michael S. Tsirkin
2022-03-08  7:20           ` Igor Mammedov
2022-03-10 15:36             ` Steven Sistare
2022-03-10 16:00               ` Igor Mammedov [this message]
2022-03-10 17:28                 ` Steven Sistare
2022-03-10 18:18                   ` Steven Sistare
2022-03-11  9:42                     ` Igor Mammedov
2022-03-29 17:43                       ` Steven Sistare
2022-03-11 10:08         ` Daniel P. Berrangé
2022-03-11 10:25     ` David Hildenbrand
2022-03-11  9:54   ` David Hildenbrand
2021-12-22 19:05 ` [PATCH V7 11/29] qapi: list utility functions Steve Sistare
2022-03-09 14:11   ` Marc-André Lureau
2022-03-11 16:45     ` Steven Sistare
2022-03-11 21:59       ` Marc-André Lureau
2021-12-22 19:05 ` [PATCH V7 12/29] vl: helper to request re-exec Steve Sistare
2022-03-09 14:16   ` Marc-André Lureau
2022-03-11 16:45     ` Steven Sistare
2021-12-22 19:05 ` [PATCH V7 13/29] cpr: preserve extra state Steve Sistare
2021-12-22 19:05 ` [PATCH V7 14/29] cpr: restart mode Steve Sistare
2021-12-22 19:05 ` [PATCH V7 15/29] cpr: restart HMP interfaces Steve Sistare
2021-12-22 19:05 ` [PATCH V7 16/29] hostmem-memfd: cpr for memory-backend-memfd Steve Sistare
2021-12-22 19:05 ` [PATCH V7 17/29] pci: export functions for cpr Steve Sistare
2021-12-22 23:07   ` Michael S. Tsirkin
2022-01-05 17:22     ` Steven Sistare
2022-01-05 20:16       ` Michael S. Tsirkin
2022-01-06 22:48         ` Steven Sistare
2022-01-07 10:03           ` Michael S. Tsirkin
2021-12-22 19:05 ` [PATCH V7 18/29] vfio-pci: refactor " Steve Sistare
2022-03-03 23:21   ` Alex Williamson
2022-03-07 14:42     ` Steven Sistare
2021-12-22 19:05 ` [PATCH V7 19/29] vfio-pci: cpr part 1 (fd and dma) Steve Sistare
2021-12-22 23:15   ` Michael S. Tsirkin
2022-01-05 17:24     ` Steven Sistare
2022-01-05 21:14       ` Michael S. Tsirkin
2022-01-05 21:40         ` Steven Sistare
2022-01-05 23:09           ` Michael S. Tsirkin
2022-01-05 23:24             ` Steven Sistare
2022-01-06  9:12               ` Michael S. Tsirkin
2022-01-06 19:13                 ` Steven Sistare
2022-03-07 22:16   ` Alex Williamson
2022-03-10 15:00     ` Steven Sistare
2022-03-10 18:35       ` Alex Williamson
2022-03-10 19:55         ` Steven Sistare
2022-03-10 22:30           ` Alex Williamson
2022-03-11 16:22             ` Steven Sistare
2021-12-22 19:05 ` [PATCH V7 20/29] vfio-pci: cpr part 2 (msi) Steve Sistare
2021-12-22 19:05 ` [PATCH V7 21/29] vfio-pci: cpr part 3 (intx) Steve Sistare
2021-12-22 19:05 ` [PATCH V7 22/29] vfio-pci: recover from unmap-all-vaddr failure Steve Sistare
2021-12-22 19:05 ` [PATCH V7 23/29] vhost: reset vhost devices for cpr Steve Sistare
2021-12-22 19:05 ` [PATCH V7 24/29] loader: suppress rom_reset during cpr Steve Sistare
2021-12-22 19:05 ` [PATCH V7 25/29] chardev: cpr framework Steve Sistare
2021-12-22 19:05 ` [PATCH V7 26/29] chardev: cpr for simple devices Steve Sistare
2021-12-22 19:05 ` [PATCH V7 27/29] chardev: cpr for pty Steve Sistare
2021-12-22 19:05 ` [PATCH V7 28/29] chardev: cpr for sockets Steve Sistare
2022-02-18  9:03   ` Guoyi Tu
2022-03-03 15:55     ` Steven Sistare
2021-12-22 19:05 ` [PATCH V7 29/29] cpr: only-cpr-capable option Steve Sistare
2022-02-18  9:43   ` Guoyi Tu
2022-03-03 15:54     ` Steven Sistare
2022-01-07 18:45 ` [PATCH V7 00/29] Live Update Steven Sistare
2022-02-18 13:36   ` Steven Sistare

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=20220310170025.33b9f6f0@redhat.com \
    --to=imammedo@redhat.com \
    --cc=alex.bennee@linaro.org \
    --cc=alex.williamson@redhat.com \
    --cc=armbru@redhat.com \
    --cc=berrange@redhat.com \
    --cc=david@redhat.com \
    --cc=dgilbert@redhat.com \
    --cc=eblake@redhat.com \
    --cc=jason.zeng@linux.intel.com \
    --cc=marcandre.lureau@redhat.com \
    --cc=mst@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=philmd@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=quintela@redhat.com \
    --cc=stefanha@redhat.com \
    --cc=steven.sistare@oracle.com \
    --cc=zhengchuan@huawei.com \
    /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).