All of lore.kernel.org
 help / color / mirror / Atom feed
From: Markus Armbruster <armbru@redhat.com>
To: Vadim Galitsyn <vadim.galitsyn@profitbricks.com>
Cc: imammedo@redhat.com, Mohammed Gamal <mgamal@redhat.com>,
	"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
	qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v2] hmp, qmp: introduce "info memory" and "query-memory" commands
Date: Fri, 23 Jun 2017 08:44:39 +0200	[thread overview]
Message-ID: <87zicz5hk8.fsf@dusky.pond.sub.org> (raw)
In-Reply-To: <CAPHE7NppPyGfe=29twDOUdWT=CXcJ8M935AbmtvPNS3-KorYzA@mail.gmail.com> (Vadim Galitsyn's message of "Thu, 22 Jun 2017 17:02:03 +0200")

Vadim Galitsyn <vadim.galitsyn@profitbricks.com> writes:

> Hi Markus,
>
> Thank you for the input.
>
>> However, your query-memory looks like it could fail.
>
> With the latest version of a patch (
> http://lists.nongnu.org/archive/html/qemu-devel/2017-06/msg03475.html)
> "query-memory" can fail only in two cases:
>
> a) if in QOM there is an object of type of TYPE_PC_DIMM which has no
> property of type PC_DIMM_SIZE_PROP, or
> b) PC_DIMM_SIZE_PROP is not represented as an integer.
>
> As far as I understand both (a) and (b) can happen only in case if QOM
> somehow corrupted which is not a normal case
> (please correct me if I am wrong).

These feel like programming errors.  They are impossible to test without
screwing up the program.  Untestable error recovery is commonly wrong.
I recommend to assert instead.  Igor, what do you think?

> Please also note, this is not the last version of the patch since new
> functionality was suggested
> to be included (NUMA information).
>
> If patch will be accepted, I think we would need a test case for it since
> command output differs once memory
> was hot-added/removed per given NUMA node. When final functionality will be
> negotiated, I will come up
> with test scenario and test case itself.

Thanks!

      reply	other threads:[~2017-06-23  6:44 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-13 14:05 [Qemu-devel] [PATCH v2] hmp, qmp: introduce "info memory" and "query-memory" commands Vadim Galitsyn
2017-06-13 14:59 ` no-reply
2017-06-14  6:52   ` Fam Zheng
2017-06-14  9:22 ` Dr. David Alan Gilbert
2017-06-14 15:20   ` Vadim Galitsyn
2017-06-14 15:40     ` Dr. David Alan Gilbert
2017-06-20 14:10       ` Markus Armbruster
2017-06-22 15:02         ` Vadim Galitsyn
2017-06-23  6:44           ` Markus Armbruster [this message]

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=87zicz5hk8.fsf@dusky.pond.sub.org \
    --to=armbru@redhat.com \
    --cc=dgilbert@redhat.com \
    --cc=imammedo@redhat.com \
    --cc=mgamal@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=vadim.galitsyn@profitbricks.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.