[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20140915183329.70666a8d@mantra.us.oracle.com>
Date: Mon, 15 Sep 2014 18:33:29 -0700
From: Mukesh Rathor <mukesh.rathor@...cle.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@...cle.com>
Cc: boris.ostrovsky@...cle.com, david.vrabel@...rix.com,
xen-devel@...ts.xenproject.org, linux-kernel@...r.kernel.org
Subject: Re: [Xen-devel] [V5 PATCH 1/1] x86/xen: Set EFER.NX and EFER.SCE in
PVH guests
On Fri, 12 Sep 2014 16:42:58 -0400
Konrad Rzeszutek Wilk <konrad.wilk@...cle.com> wrote:
> On Wed, Sep 10, 2014 at 04:36:06PM -0700, Mukesh Rathor wrote:
sorry, i didn't realize you had more comments... didn't scroll down :)..
> > cpumask_var_t xen_cpu_initialized_map;
> >
> > @@ -99,10 +100,14 @@ static void cpu_bringup(void)
> > wmb(); /* make sure everything is
> > out */ }
> >
> > -/* Note: cpu parameter is only relevant for PVH */
> > -static void cpu_bringup_and_idle(int cpu)
> > +/*
> > + * Note: cpu parameter is only relevant for PVH. The reason for
> > passing it
> > + * is we can't do smp_processor_id until the percpu segments are
> > loaded, for
> > + * which we need the cpu number! So we pass it in rdi as first
> > parameter.
> > + */
>
> Thank you for expanding on that (I totally forgot why we did that).
sure.
> > + * The vcpu comes on kernel page tables which have
> > the NX pte
> > + * bit set. This means before DS/SS is touched, NX
> > in
> > + * EFER must be set. Hence the following assembly
> > glue code.
>
> And you ripped out the nice 'N.B' comment I added. Sad :-(
> > */
> > + ctxt->user_regs.eip = (unsigned
> > long)xen_pvh_early_cpu_init; ctxt->user_regs.rdi = cpu;
> > + ctxt->user_regs.rsi = true; /* secondary cpu ==
> > true */
>
> Oh, that is new. Ah yes we can use that [looking at Xen code].
> I wonder what other registers we can use to pass stuff around.
All GPRs. I commented that we can do that in the Rogers PVH doc.
Looks like David responded to other comments.
Thanks,
Mukesh
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists