From: Boris Ostrovsky <boris.ostrovsky@oracle.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>,
"Luis R. Rodriguez" <mcgrof@suse.com>
Cc: Juergen Gross <jgross@suse.com>, Michal Marek <mmarek@suse.cz>,
Jason Douglas <jdouglas@suse.com>,
"Luis R. Rodriguez" <mcgrof@do-not-panic.com>,
Takashi Iwai <tiwai@suse.de>,
stefano.stabellini@eu.citrix.com,
Henrique de Moraes Holschuh <hmh@debian.org>,
david.vrabel@citrix.com, Jan Beulich <JBeulich@suse.com>,
xen-devel@lists.xenproject.org, 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, 30 Jan 2015 16:24:43 -0500 [thread overview]
Message-ID: <54CBF69B.8020700@oracle.com> (raw)
In-Reply-To: <54CBEB8D.8030509@citrix.com>
On 01/30/2015 03:37 PM, Andrew Cooper wrote:
>
> The actions Xen needs to take are:
>
> - Copy the buffer into Xen.
> - Scan the buffer for the correct patch
Why not have the toolstack search for the right patch? Hypervisor will
verify that it's appropriate but won't have to spend time scanning the
(potentially large) buffer.
(The logic for scanning the buffer is in the hypervisor code but we
could move it to a library)
-boris
> - Rendezvous all online cpus in an IPI to apply the patch, and keep the
> processors in until all have completed the patch.
>
>
next prev parent reply other threads:[~2015-01-30 21:25 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 [this message]
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
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=54CBF69B.8020700@oracle.com \
--to=boris.ostrovsky@oracle.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.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=mcgrof@suse.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.