Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1301210
| From | Piotr Dąbrowski <ultr@ultr.pl> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: new cmdline parameter disable_cpu_features= (microcode update?) |
| Date | 2016-01-05 01:30 +0100 |
| Message-ID | <qNnFE-2qI-7@gated-at.bofh.it> (permalink) |
| References | <qNmgy-1m8-9@gated-at.bofh.it> <qNmzU-1JR-13@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
Thank you for your reply.
> You cannot change the microcode patches - they're supplied by the CPU
> vendors as is and are signed/encrypted.
Is the microcode's header encrypted too?
I thought there are two Processor Flags fields ('pf') available [1].
Are they what I think they are?
Is the header signed too, or only the actual microcode blob below the
headers is?
Sorry if I get it all wrong and there is no use for further discussion.
Do you think there is any point in actually implementing the
kernel-only disable_cpu_features= option upstream
and then somehow convince the userland to respect flags reported by
the kernel instead of those from the CPU?
[1] arch/x86/include/asm/microcode_intel.h:
struct microcode_header_intel {
unsigned int hdrver;
unsigned int rev;
unsigned int date;
unsigned int sig;
unsigned int cksum;
unsigned int ldrver;
unsigned int pf;
unsigned int datasize;
unsigned int totalsize;
unsigned int reserved[3];
};
[...]
/* microcode format is extended from prescott processors */
struct extended_signature {
unsigned int sig;
unsigned int pf;
unsigned int cksum;
};
Best Regards,
Piotr Dąbrowski
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
new cmdline parameter disable_cpu_features= (microcode update?) Piotr Dąbrowski <ultr@ultr.pl> - 2016-01-05 00:00 +0100
Re: new cmdline parameter disable_cpu_features= (microcode update?) Borislav Petkov <bp@alien8.de> - 2016-01-05 00:20 +0100
Re: new cmdline parameter disable_cpu_features= (microcode update?) Piotr Dąbrowski <ultr@ultr.pl> - 2016-01-05 01:30 +0100
Re: new cmdline parameter disable_cpu_features= (microcode update?) Borislav Petkov <bp@alien8.de> - 2016-01-05 12:40 +0100
csiph-web