All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sascha Silbe <silbe@linux.vnet.ibm.com>
To: Markus Armbruster <armbru@redhat.com>, qemu-devel@nongnu.org
Cc: peter.maydell@linaro.org, pbonzini@redhat.com,
	Cornelia Huck <cornelia.huck@de.ibm.com>
Subject: Re: [Qemu-devel] [PATCH RFC v3 1/5] tests: New make target check-source
Date: Tue, 05 Jul 2016 19:17:31 +0200	[thread overview]
Message-ID: <87bn2cknro.fsf@oc4731375738.ibm.com> (raw)
In-Reply-To: <1467291213-13393-2-git-send-email-armbru@redhat.com>

Dear Markus,


I looked into the s390x specific failures as it would be nice to get
them fixed up right away. Fortunately it looks like all of them are
related to known shortcomings of the header check rather than actual
issues with the header files, so there's nothing for me to do. ;)


Markus Armbruster <armbru@redhat.com> writes:

[...]
> Some headers fail the test because they need to be compiled with
> -DNEED_CPU_H, and testing them is not yet implemented.  They are
> marked with a comment
>
>     /* NOTE: May only be included into target-dependent code */

The following header files either include target-s390x/cpu.h themselves
or expect it to have been included already so they should be marked with
the above note rather than the FIXME:

- hw/s390x/ipl.h
- hw/s390x/s390-pci-inst.h
- hw/s390x/s390-virtio.h


[linux-headers/asm-s390/kvm.h]
> +/* FIXME Does not pass make check-headers with CONFIG_WIN32, yet! */

Is this because of the linux/types.h include or is there some other
issue? Should we even check these imported headers?


[linux-user/host/*/hostdep.h]
> +/* FIXME Does not pass make check-headers, yet! */

The "struct ucontext" definition used by hostdep.h differs between host
architectures. Not sure if testing the headers for "foreign" host
architectures is possible; we should probably just skip them instead of
marking them with a FIXME.


Many or even most other non-softmmu target failures smell like
NEED_CPU_H.


[*/helper.h]
> +/* FIXME Does not pass make check-headers, yet! */

Probably never will. Looks like it's meant to be included only by some
magic preprocessor code.

Sascha
-- 
Softwareentwicklung Sascha Silbe, Niederhofenstraße 5/1, 71229 Leonberg
https://se-silbe.de/
USt-IdNr. DE281696641

  parent reply	other threads:[~2016-07-05 17:17 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-30 12:53 [Qemu-devel] [PATCH RFC v3 0/5] Baby steps towards saner headers Markus Armbruster
2016-06-30 12:53 ` [Qemu-devel] [PATCH RFC v3 1/5] tests: New make target check-source Markus Armbruster
2016-06-30 13:27   ` Paolo Bonzini
2016-06-30 14:30     ` Markus Armbruster
2016-06-30 14:31       ` Paolo Bonzini
2016-07-05 17:17   ` Sascha Silbe [this message]
2016-06-30 12:53 ` [Qemu-devel] [PATCH RFC v3 2/5] tests: Make check-block a phony target Markus Armbruster
2016-07-01 17:11   ` Eric Blake
2016-06-30 12:53 ` [Qemu-devel] [PATCH RFC v3 3/5] Include hw/irq.h where qemu_irq is used Markus Armbruster
2016-06-30 12:53 ` [Qemu-devel] [PATCH RFC v3 4/5] Include exec/hwaddr.h where hwaddr " Markus Armbruster
2016-06-30 12:53 ` [Qemu-devel] [PATCH RFC v3 5/5] Add a few missing #include "qemu/queue.h" Markus Armbruster

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=87bn2cknro.fsf@oc4731375738.ibm.com \
    --to=silbe@linux.vnet.ibm.com \
    --cc=armbru@redhat.com \
    --cc=cornelia.huck@de.ibm.com \
    --cc=pbonzini@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.