From: Borislav Petkov <bp@alien8.de>
To: "Enrico Weigelt, metux IT consult" <lkml@metux.net>
Cc: "Enrico Weigelt, metux IT consult" <info@metux.net>,
linux-kernel@vger.kernel.org, tglx@linutronix.de,
mingo@redhat.com, x86@kernel.org, hpa@zytor.com,
dmitry.torokhov@gmail.com, derek.kiernan@xilinx.com,
dragan.cvetic@xilinx.com, richardcochran@gmail.com,
linux-hyperv@vger.kernel.org, linux-input@vger.kernel.org,
netdev@vger.kernel.org
Subject: Re: [PATCH 1/2] x86: make vmware support optional
Date: Wed, 2 Dec 2020 20:22:23 +0100 [thread overview]
Message-ID: <20201202192223.GK2951@zn.tnic> (raw)
In-Reply-To: <0c0480af-bcf5-d7ba-9e76-d511e60f76ec@metux.net>
On Wed, Dec 02, 2020 at 08:17:23PM +0100, Enrico Weigelt, metux IT consult wrote:
> Reducing the kernel size. Think of very high density virtualization
> (w/ specially stripped-down workloads) or embedded systems.
>
> For example, I'm running bare minimum kernels w/ only kvm and virtio
> (not even pci, etc) in such scenarios.
>
> Of course, that's nothing for an average distro, therefore leaving
> default y.
Ok, pls put the reasoning for the change in the next revision's commit
message along with how much KB savings we're talking about.
Thx.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
next prev parent reply other threads:[~2020-12-02 19:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-17 20:23 [PATCH 1/2] x86: make vmware support optional Enrico Weigelt, metux IT consult
2020-11-17 20:23 ` [PATCH 2/2] x86: make hyperv " Enrico Weigelt, metux IT consult
2020-11-18 9:23 ` Wei Liu
2020-11-17 20:31 ` [PATCH 1/2] x86: make vmware " Borislav Petkov
2020-12-02 19:17 ` Enrico Weigelt, metux IT consult
2020-12-02 19:22 ` Borislav Petkov [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-11-17 20:21 Enrico Weigelt, metux IT consult
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=20201202192223.GK2951@zn.tnic \
--to=bp@alien8.de \
--cc=derek.kiernan@xilinx.com \
--cc=dmitry.torokhov@gmail.com \
--cc=dragan.cvetic@xilinx.com \
--cc=hpa@zytor.com \
--cc=info@metux.net \
--cc=linux-hyperv@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@metux.net \
--cc=mingo@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=richardcochran@gmail.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.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 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.