mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Borislav Petkov <bp@alien8.de>,
	Tony W Wang-oc <TonyWWang-oc@zhaoxin.com>
Cc: tglx@linutronix.de, mingo@redhat.com, x86@kernel.org,
	linux-kernel@vger.kernel.org, DavidWang@zhaoxin.com,
	CooperYan@zhaoxin.com, QiyuanWang@zhaoxin.com,
	HerryYang@zhaoxin.com, CobeChen@zhaoxin.com
Subject: Re: [PATCH] x86/Kconfig: make X86_UMIP to cover any X86 CPU
Date: Mon, 9 Mar 2020 17:25:59 -0700	[thread overview]
Message-ID: <79c4bc05-0482-3ce7-0f93-544977e466dc@zytor.com> (raw)
In-Reply-To: <20200309203632.GB9002@zn.tnic>

On 2020-03-09 13:36, Borislav Petkov wrote:
> 
> If you're going to do that, is there even any use for that config option
> at all?
> 
> AFAICT, it adds ~1K to kernel text so we might just as well remove the
> ifdeffery completely. The code ends up built in in 99% of the cases
> anyway...
> 

Perhaps the super-tiny-embedded kernel guys care? Otherwise it seems
pointless.

In general, once INTEL and AMD is enabled, it is just a matter of time
until other (still existent) vendors add those features, at least for
core features.

	-hpa

  reply	other threads:[~2020-03-10  0:26 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-09  6:06 Tony W Wang-oc
2020-03-09 20:36 ` Borislav Petkov
2020-03-10  0:25   ` H. Peter Anvin [this message]
2020-03-10  7:24     ` Tony W Wang-oc
2020-03-10  9:09       ` Borislav Petkov
2020-03-10 10:09         ` Tony W Wang-oc
2020-03-10  9:08     ` Borislav Petkov
2020-03-10  9:15 ` [tip: x86/cpu] x86/Kconfig: Drop vendor dependency for X86_UMIP tip-bot2 for Tony W Wang-oc

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=79c4bc05-0482-3ce7-0f93-544977e466dc@zytor.com \
    --to=hpa@zytor.com \
    --cc=CobeChen@zhaoxin.com \
    --cc=CooperYan@zhaoxin.com \
    --cc=DavidWang@zhaoxin.com \
    --cc=HerryYang@zhaoxin.com \
    --cc=QiyuanWang@zhaoxin.com \
    --cc=TonyWWang-oc@zhaoxin.com \
    --cc=bp@alien8.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®