From: Borislav Petkov <bp@alien8.de>
To: "Rafał Miłecki" <zajec5@gmail.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H . Peter Anvin" <hpa@zytor.com>,
x86@kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Problem with late AMD microcode reload/feedback
Date: Sun, 16 Dec 2018 12:12:28 +0100 [thread overview]
Message-ID: <20181216111228.GE815@zn.tnic> (raw)
In-Reply-To: <CACna6ryc2QacKUeSBH5ZVGazOR0-jTeNi7fhm9hGpaXtRJLD+w@mail.gmail.com>
On Sun, Dec 16, 2018 at 12:02:49PM +0100, Rafał Miłecki wrote:
> OK, if you say so, I'll try not to panic seeing those errors repeating
> over and over.
Yes, patience is the key :-)
> I know such issues may take months or years to get fixed, so I was
> trying to do some hacking on my own. I'll try some patience :)
Well, if you wanna hack on stuff, there's a lot more you can do which is
100% safe.
Like getting rid of -Wmissing-prototypes warnings, for example, so that
we can enable this option per default. If you're interested, see here:
https://marc.info/?l=kernel-janitors&m=154178546220848&w=2
It is not hardcore stuff but if you're looking for doing some work on
the kernel, that would be one thing to do.
And of course there's the ever-so-helpful testing of linux-next kernels
on old/spare hardware and trying to fix any issues there. Or reviewing
patches on lkml.
It all depends on what kind of "hacking" you wanna do.
:-)
--
Regards/Gruss,
Boris.
Good mailing practices for 400: avoid top-posting and trim the reply.
next prev parent reply other threads:[~2018-12-16 11:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-15 23:46 Problem with late AMD microcode reload/feedback Rafał Miłecki
2018-12-16 0:05 ` Borislav Petkov
2018-12-16 8:08 ` Rafał Miłecki
2018-12-16 10:06 ` Borislav Petkov
2018-12-16 10:26 ` Rafał Miłecki
2018-12-16 10:44 ` Borislav Petkov
2018-12-16 11:02 ` Rafał Miłecki
2018-12-16 11:12 ` Borislav Petkov [this message]
2018-12-16 0:08 ` Borislav Petkov
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=20181216111228.GE815@zn.tnic \
--to=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=zajec5@gmail.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;
as well as URLs for NNTP newsgroup(s).