qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Huth <thuth@redhat.com>
To: "Philippe Mathieu-Daudé" <philmd@linaro.org>, qemu-devel@nongnu.org
Cc: "Janosch Frank" <frankja@linux.ibm.com>,
	"Alex Bennée" <alex.bennee@linaro.org>,
	"Marc-André Lureau" <marcandre.lureau@redhat.com>
Subject: Re: [PATCH v4 4/7] dump: Introduce win_dump_available()
Date: Fri, 24 Feb 2023 08:08:40 +0100	[thread overview]
Message-ID: <5a22777b-25ee-a479-77a7-4364b0ecfe10@redhat.com> (raw)
In-Reply-To: <20230223231755.81633-5-philmd@linaro.org>

On 24/02/2023 00.17, Philippe Mathieu-Daudé wrote:
> Remove a pair of TARGET_X86_64 #ifdef'ry by introducing
> the win_dump_available() method. We'll soon extract it
> to a stub file for non-x86 targets.
> 
> Signed-off-by: Philippe Mathieu-Daudé <philmd@linaro.org>
> ---
>   dump/dump.c     | 23 +++++++++++++----------
>   dump/win_dump.c |  5 +++++
>   dump/win_dump.h |  3 +++
>   3 files changed, 21 insertions(+), 10 deletions(-)
> 
> diff --git a/dump/dump.c b/dump/dump.c
> index 3784a9054d..c356a88be1 100644
> --- a/dump/dump.c
> +++ b/dump/dump.c
> @@ -30,9 +30,15 @@
>   #include "qemu/main-loop.h"
>   #include "hw/misc/vmcoreinfo.h"
>   #include "migration/blocker.h"
> -
> -#ifdef TARGET_X86_64
>   #include "win_dump.h"
> +
> +#ifndef TARGET_X86_64
> +bool win_dump_available(Error **errp)
> +{
> +    error_setg(errp, "Windows dump is only available for x86-64");
> +
> +    return false;
> +}
>   #endif

I think I'd prefer to introduce the stub file immediately here already, but 
it's just a matter of taste.

So with the indentation fixed (that Richard mentioned):

Reviewed-by: Thomas Huth <thuth@redhat.com>




  parent reply	other threads:[~2023-02-24  7:09 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-23 23:17 [PATCH v4 0/7] dump: Make most of it target agnostic (build once) Philippe Mathieu-Daudé
2023-02-23 23:17 ` [PATCH v4 1/7] dump: Replace tswapN() -> cpu_to_dumpN() Philippe Mathieu-Daudé
2023-02-23 23:29   ` Richard Henderson
2023-02-24  7:00   ` Thomas Huth
2023-02-23 23:17 ` [PATCH v4 2/7] dump: Replace TARGET_PAGE_SIZE -> qemu_target_page_size() Philippe Mathieu-Daudé
2023-02-23 23:30   ` Richard Henderson
2023-02-24  7:01   ` Thomas Huth
2023-02-23 23:17 ` [PATCH v4 3/7] dump: Correct headers included Philippe Mathieu-Daudé
2023-02-23 23:32   ` Richard Henderson
2023-02-24  7:02   ` Thomas Huth
2023-02-23 23:17 ` [PATCH v4 4/7] dump: Introduce win_dump_available() Philippe Mathieu-Daudé
2023-02-23 23:43   ` Richard Henderson
2023-02-24  7:08   ` Thomas Huth [this message]
2023-02-23 23:17 ` [PATCH v4 5/7] dump: Introduce create_win_dump() Philippe Mathieu-Daudé
2023-02-23 23:43   ` Richard Henderson
2023-02-24  7:08   ` Thomas Huth
2023-02-23 23:17 ` [PATCH v4 6/7] dump: Build once by adding stubs for non-x86 targets Philippe Mathieu-Daudé
2023-02-23 23:51   ` Richard Henderson
2023-02-24  6:53     ` Philippe Mathieu-Daudé
2023-02-23 23:17 ` [PATCH v4 7/7] dump: Rename x86-specific file as win_dump_x86.c Philippe Mathieu-Daudé
2023-02-23 23:22   ` Philippe Mathieu-Daudé
2023-02-23 23:52   ` Richard Henderson

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=5a22777b-25ee-a479-77a7-4364b0ecfe10@redhat.com \
    --to=thuth@redhat.com \
    --cc=alex.bennee@linaro.org \
    --cc=frankja@linux.ibm.com \
    --cc=marcandre.lureau@redhat.com \
    --cc=philmd@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 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).