Kernel KVM virtualization development
 help / color / mirror / Atom feed
From: Markus Armbruster <armbru@redhat.com>
To: quintela@redhat.com
Cc: KVM devel mailing list <kvm@vger.kernel.org>, qemu-devel@nongnu.org
Subject: Re: KVM Call minutes for 2012-09-25
Date: Tue, 25 Sep 2012 16:59:00 +0200	[thread overview]
Message-ID: <873926p2rv.fsf@blackfin.pond.sub.org> (raw)
In-Reply-To: <871uhqqif4.fsf@trasno.org> (Juan Quintela's message of "Tue, 25 Sep 2012 16:35:43 +0200")

Juan Quintela <quintela@redhat.com> writes:

> Hi
>
> This are this week minutes:
>
> - URI parsing library for glusterfs: libxml2 vs. in-tree "fork" of the
> same code. (Paolo)
>  * code hasn't changed in 2 years, it is really stable
>  * anthony wants to copy the code
>
> - there are several commands that do blocking IO
>   dump-guest-memory/screen-dump
>   convert to asynchronous commands after we move all to QAPI
>   only two commands missingto port to QAPI, and one is posted on list
>   non-blocking IO to a file is a challenge
>   (we have code on the block layer for it)
>
> - how to give errors from OpenFile to the caller
>   putting errno as int: bad idea
>   putting as strerrno string: also a bad idea, no warantees

Use the identifiers instead of their non-portable numeric encodings or
strerror() descriptions: "EPERM", "EINVAL", ...

>   Using an extended error code
>   Put it as a string that can be parsed?
>   Paolo suggest to create a new error class
>   We don't warantee that errors would be "parseable".

We don't want programs to parse the human-readable error string.

  reply	other threads:[~2012-09-25 14:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-25 14:35 KVM Call minutes for 2012-09-25 Juan Quintela
2012-09-25 14:59 ` Markus Armbruster [this message]
2012-09-25 18:52   ` Luiz Capitulino
2012-09-25 21:13     ` [Qemu-devel] " Anthony Liguori

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=873926p2rv.fsf@blackfin.pond.sub.org \
    --to=armbru@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=qemu-devel@nongnu.org \
    --cc=quintela@redhat.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