All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Egger <Christoph.Egger@amd.com>
To: xen-devel@lists.xensource.com
Cc: "Tian, Kevin" <kevin.tian@intel.com>
Subject: Re: [PATCH] x86,amd,microcode: fix hypercall return code
Date: Mon, 22 Sep 2008 14:59:10 +0200	[thread overview]
Message-ID: <200809221459.10713.Christoph.Egger@amd.com> (raw)
In-Reply-To: <D8078B8B3B09934AA9F8F2D5FB3F28CE08873AF2D7@pdsmsx502.ccr.corp.intel.com>

On Monday 22 September 2008 14:47:38 Tian, Kevin wrote:
> >From: Christoph Egger
> >Sent: 2008年9月22日 20:23
> >
> >
> >Hi,
> >
> >Attached patch makes the hypercall return failure
> >if the microcode didn't apply.
> >
> >Signed-off-by: Christoph Egger <Christoph.Egger@amd.com>
>
> It's weird that you don't add a 'break' if apply_microcode failed,
> unless you're sure next invocation to get_next_ucode_from_buffer
> _amd return 0... But even that, this is a bad coding style.

Yes, it is. Note, I ported that code from Linux. I don't know if
code from BSD would have been accepted due to license
incompatibilities.

Christoph

-- 
AMD Saxony, Dresden, Germany
Operating System Research Center

Legal Information:
AMD Saxony Limited Liability Company & Co. KG
Sitz (Geschäftsanschrift):
   Wilschdorfer Landstr. 101, 01109 Dresden, Deutschland
Registergericht Dresden: HRA 4896
vertretungsberechtigter Komplementär:
   AMD Saxony LLC (Sitz Wilmington, Delaware, USA)
Geschäftsführer der AMD Saxony LLC:
   Dr. Hans-R. Deppe, Thomas McCoy

      reply	other threads:[~2008-09-22 12:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-22 12:22 [PATCH] x86,amd,microcode: fix hypercall return code Christoph Egger
2008-09-22 12:47 ` Tian, Kevin
2008-09-22 12:59   ` Christoph Egger [this message]

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=200809221459.10713.Christoph.Egger@amd.com \
    --to=christoph.egger@amd.com \
    --cc=kevin.tian@intel.com \
    --cc=xen-devel@lists.xensource.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 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.