Re: [PATCH] VMX: XSA-60 workaround

[Matt Wilson <msw@amazon.com>]

On Tue, Aug 20, 2013 at 08:22:41AM +0100, Jan Beulich wrote:
> >>> On 19.08.13 at 20:27, Matt Wilson <msw@amazon.com> wrote:
> > On Tue, Aug 13, 2013 at 05:36:17PM +0100, Jan Beulich wrote:
> >> Considering that there's still no real progress towards a resolution
> >> for XSA-60, I'd like to propose turning off the probelamtic code by
> >> default, allowing it to be turned back on via command line option.
> > 
> > Apologies for a late reply, I've been on holiday for the past week.
> > 
> > I think it'd be really handy to make this a per-domain configuration,
> > perhaps with a system-wide default set by boot command line.
> 
> Remember this is a temporary workaround, not a solution. I'm
> not going to waste time trying to make the logic more sophisticated,
> but I wouldn't mind if someone else took the patch further.

I'd like to help with a solution. What's the current thinking on the
best way to handle the problem?

> > If not per-domain, it would be helpful to be configurable at boot time.
> 
> Which it is - did you overlook the addition of the
> "vmx-permit-cache-disable" command line option?

Sorry, I dropped some words out. Of course this is currently a boot
time parameter now. I meant to ask if it could be made *run time*
configurable with a boot time default.

--msw