All of lore.kernel.org
 help / color / mirror / Atom feed
From: Aravind Gopalakrishnan <aravind.gopalakrishnan@amd.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: Andrew Cooper <andrew.cooper3@citrix.com>,
	boris.ostrovsky@oracle.com, keir@xen.org,
	Suravee.Suthikulpanit@amd.com, xen-devel@lists.xen.org
Subject: Re: [PATCH V3] x86, amd_ucode: Skip microcode updates for final levels
Date: Tue, 11 Aug 2015 10:43:31 -0500	[thread overview]
Message-ID: <55CA1823.5010703@amd.com> (raw)
In-Reply-To: <55CA319E0200007800099B5B@prv-mh.provo.novell.com>

On 8/11/2015 10:32 AM, Jan Beulich wrote:
>>>>>> +static bool_t check_final_patch_levels(int cpu)
>>>>> unsigned int
>>>>>
>>>> I can change this too, but- Any specific reason for this?
>>>> The other sanity checker or verification functions like
>>>> verify_patch_size() or microcode_fits() return a bool_t too..
>>> "int cpu" is the issue (I am guessing), not the return type.
>>>
>> Thought about that too.. but all the microcode_ops functions accept an
>> 'int cpu'.
>> I'm just using the same type in check_final_patch_levels().
> And ideally all other bad examples would be fixed in a cleanup
> patch too - CPU numbers can't be negative. In any event we
> should aim at not proliferating such sub-optimal code.
>


Okay, I can clean that up while at it.

Would it be OK if I did a pre-patch to cleanup the 'int cpu' usage in 
the microcode* files and then apply this patch on top of it?

Thanks,
-Aravind.

  reply	other threads:[~2015-08-11 15:43 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-03 19:34 [PATCH V3] x86, amd_ucode: Skip microcode updates for final levels Aravind Gopalakrishnan
2015-08-03 19:54 ` Boris Ostrovsky
2015-08-03 22:51   ` Andrew Cooper
2015-08-11 14:53 ` Jan Beulich
2015-08-11 15:14   ` Aravind Gopalakrishnan
2015-08-11 15:17     ` Andrew Cooper
2015-08-11 15:28       ` Aravind Gopalakrishnan
2015-08-11 15:32         ` Jan Beulich
2015-08-11 15:43           ` Aravind Gopalakrishnan [this message]
2015-08-11 15:57             ` Jan Beulich
2015-08-11 15:29       ` Jan Beulich

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=55CA1823.5010703@amd.com \
    --to=aravind.gopalakrishnan@amd.com \
    --cc=JBeulich@suse.com \
    --cc=Suravee.Suthikulpanit@amd.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=boris.ostrovsky@oracle.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.