All of lore.kernel.org
 help / color / mirror / Atom feed
From: Laszlo Ersek <lersek@redhat.com>
To: Andrew Jones <drjones@redhat.com>
Cc: peter.maydell@linaro.org, qemu-devel@nongnu.org, ehabkost@redhat.com
Subject: Re: [Qemu-devel] [PATCH v2 0/2] hw/arm/virt: max-cpus init/check fixup
Date: Mon, 19 Oct 2015 17:24:31 +0200	[thread overview]
Message-ID: <56250B2F.7010505@redhat.com> (raw)
In-Reply-To: <1445189728-860-1-git-send-email-drjones@redhat.com>

On 10/18/15 19:35, Andrew Jones wrote:
> Changes from v1
> . drop the RFC patch "arm_gic_common.h: add gicv2 aliases for defines" [Peter]
> . add a patch to cleanup vl.c's max-cpu error message a little [Drew]
> . cleanup mach-virt's new error message [Peter]
> . make the error message exactly like vl's cleaned up message [Drew]
> . add a comment to virt_class_init explaining that we'll further restrict
>   max_cpus later [Peter]
> 
> ---
> 
> Sorry to be so late getting this simple v2 out. I was trying to
> get a new feature (qmp-dump-guest-memory support for arm) posted
> before the 2.5 soft freeze (but missed that anyway...)

(off-topic)

When you do that, please consider extending the
"scripts/dump-guest-memory.py" script as well.

(This is not even a "nice to have" request -- the script already doesn't
support all the target arches on which the QMP command is available (it
only supports x86_64), so nothing is lost if you don't extend the
script. My only goal is to put the thought in your mind; you decide :))

Thanks!
Laszlo

> 
> Andrew Jones (2):
>   vl: trivial: minor tweaks to a max-cpu error msg
>   hw/arm/virt: don't use a15memmap directly
> 
>  hw/arm/virt.c | 25 +++++++++++++++++++++----
>  vl.c          |  4 ++--
>  2 files changed, 23 insertions(+), 6 deletions(-)
> 

  parent reply	other threads:[~2015-10-19 15:24 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-18 17:35 [Qemu-devel] [PATCH v2 0/2] hw/arm/virt: max-cpus init/check fixup Andrew Jones
2015-10-18 17:35 ` [Qemu-devel] [PATCH 1/2] vl: trivial: minor tweaks to a max-cpu error msg Andrew Jones
2015-10-19 18:51   ` Eduardo Habkost
2015-10-20 12:05     ` Paolo Bonzini
2015-10-20  7:12   ` Markus Armbruster
2015-10-26 13:00     ` Andrew Jones
2015-10-26 13:38       ` Eduardo Habkost
2015-10-18 17:35 ` [Qemu-devel] [PATCH v2 2/2] hw/arm/virt: don't use a15memmap directly Andrew Jones
2015-10-19 15:24 ` Laszlo Ersek [this message]
2015-10-23 15:01 ` [Qemu-devel] [PATCH v2 0/2] hw/arm/virt: max-cpus init/check fixup Peter Maydell

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=56250B2F.7010505@redhat.com \
    --to=lersek@redhat.com \
    --cc=drjones@redhat.com \
    --cc=ehabkost@redhat.com \
    --cc=peter.maydell@linaro.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 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.