All of lore.kernel.org
 help / color / mirror / Atom feed
From: Boris Ostrovsky <boris.ostrovsky@oracle.com>
To: Aravind Gopalakrishnan <aravind.gopalakrishnan@amd.com>,
	jbeulich@suse.com, andrew.cooper3@citrix.com
Cc: keir@xen.org, Suravee.Suthikulpanit@amd.com, xen-devel@lists.xen.org
Subject: Re: [PATCH V2] x86, amd_ucode: Skip microcode updates for final levels
Date: Mon, 03 Aug 2015 15:00:41 -0400	[thread overview]
Message-ID: <55BFBA59.6070004@oracle.com> (raw)
In-Reply-To: <55BFB61F.5090805@amd.com>

On 08/03/2015 02:42 PM, Aravind Gopalakrishnan wrote:
>
> Ah. I see what you mean.
> I can think of two ways around this-
> a. I can move the check_final_patch_levels() call to 
> apply_microcode(). That way, our initial checks in microcode_fits() 
> would have already checked equivalent cpu IDs so we know we are on the 
> right family.
> b. Introduce a family check in this patch as you suggested (It's a 
> simple change, should work fine too and I think can retain Andrew's 
> 'Reviewed-by' as the logic doesn't change too much..)
>
> Do let me know if you have a preference.

I'd leave it where it is right now since there is no reason to do all 
allocations/checks/stuff and then get to apply_microcode() and find out 
that it was all for nothing. So just testing boot_cpu_data.x86 in 
check_final_patch_levels() and returning if it's not 10h should be 
sufficient.

Thanks.
-boris

  reply	other threads:[~2015-08-03 19:00 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-03 16:35 [PATCH V2] x86, amd_ucode: Skip microcode updates for final levels Aravind Gopalakrishnan
2015-08-03 16:43 ` Andrew Cooper
2015-08-03 17:22 ` Boris Ostrovsky
2015-08-03 17:52   ` Aravind Gopalakrishnan
2015-08-03 18:18     ` Boris Ostrovsky
2015-08-03 18:42       ` Aravind Gopalakrishnan
2015-08-03 19:00         ` Boris Ostrovsky [this message]
2015-08-03 19:11           ` Aravind Gopalakrishnan

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=55BFBA59.6070004@oracle.com \
    --to=boris.ostrovsky@oracle.com \
    --cc=Suravee.Suthikulpanit@amd.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=aravind.gopalakrishnan@amd.com \
    --cc=jbeulich@suse.com \
    --cc=keir@xen.org \
    --cc=xen-devel@lists.xen.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.