All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Cooper <andrew.cooper3@citrix.com>
To: "Luis R. Rodriguez" <mcgrof@do-not-panic.com>
Cc: Juergen Gross <jgross@suse.com>, Michal Marek <mmarek@suse.cz>,
	Jason Douglas <jdouglas@suse.com>,
	Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
	Takashi Iwai <tiwai@suse.de>,
	Henrique de Moraes Holschuh <hmh@debian.org>,
	David Vrabel <david.vrabel@citrix.com>,
	Jan Beulich <JBeulich@suse.com>,
	xen-devel@lists.xenproject.org,
	Boris Ostrovsky <boris.ostrovsky@oracle.com>,
	Borislav Petkov <bp@suse.de>, Olaf Hering <ohering@suse.de>
Subject: Re: [RFC v2] misc/xenmicrocode: Upload /lib/firmware/<some blob> to the hypervisor
Date: Fri, 12 Jun 2015 09:48:24 +0100	[thread overview]
Message-ID: <557A9CD8.9010507@citrix.com> (raw)
In-Reply-To: <CAB=NE6X5L8hPa3217vGY+Q=d_q1UyzrgR6J7+oberQyzu73Gew@mail.gmail.com>

On 12/06/15 03:30, Luis R. Rodriguez wrote:
> On Fri, Jan 30, 2015 at 1:57 PM, Luis R. Rodriguez <mcgrof@suse.com> wrote:
>> On Fri, Jan 30, 2015 at 08:37:33PM +0000, Andrew Cooper wrote:
>>> The right thing to do is to fix the hypercall implementation, at which
>>> point the utility below is fine and xc_microcode_update() can be a thing
>>> wrapper around the hypercall.
>>>
>>> The actions Xen needs to take are:
>>>
>>> - Copy the buffer into Xen.
>>> - Scan the buffer for the correct patch
>>> - Rendezvous all online cpus in an IPI to apply the patch, and keep the
>>> processors in until all have completed the patch.
>>>
>>> The IPI itself probably wants common rendezvous code, and a system
>>> specific call for application.  The system specific call will need to
>>> adhere to the requirements in the relevant manual.  Care will have to be
>>> taken to avoid deadlocking with the time calibration rendezvous, and
>>> facilities such as the watchdog might temporally need pausing.
>>>
>>> If you feel up to all that, then please go ahead.  If not, I will
>>> attempt to find some copious free time.
>> You can have a crack at that. Let me know when the above is ready and I'll
>> respin. I'd try it but it seems you would spend considerbly less time than
>> me doing the above.
> Andrew, wanted to check to see if you have had time to work on the above.

Sadly no - I have not had time.

~Andrew

  reply	other threads:[~2015-06-12  8:48 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-30  1:14 [RFC v2] misc/xenmicrocode: Upload /lib/firmware/<some blob> to the hypervisor Luis R. Rodriguez
2015-01-30 14:23 ` Andrew Cooper
2015-01-30 19:51   ` Luis R. Rodriguez
2015-01-30 20:37     ` Andrew Cooper
2015-01-30 21:24       ` Boris Ostrovsky
2015-01-30 21:55         ` Andrew Cooper
2015-01-30 21:57       ` Luis R. Rodriguez
2015-06-12  2:30         ` Luis R. Rodriguez
2015-06-12  8:48           ` Andrew Cooper [this message]
2015-01-30 14:44 ` Boris Ostrovsky
2015-01-30 20:05   ` Luis R. Rodriguez
2015-01-30 21:14     ` Boris Ostrovsky
2015-01-30 21:28       ` Luis R. Rodriguez

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=557A9CD8.9010507@citrix.com \
    --to=andrew.cooper3@citrix.com \
    --cc=JBeulich@suse.com \
    --cc=boris.ostrovsky@oracle.com \
    --cc=bp@suse.de \
    --cc=david.vrabel@citrix.com \
    --cc=hmh@debian.org \
    --cc=jdouglas@suse.com \
    --cc=jgross@suse.com \
    --cc=mcgrof@do-not-panic.com \
    --cc=mmarek@suse.cz \
    --cc=ohering@suse.de \
    --cc=stefano.stabellini@eu.citrix.com \
    --cc=tiwai@suse.de \
    --cc=xen-devel@lists.xenproject.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.