From: "Michael S. Tsirkin" <mst@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Thomas Huth <thuth@redhat.com>, Cornelia Huck <cohuck@redhat.com>,
qemu-devel@nongnu.org
Subject: Re: [PATCH v2 for-7.0] scripts: Explain the difference between linux-headers and standard-headers
Date: Fri, 10 Dec 2021 05:48:56 -0500 [thread overview]
Message-ID: <20211210054601-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20211209194532.1502920-1-peter.maydell@linaro.org>
On Thu, Dec 09, 2021 at 07:45:32PM +0000, Peter Maydell wrote:
> If you don't know it, it's hard to figure out the difference between
> the linux-headers folder and the include/standard-headers folder.
> So let's add a short explanation to clarify the difference.
>
> Suggested-by: Thomas Huth <thuth@redhat.com>
> Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
A couple of minor tweaks: what matters is which platform
we are building for I think.
> ---
> v1 of this was from Thomas; I suggested some expanded wording
> and since that made the patch pretty much entirely my text
> Thomas suggested I send this under my name.
> ---
> scripts/update-linux-headers.sh | 16 ++++++++++++++++
> 1 file changed, 16 insertions(+)
>
> diff --git a/scripts/update-linux-headers.sh b/scripts/update-linux-headers.sh
> index fea4d6eb655..d23851e1d3b 100755
> --- a/scripts/update-linux-headers.sh
> +++ b/scripts/update-linux-headers.sh
> @@ -9,6 +9,22 @@
> #
> # This work is licensed under the terms of the GNU GPL version 2.
> # See the COPYING file in the top-level directory.
> +#
> +# The script will copy the headers into two target folders:
> +#
> +# - linux-headers/ for files that are required for compiling on a
I think it's more of a "for a Linux host"
> +# Linux host. Generally we have these so we can use kernel structs
> +# and defines that are more recent than the headers that might be
> +# in /usr/include/linux
I'd just say "installed". Path does not matter.
>on the host system. Usually this script
> +# can do simple file copies for these headers.
> +#
> +# - include/standard-headers/ for files that are used for guest
> +# device emulation and are required on all hosts. For instance, we
> +# get our definitions of the virtio structures from the Linux
> +# kernel headers, but we need those definitions regardless of which
> +# host OS we are building on.
we are building for
> This script has to be careful to
> +# sanitize the headers to remove any use of Linux-specifics such as
> +# types like "__u64". This work is done in the cp_portable function.
>
> tmpdir=$(mktemp -d)
> linux="$1"
> --
> 2.25.1
next prev parent reply other threads:[~2021-12-10 10:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-09 19:45 [PATCH v2 for-7.0] scripts: Explain the difference between linux-headers and standard-headers Peter Maydell
2021-12-09 19:55 ` Thomas Huth
2021-12-10 10:16 ` Cornelia Huck
2021-12-10 10:48 ` Michael S. Tsirkin [this message]
2021-12-14 20:10 ` Alex Bennée
2022-01-28 12:00 ` 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=20211210054601-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=cohuck@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=thuth@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 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.