public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Alexander Kanavin <alex.kanavin@gmail.com>,
	Mark Hatle <mark.hatle@kernel.crashing.org>
Cc: mark.hatle@amd.com, openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH 1/1] qemu: Allow native and nativesdk versions on Linux older then 4.17
Date: Thu, 25 Jan 2024 22:38:28 +0000	[thread overview]
Message-ID: <9ffa7599e4a73860b2e696fc7b04c968355f369f.camel@linuxfoundation.org> (raw)
In-Reply-To: <CANNYZj8AcHDRngXF08_G-KwKYZo67AW_NZVHC1NaJu0wFXH4Vw@mail.gmail.com>

On Thu, 2024-01-25 at 22:41 +0100, Alexander Kanavin wrote:
> Initial release of Ubuntu 18.04 had 4.15 alright. Later point releases 
> offered much newer kernels. It’s also altogether EOL since end of may 2023.
> 
> Why should oe-core carry these? It’s RP’s call as qemu maintainer but my vote 
> is a firm no, unless additional arguments are put forward.

I had talked a bit with Mark about this issue and in the end I did
suggest sending the patch as the issue is a tricky one and it is
something we should really think about. At the very least it is worth
documenting and understanding the implications as it isn't easy to see
all the implications straight away.

The challenge is that the generated SDKs may end up running on
older/interesting systems and it is mostly pure luck we haven't hit
this. We do still have one 18.04 autobuilder system, albeit with a
slightly newer kernel version without this issue. Our "normal" sanity
checks don't cover it either.

I'm still unsure if we plan to merge the patch or not.

Cheers,

Richard




  parent reply	other threads:[~2024-01-25 22:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-25 21:03 [PATCH 0/1] Support running qemu on kernel older then 4.17 Mark Hatle
2024-01-25 21:03 ` [PATCH 1/1] qemu: Allow native and nativesdk versions on Linux " Mark Hatle
2024-01-25 21:41   ` [OE-core] " Alexander Kanavin
2024-01-25 22:23     ` Mark Hatle
2024-01-25 22:38     ` Richard Purdie [this message]
2024-01-25 21:42   ` Martin Jansa
2024-01-25 22:20     ` Mark Hatle

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=9ffa7599e4a73860b2e696fc7b04c968355f369f.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=alex.kanavin@gmail.com \
    --cc=mark.hatle@amd.com \
    --cc=mark.hatle@kernel.crashing.org \
    --cc=openembedded-core@lists.openembedded.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