From: Borislav Petkov <bp@alien8.de>
To: Marcos Del Sol Vives <marcos@orca.pet>
Cc: x86@kernel.org, Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86: add support DM&P devices
Date: Wed, 13 Oct 2021 18:57:49 +0200 [thread overview]
Message-ID: <YWcQDYY9CuWKsayl@zn.tnic> (raw)
In-Reply-To: <20211008162246.1638801-1-marcos@orca.pet>
On Fri, Oct 08, 2021 at 06:22:46PM +0200, Marcos Del Sol Vives wrote:
> +config CPU_SUP_DMP_32
> + default y
> + bool "Support DM&P processors" if PROCESSOR_SELECT
> + depends on !64BIT
You mean
depends on X86_32
?
Wikipedia says those things are 32-bit.
> + help
> + This enables detection, tunings and quirks for DM&P processors
> +
> + You need this enabled if you want your kernel to run on a
> + DM&P CPU. Disabling this option on other types of CPUs
So I'm not sure about the nomenclature: those CPUs are called Vortex86
and DM&P is simply the next owner of the IP:
"Vortex86 previously belonged to SiS, which got the basic design from
Rise Technology.[1] SiS sold it to DM&P Electronics[2] in Taiwan."
So I'm thinking we should call everything Vortex, the file vortex.c, the
vendor define X86_VENDOR_VORTEX and so on.
> + makes the kernel a tiny bit smaller. Disabling it on a DM&P
> + CPU might render the kernel unbootable.
Why unbootable? It looks like those are perfect clones: "No special init
required for DM&P processors." it says in the patch. :)
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
next prev parent reply other threads:[~2021-10-13 16:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-08 16:22 [PATCH] x86: add support DM&P devices Marcos Del Sol Vives
2021-10-13 16:57 ` Borislav Petkov [this message]
2021-10-14 18:29 ` Marcos Del Sol Vives
2021-10-16 17:52 ` Borislav Petkov
-- strict thread matches above, loose matches on Subject: below --
2021-06-28 8:03 Marcos Del Sol Vives
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=YWcQDYY9CuWKsayl@zn.tnic \
--to=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcos@orca.pet \
--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;
as well as URLs for NNTP newsgroup(s).