public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Juan Quintela <quintela@redhat.com>
To: kvm-devel <kvm@vger.kernel.org>, qemu-devel@nongnu.org
Subject: KVM call today 2020-03-10
Date: Tue, 10 Mar 2020 12:20:33 +0100	[thread overview]
Message-ID: <87a74ozcam.fsf@secure.laptop> (raw)



Hi

Today is a call becasue there are topics, in case you missed.
Notice that this call is in USA time, so if you are not there, it is
inside possiblity that it is one hour sooner that you are used to. See
the calendar.

 * Clarify the feedback on the latest revision of multi-process QEMU
   patches concerning:
   - Command-line: It's not clear what's the preferred approach to pass
     command-line parameters for the remote process. We are wondering if
     it's OK to accept the command-line parameters for the remote as a
     single string, or if it should be on multiple lines?
   - Refactoring migration related code: We realize that some of the
     modules we have built into the remote process (such as block and
     migration) compile more code than is required by the remote process.
     Ideally, we could refactor them to utilize just the pieces of code
     needed. However, this problem of refactoring has a larger scope.
     Could this be addressed in later projects?



 Call details:

By popular demand, a google calendar public entry with it

  https://www.google.com/calendar/embed?src=dG9iMXRqcXAzN3Y4ZXZwNzRoMHE4a3BqcXNAZ3JvdXAuY2FsZW5kYXIuZ29vZ2xlLmNvbQ

(Let me know if you have any problems with the calendar entry.  I just
gave up about getting right at the same time CEST, CET, EDT and DST).

If you need phone number details,  contact me privately

Thanks, Juan.


                 reply	other threads:[~2020-03-10 11:20 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=87a74ozcam.fsf@secure.laptop \
    --to=quintela@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=qemu-devel@nongnu.org \
    /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