From: Robbie Harwood <rharwood@redhat.com>
To: Ard Biesheuvel <ardb@kernel.org>,
Julian Andres Klode <julian.klode@canonical.com>
Cc: Daniel Kiper <dkiper@net-space.pl>,
grub-devel@gnu.org, Jeremy Szu <jeremy.szu@canonical.com>,
arei@altlinux.org, heinrich.schuchardt@canonical.com,
ilias.apalodimas@linaro.org, quic_llindhol@quicinc.com,
tobias.powalowski@googlemail.com
Subject: Re: Handling large allocations (bypassing mm?)
Date: Fri, 16 Dec 2022 12:55:39 -0500 [thread overview]
Message-ID: <jlgedszs06c.fsf@redhat.com> (raw)
In-Reply-To: <CAMj1kXHi7sf+du-SVpHxefWTDB_-iqGSF=PRbDURe1ciFsSLkQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1034 bytes --]
Ard Biesheuvel <ardb@kernel.org> writes:
> As for supporing kernels from 2012: I don't see why upstream GRUB
> should care about that. If your distro fork supports those today, you
> will simply need to carry those patches out of tree a bit longer.
No, it's not a question of distros supporting themselves like this. For
better or worse, people expect to be able to install many OSs on their
drive and have any grub be able to boot any of them.
One such use case I've seen is hardware testing: someone will install
all the operating systems they care about on a drive, then plug it in to
the machine with the hardware and try all of them in sequence. And of
course there're always hobbyists who just think it's fun to do things
like that - they file bugs too :)
In any case, it's not a little bit of time we're talking about here -
even though RHEL 6 is only guaranteed into 2024 right now, RHEL 8 is
slated to be here until at least 2031. (Source:
https://access.redhat.com/support/policy/updates/errata/ )
Be well,
--Robbie
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 861 bytes --]
next prev parent reply other threads:[~2022-12-16 17:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-14 13:21 Handling large allocations (bypassing mm?) Julian Andres Klode
2022-12-14 15:11 ` Daniel Kiper
2022-12-15 14:28 ` Julian Andres Klode
2022-12-15 17:35 ` Ard Biesheuvel
2022-12-16 17:55 ` Robbie Harwood [this message]
2022-12-22 13:14 ` Ard Biesheuvel
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=jlgedszs06c.fsf@redhat.com \
--to=rharwood@redhat.com \
--cc=ardb@kernel.org \
--cc=arei@altlinux.org \
--cc=dkiper@net-space.pl \
--cc=grub-devel@gnu.org \
--cc=heinrich.schuchardt@canonical.com \
--cc=ilias.apalodimas@linaro.org \
--cc=jeremy.szu@canonical.com \
--cc=julian.klode@canonical.com \
--cc=quic_llindhol@quicinc.com \
--cc=tobias.powalowski@googlemail.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.