From: Dave Hansen <dave.hansen@intel.com>
To: Fam Zheng <fam.zheng@bytedance.com>
Cc: linux-kernel@vger.kernel.org, Lukasz Luba <lukasz.luba@arm.com>,
linyongting@bytedance.com, songmuchun@bytedance.com,
satish.kumar@bytedance.com, Borislav Petkov <bp@alien8.de>,
Thomas Gleixner <tglx@linutronix.de>,
yuanzhu@bytedance.com, Ingo Molnar <mingo@redhat.com>,
Daniel Lezcano <daniel.lezcano@linaro.org>,
Zhang Rui <rui.zhang@intel.com>,
fam@euphon.net, "H. Peter Anvin" <hpa@zytor.com>,
x86@kernel.org, liangma@bytedance.com,
Dave Hansen <dave.hansen@linux.intel.com>,
"Rafael J. Wysocki" <rafael@kernel.org>,
guojinhui.liam@bytedance.com, linux-pm@vger.kernel.org,
Thom Hughes <thom.hughes@bytedance.com>
Subject: Re: [External] Re: [RFC 0/5] parker: PARtitioned KERnel
Date: Wed, 24 Sep 2025 11:32:36 -0700 [thread overview]
Message-ID: <5490118a-7185-44fe-b816-b01c8ff75979@intel.com> (raw)
In-Reply-To: <CAG+v+KZ4bRgVNiMDhNTeiOqqbEXCBD72K5SQZCo=m0xaQ2vauQ@mail.gmail.com>
On 9/24/25 09:21, Fam Zheng wrote:
...
> The model and motivation here is not to split the domain and give
> different shares to different sysadmins, it's intended for one kernel
> to partition itself. I agree we shouldn't have different kernels here:
> one old, one new, one Linux, one Windows... All partitions should run
> a verified parker-aware kernel. Actually, it may be a good idea to
> force the same buildid in kexec between the boot kernel and secondary
> ones.
Uhhh.... From the cover letter:
> Another possible use case is for different kernel instances to have
> different performance tunings, CONFIG_ options, FDO/PGO according to
> the workload.
Wouldn't the buildid change with CONIFG_ options and FDO/PGO?
Thank you for posting this series. It's interesting and a thought
provoking. But, that's where it stops for me. I don't think this
approach has any future upstream. I probably won't look at it again,
even if it hits my inbox. (I hope it _isn't_ sent again unless there is
some *MAJOR* *MAJOR* change to the approach).
next prev parent reply other threads:[~2025-09-24 18:32 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-23 15:31 [RFC 0/5] parker: PARtitioned KERnel Fam Zheng
2025-09-23 15:31 ` [RFC 1/5] x86/boot/e820: Fix memmap to parse with 1 argument Fam Zheng
2025-09-23 15:31 ` [RFC 2/5] x86/smpboot: Export wakeup_secondary_cpu_via_init Fam Zheng
2025-09-23 15:31 ` [RFC 3/5] x86/parker: Introduce parker kerfs interface Fam Zheng
2025-09-23 15:31 ` [RFC 4/5] x86/parker: Add parker initialisation code Fam Zheng
2025-09-23 15:31 ` [RFC 5/5] x86/apic: Make Parker instance use physical APIC Fam Zheng
2025-09-23 19:46 ` [RFC 0/5] parker: PARtitioned KERnel H. Peter Anvin
2025-09-24 15:22 ` Dave Hansen
2025-09-24 16:21 ` [External] " Fam Zheng
2025-09-24 18:32 ` Dave Hansen [this message]
[not found] ` <CABgc4wRgpYNARf+7MhsadfXjDJ0Vd01OoqnVdrW3m6dXMzQSaQ@mail.gmail.com>
2025-09-24 20:13 ` Fam Zheng
2025-09-24 19:01 ` H. Peter Anvin
[not found] ` <CABgc4wTjc9nxmB16LkxiOL5gYO9K8kr46OqM=asyUkX7cT50Sg@mail.gmail.com>
2025-09-24 20:14 ` Fam Zheng
2025-09-24 22:13 ` H. Peter Anvin
2025-09-25 7:26 ` [External] " Fam Zheng
2025-09-25 15:32 ` H. Peter Anvin
2025-10-22 12:11 ` Pavel Machek
2025-10-23 1:26 ` H. Peter Anvin
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=5490118a-7185-44fe-b816-b01c8ff75979@intel.com \
--to=dave.hansen@intel.com \
--cc=bp@alien8.de \
--cc=daniel.lezcano@linaro.org \
--cc=dave.hansen@linux.intel.com \
--cc=fam.zheng@bytedance.com \
--cc=fam@euphon.net \
--cc=guojinhui.liam@bytedance.com \
--cc=hpa@zytor.com \
--cc=liangma@bytedance.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linyongting@bytedance.com \
--cc=lukasz.luba@arm.com \
--cc=mingo@redhat.com \
--cc=rafael@kernel.org \
--cc=rui.zhang@intel.com \
--cc=satish.kumar@bytedance.com \
--cc=songmuchun@bytedance.com \
--cc=tglx@linutronix.de \
--cc=thom.hughes@bytedance.com \
--cc=x86@kernel.org \
--cc=yuanzhu@bytedance.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox