Hi Konrad,
On 06/06/16 15:17, Konrad Rzeszutek Wilk wrote:
On Thu, Jun 02, 2016 at 04:14:04PM +0100, Julien Grall wrote:
On 02/06/16 16:04, Julien Grall wrote:
Hi Konrad,
On 02/06/16 15:46, Konrad Rzeszutek Wilk wrote:
On Tue, May 31, 2016 at 11:24:10AM +0100, Julien Grall wrote:
On 31/05
On Thu, Jun 02, 2016 at 04:14:04PM +0100, Julien Grall wrote:
>
>
> On 02/06/16 16:04, Julien Grall wrote:
> >Hi Konrad,
> >
> >On 02/06/16 15:46, Konrad Rzeszutek Wilk wrote:
> >>On Tue, May 31, 2016 at 11:24:10AM +0100, Julien Grall wrote:
> >>>On 31/05/16 10:21, Stefano Stabellini wrote:
> >>>
On 02/06/16 16:04, Julien Grall wrote:
Hi Konrad,
On 02/06/16 15:46, Konrad Rzeszutek Wilk wrote:
On Tue, May 31, 2016 at 11:24:10AM +0100, Julien Grall wrote:
On 31/05/16 10:21, Stefano Stabellini wrote:
On Mon, 30 May 2016, Julien Grall wrote:
By spinning in __apply_alternatives_multi_st
Hi Konrad,
On 02/06/16 15:46, Konrad Rzeszutek Wilk wrote:
On Tue, May 31, 2016 at 11:24:10AM +0100, Julien Grall wrote:
On 31/05/16 10:21, Stefano Stabellini wrote:
On Mon, 30 May 2016, Julien Grall wrote:
By spinning in __apply_alternatives_multi_stop we protect us against
modification in t
On Tue, May 31, 2016 at 11:24:10AM +0100, Julien Grall wrote:
> Hi Stefano,
>
> On 31/05/16 10:21, Stefano Stabellini wrote:
> >On Mon, 30 May 2016, Julien Grall wrote:
> >>Hi Stefano,
> >>
> >>On 30/05/2016 15:45, Stefano Stabellini wrote:
> >>>On Mon, 23 May 2016, Julien Grall wrote:
> Hi St
Hi Stefano,
On 31/05/16 10:21, Stefano Stabellini wrote:
On Mon, 30 May 2016, Julien Grall wrote:
Hi Stefano,
On 30/05/2016 15:45, Stefano Stabellini wrote:
On Mon, 23 May 2016, Julien Grall wrote:
Hi Stefano,
On 21/05/16 16:09, Stefano Stabellini wrote:
On Thu, 5 May 2016, Julien Grall wr
On Mon, 30 May 2016, Julien Grall wrote:
> Hi Stefano,
>
> On 30/05/2016 15:45, Stefano Stabellini wrote:
> > On Mon, 23 May 2016, Julien Grall wrote:
> > > Hi Stefano,
> > >
> > > On 21/05/16 16:09, Stefano Stabellini wrote:
> > > > On Thu, 5 May 2016, Julien Grall wrote:
> > > > > +void __init
Hi Stefano,
On 30/05/2016 15:45, Stefano Stabellini wrote:
On Mon, 23 May 2016, Julien Grall wrote:
Hi Stefano,
On 21/05/16 16:09, Stefano Stabellini wrote:
On Thu, 5 May 2016, Julien Grall wrote:
+void __init apply_alternatives_all(void)
+{
+int ret;
+
+ /* better not try code pat
On Mon, 23 May 2016, Julien Grall wrote:
> Hi Stefano,
>
> On 21/05/16 16:09, Stefano Stabellini wrote:
> > On Thu, 5 May 2016, Julien Grall wrote:
> > > +void __init apply_alternatives_all(void)
> > > +{
> > > +int ret;
> > > +
> > > + /* better not try code patching on a live SMP system */
>
Hi Stefano,
On 21/05/16 16:09, Stefano Stabellini wrote:
On Thu, 5 May 2016, Julien Grall wrote:
+void __init apply_alternatives_all(void)
+{
+int ret;
+
+ /* better not try code patching on a live SMP system */
+ret = stop_machine_run(__apply_alternatives_multi_stop, NULL, NR_CPU
On Thu, 5 May 2016, Julien Grall wrote:
> Some of the processor erratum will require to modify code sequence.
> As those modifications may impact the performance, they should only
> be enabled on affected cores. Furthermore, Xen may also want to take
> advantage of new hardware features coming up w
Hi Konrad,
On 13/05/2016 21:26, Konrad Rzeszutek Wilk wrote:
On Thu, May 05, 2016 at 05:34:19PM +0100, Julien Grall wrote:
Some of the processor erratum will require to modify code sequence.
As those modifications may impact the performance, they should only
be enabled on affected cores. Furthe
On Thu, May 05, 2016 at 05:34:19PM +0100, Julien Grall wrote:
> Some of the processor erratum will require to modify code sequence.
> As those modifications may impact the performance, they should only
> be enabled on affected cores. Furthermore, Xen may also want to take
> advantage of new hardwar
13 matches
Mail list logo
