qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
	"patches@linaro.org" <patches@linaro.org>
Subject: Re: [Qemu-devel] [PATCH] update-linux-headers.sh: Don't hard code list of architectures
Date: Tue, 17 Jul 2012 20:30:48 +0200	[thread overview]
Message-ID: <5005AF58.3070302@siemens.com> (raw)
In-Reply-To: <CAFEAcA82Jnjb5hE_kOsSmz9c-H8ouZxO5kbLpJTOy7i2BvmKWg@mail.gmail.com>

On 2012-07-17 19:34, Peter Maydell wrote:
> On 17 July 2012 18:03, Jan Kiszka <jan.kiszka@siemens.com> wrote:
>> On 2012-07-17 18:41, Peter Maydell wrote:
>>> Rather than hardcoding the list of architectures in the kernel
>>> header update script, just import headers for every architecture
>>> which supports KVM. This reduces the number of QEMU files which
>>> need to be updated to add support for a new KVM architecture.
>>> It also means we won't break if the kernel drops support for
>>> an architecture in the future.
>>>
>>> Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
>>> ---
>>> I'd like this for ARM, obviously. NB that this change will mean we'll
>>> pick up the ia64 kvm headers next time somebody does a kernel header
>>> update; this seems harmless (and perhaps even useful?). ia64 'make
>>> headers_install' is a bit noisy as of 3.5-rc5 but succeeds anyway.
>>
>> IA64 KVM support is dead and may be removed at some point from the
>> kernel. What about blacklisting it here already to avoid that noise?
> 
> It's only noisy for the developer who runs the script, and if

Developers are also human that may hate seeing this mess. :)

> we blacklist it then we'll have to update the script again to
> remove it from the blacklist when it finally dies.

We /can/ clean this up then, but there will be no urgent need.

> 
> I don't feel very strongly about it, though, so I can add an
> 
>    # Blacklist architectures which have KVM headers but are actually dead
>    if [ "$arch" = "ia64" ]; then
>        continue
>    fi
> 
> to the patch if you want.

Yes, I would prefer doing this.

Jan

-- 
Siemens AG, Corporate Technology, CT RTC ITP SDP-DE
Corporate Competence Center Embedded Linux

  reply	other threads:[~2012-07-17 18:31 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-17 16:41 [Qemu-devel] [PATCH] update-linux-headers.sh: Don't hard code list of architectures Peter Maydell
2012-07-17 17:03 ` Jan Kiszka
2012-07-17 17:34   ` Peter Maydell
2012-07-17 18:30     ` Jan Kiszka [this message]
  -- strict thread matches above, loose matches on Subject: below --
2012-07-18 10:11 Peter Maydell
2012-07-18 10:18 ` Jan Kiszka
2012-08-03 12:55 ` Peter Maydell
2012-08-13  9:23   ` 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=5005AF58.3070302@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=patches@linaro.org \
    --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 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).